Editing Guideline: How to Contribute Code
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 1: | Line 1: | ||
{{welcome}} | {{welcome}} | ||
{{Navbar Development Contributor Page}} | {{Navbar Development Contributor Page}} | ||
| − | + | ||
==Introduction== | ==Introduction== | ||
| − | On this page we would like to give you some rules for developers, how to contribute code and how things need should be done. The following guidline is derived from a statement of Eric Turgeon at 13.06.20 | + | On this page we would like to give you some rules for developers, how to contribute code and how things need should be done. The following guidline is derived from a statement of Eric Turgeon at [13.06.20 16:39] on Telegram as founder and leader of this project. |
| + | |||
| + | |||
==Guidline== | ==Guidline== | ||
| Line 10: | Line 12: | ||
In the meantime, for those that GhostBSD Github members. | In the meantime, for those that GhostBSD Github members. | ||
| − | # The only official supported desktop is | + | # The only official supported desktop is MATE. The other DE's are community releases. That might change in the future, but for now, the main focus is MATE. Nevertheless the same rules apply to the ports and changes to ghostbsd-build and all the other tools. |
# For ports, make sure new or update port does not change or override a file from other ports, including config files. With other words: ports have only to care about themselves. All files that ports installed need to be tracked, except config files. | # For ports, make sure new or update port does not change or override a file from other ports, including config files. With other words: ports have only to care about themselves. All files that ports installed need to be tracked, except config files. | ||
| − | # Follow the | + | # Follow the FreeBSD ports Handbook for test for the guideline to make ports. A useful tool is portlint to verify the port is done right. |
| − | # When it comes to the GhostBSD tools, including | + | # When it comes to the GhostBSD tools, including ghostbsd-build, work on sorted tickets. If there is no ticket, no code gets in unless it is new port or port updates. |
# Please do not create a ticket with questions. It will close immediately with a reply message to join GHostBSD forums or Telegram for questions. | # Please do not create a ticket with questions. It will close immediately with a reply message to join GHostBSD forums or Telegram for questions. | ||
# If you have an idea, share it with everyone on Telegram. If the idea is good, a ticket will be done. | # If you have an idea, share it with everyone on Telegram. If the idea is good, a ticket will be done. | ||
| − | # If you work on a non-official GhostBSD, like | + | # If you work on a non-official GhostBSD, like XFCE, let everyone know on Telegram, what you are working on, to make sure no one oversteps on other's works. |
| − | # Don't start something that will affect any GhostBSD | + | # Don't start something that will affect any GhostBSD tools and or GhostBSD itself without a sorted ticket. The main reason is unplanned changes can affect other's work and affect the main project. |
| − | # The main point is | + | # The main point is to communicate with all people who are working on GhostBSD. Transparency is important to avoid frustrations. |
| − | + | ||
| − | + | ||
For anyone who is not happy with this can start his/her own project. | For anyone who is not happy with this can start his/her own project. | ||
