Difference between revisions of "Become a Developer"
m |
Tigersharke (Talk | contribs) |
||
| Line 1: | Line 1: | ||
<noinclude>{{NavHeader|back=Become a Translator|forward=Report Bugs}}</noinclude> | <noinclude>{{NavHeader|back=Become a Translator|forward=Report Bugs}}</noinclude> | ||
| − | If you like programming, and especially coding on FreeBSD, we would love to see you join the | + | If you like programming, and especially coding on FreeBSD, we would love to see you join the {{citelink|url=http://pcbsd.org/team-members|PC-BSD Team}} as a PC-BSD committer. Developers who want to help improve the PC-BSD codebase are always welcome! If you would like to take part in core development, and possibly earn a commit bit, a good place to get started is by signing up for the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/dev|developers mailing list}}. Once you have signed up, feel free to browse our active [[PC-BSD 9.1 TODO|TODO list]], or search for bugs that need fixing in the PC-BSD {{citelink|url=http://trac.pcbsd.org/|Trac database}}. If you see something of interest you want to work on, or have a proposal for a project you wish to add to PC-BSD, please let us know via the developers list and we will be happy to help get you started. |
Most of the PC-BSD specific GUI tools are developed in C++ using the QT Libraries, and other non-GUI development is done using standard Bourne shell scripts. There may be cases where other languages or libraries are needed, but those will be evaluated on a case-by-case basis, so feel free to let us know your proposals on the developers mailing list. | Most of the PC-BSD specific GUI tools are developed in C++ using the QT Libraries, and other non-GUI development is done using standard Bourne shell scripts. There may be cases where other languages or libraries are needed, but those will be evaluated on a case-by-case basis, so feel free to let us know your proposals on the developers mailing list. | ||
| Line 7: | Line 7: | ||
Developers will also find the following resources helpful: | Developers will also find the following resources helpful: | ||
| − | * | + | * {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/commits|Commits Mailing List}} |
| − | * | + | * {{citelink|url=http://trac.pcbsd.org/wiki/Developers|Development Wiki}} |
| − | * | + | * {{citelink|url=http://trac.pcbsd.org/wiki/GettingSource|Getting PC-BSD Source}} |
| − | * | + | * {{citelink|url=http://doc.trolltech.com/4.6/qmake-manual.html|qmake Manual}} |
| + | <noinclude>{{refheading}}</noinclude> | ||
<noinclude> | <noinclude> | ||
[[category:handbook]] | [[category:handbook]] | ||
Revision as of 21:25, 17 July 2012
| Become a Developer |
If you like programming, and especially coding on FreeBSD, we would love to see you join the PC-BSD Team[1] as a PC-BSD committer. Developers who want to help improve the PC-BSD codebase are always welcome! If you would like to take part in core development, and possibly earn a commit bit, a good place to get started is by signing up for the developers mailing list[2]. Once you have signed up, feel free to browse our active TODO list, or search for bugs that need fixing in the PC-BSD Trac database[3]. If you see something of interest you want to work on, or have a proposal for a project you wish to add to PC-BSD, please let us know via the developers list and we will be happy to help get you started.
Most of the PC-BSD specific GUI tools are developed in C++ using the QT Libraries, and other non-GUI development is done using standard Bourne shell scripts. There may be cases where other languages or libraries are needed, but those will be evaluated on a case-by-case basis, so feel free to let us know your proposals on the developers mailing list.
Developers will also find the following resources helpful:
References
