The development of FreeBSD is a very open and flexible process, being literally built from the contributions of thousands of people around the world, as can be seen from our list
FreeBSD’s development infrastructure allow these thousands of contributors to collaborate over the Internet.
We are constantly on the lookout for new developers and ideas, and those interested in becoming more closely involved with the project need simply contact us at the link:FreeBSD technical discussions mailing list.
The link:FreeBSD announcements mailing list is also available to those wishing to make other FreeBSD users aware of major areas of work.
Useful things to know about the FreeBSD Project and its development process, whether working independently or in close cooperation:
For several years, the central source tree for FreeBSD was maintained by CVS (Concurrent Versions System), a freely available source code control tool.
In June 2008, the Project switched to using SVN (Subversion). The switch was deemed necessary, as the technical limitations imposed by
CVS were becoming obvious due to the rapid expansion of the source tree and the amount of history already stored.
The Documentation Project and Ports Collection repositories also moved from
SVN in May 2012 and July 2012, respectively.
Please refer to the Synchronizing your source
tree section for more information on obtaining the FreeBSD
src/ repository and Using the Ports
Collection for details on obtaining the FreeBSD Ports Collection.
- The committers list
are the people who have write access to the Subversion tree, and are authorized to make modifications to the FreeBSD source (the term “committer”
commit, the source control command which is used to bring new changes into the repository). Anyone can submit a bug to the Bug
Before submitting a bug report, the FreeBSD mailing lists, IRC channels, or forums can be used to help verify that an issue is actually a bug.
- The FreeBSD core team
The FreeBSD core team
would be equivalent to the board of directors if the FreeBSD Project were a company.
The primary task of the core team is to make sure the project, as a whole, is in good shape and is heading in the right directions.
Inviting dedicated and responsible developers to join our group of committers is one of the functions of the core team, as is the recruitment of new core team members as others move on.
The current core team was elected from a pool of committer candidates in July 2018.
Elections are held every 2 years.
Like most developers, most members of the core team are also volunteers when it comes to FreeBSD development and do not benefit from the project financially, so “commitment”
should also not be misconstrued as meaning “guaranteed support.”
The “board of directors”
analogy above is not very accurate, and it may be more suitable to say that these are the people who gave up their lives in favor of FreeBSD against their better judgement!
- Outside contributors
Last, but definitely not least, the largest group of developers are the users themselves who provide feedback and bug fixes to us on an almost constant basis.
The primary way of keeping in touch with FreeBSD’s more non-centralized development is to subscribe to the link:FreeBSD technical discussions mailing list where such things are discussed.
See [_eresources] for more information about the various FreeBSD mailing lists.
FreeBSD Contributors List
is a long and growing one, so why not join it by contributing something back to FreeBSD today?
Providing code is not the only way of contributing to the project; for a more complete list of things that need doing, please refer to the FreeBSD Project
In summary, our development model is organized as a loose set of concentric circles.
The centralized model is designed for the convenience of the users of FreeBSD, who are provided with an easy way of tracking one central code base, not to keep potential contributors out! Our desire is to present a stable operating system with a large set of coherent application programs that the users can easily install and use — this model works very well in accomplishing that.
All we ask of those who would join us as FreeBSD developers is some of the same dedication its current people have to its continued success!