Difference between revisions of "Development Contributor Page"
(→Introduction) |
(→Developing on GhostBSD) |
||
| (6 intermediate revisions by the same user not shown) | |||
| 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. Some users say: "Wouldn't it look a program prettier this way?" or "I would like to change the name or the logo of this project, because it would be cooler or it seems out of date" and so on. |
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 12: | Line 12: | ||
==Developing on GhostBSD== | ==Developing on GhostBSD== | ||
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: '''ASK QUESTIONS, ASK Eric''' on Telegram. | ||
| + | |||
| + | There is a group on [https://t.me/ghostbsd Telegram]: GhostBSD Dev. Describe you background, you knowledge and ask Eric, were to begin. | ||
We recommend to read first | We recommend to read first | ||
| + | * [[Code of Conduct]] | ||
* [[Guideline: How to Contribute Code]] and | * [[Guideline: How to Contribute Code]] and | ||
* [[Porters Guideline]] | * [[Porters Guideline]] | ||
| − | |||
For anyone who is not happy with this guidelines can start his/her own project. | For anyone who is not happy with this guidelines can start his/her own project. | ||
| Line 24: | Line 28: | ||
It is also recommended to read | It is also recommended to read | ||
* [https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ The FreeBSD developers handbook] and | * [https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ The FreeBSD developers handbook] and | ||
| − | * [https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ | + | * [https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ The FreeBSD porters handbook] |
to understand the basics. | to understand the basics. | ||
Latest revision as of 15:43, 19 June 2020
| Development Contributor Page | ||
|---|---|---|
| Porters Guideline | Guideline: How to Contribute Code | GhostBSD Builds |
Back to  Contribution
| ||
Introduction[edit]
It is often the same: If a newcomer steps in a running project, he or she think they have to reinvent the wheel. Some users say: "Wouldn't it look a program prettier this way?" or "I would like to change the name or the logo of this project, because it would be cooler or it seems out of date" and so on.
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.
So we will describe some guidelines and rules for those people, who are like to contribute tho GhostBSD as a developer.
Developing on GhostBSD[edit]
The GhostBSD System is installed and you are ready to start programming. But where to start?
The first and most important step is: ASK QUESTIONS, ASK Eric on Telegram.
There is a group on Telegram: GhostBSD Dev. Describe you background, you knowledge and ask Eric, were to begin.
We recommend to read first
For anyone who is not happy with this guidelines can start his/her own project.
Additional Information[edit]
It is also recommended to read
to understand the basics.
