Up until now, the FreeBSD project has released a number of described techniques to do different parts of work. However, a project model summarising how the project is structured is needed because of the increasing amount of project members. [1] This paper will provide such a project model and is donated to the FreeBSD Documentation project where it can evolve together with the project so that it can at any point in time reflect the way the project works. It is based on [Saers, 2003].
I would like to thank the following people for taking the time to explain things that were unclear to me and for proofreading the document.
Andrey A. Chernov <[email protected]>
Bruce A. Mah <[email protected]>
Dag-Erling Smørgrav <[email protected]>
Giorgos Keramidas<[email protected]>
Ingvil Hovig <[email protected]>
Jesper Holck<[email protected]>
John Baldwin <[email protected]>
John Polstra <[email protected]>
Kirk McKusick <[email protected]>
Mark Linimon <[email protected]>
Marleen Devos
Niels Jørgenssen<[email protected]>
Nik Clayton <[email protected]>
Poul-Henning Kamp <[email protected]>
Simon L. Nielsen <[email protected]>
| [1] |
This goes hand-in-hand with Brooks' law that “adding another person to a late project will make it later” since it will increase the communication needs Brooks, 1995. A project model is a tool to reduce the communication needs. |
This, and other documents, can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/.
For questions about FreeBSD, read the documentation before contacting <[email protected]>.
For questions about this documentation, e-mail <[email protected]>.