Editing Development Contributor Page
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
==Introduction== | ==Introduction== | ||
− | It is often the same: If a newcomer steps in a running project, he or she think they have to reinvent the wheel | + | It is often the same: If a newcomer steps in a running project, he or she think they have to reinvent the wheel. |
The more people work on a project the more necessary is it, to follow some simple rules, to ensure a save workflow to build GhostBSD releases. For this project is it important to get a clear structure, open communication, and transparency. | The more people work on a project the more necessary is it, to follow some simple rules, to ensure a save workflow to build GhostBSD releases. For this project is it important to get a clear structure, open communication, and transparency. | ||
Line 13: | Line 13: | ||
The GhostBSD System is installed and you are ready to start programming. But where to start? | The GhostBSD System is installed and you are ready to start programming. But where to start? | ||
− | The first and most important step is: | + | The first and most important step is: ASK a QUESTION, ASK Eric on Telegram. |
− | There is | + | There is a chanal: GhostBSD Dev on Telegram, describe you background, you knowledge and ask Eric, were to begin. |
We recommend to read first | We recommend to read first | ||
− | |||
* [[Guideline: How to Contribute Code]] and | * [[Guideline: How to Contribute Code]] and | ||
* [[Porters Guideline]] | * [[Porters Guideline]] |