A project model for the FreeBSD Project
Prev |  | Next

# Foreword

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 `<ache@freebsd.org>`

- Bruce A. Mah `<bmah@freebsd.org>`

- Dag-Erling Smørgrav `<des@freebsd.org>`

- Giorgos Keramidas`<keramida@freebsd.org>`

- Ingvil Hovig `<ingvil.hovig@skatteetaten.no>`

- Jesper Holck`<jeh.inf@cbs.dk>`

- John Baldwin `<jhb@freebsd.org>`

- John Polstra `<jdp@freebsd.org>`

- Kirk McKusick `<mckusick@freebsd.org>`

- Mark Linimon `<linimon@freebsd.org>`

- Marleen Devos

- Niels Jørgenssen`<nielsj@ruc.dk>`

- Nik Clayton `<nik@freebsd.org>`

- Poul-Henning Kamp `<phk@freebsd.org>`

- Simon L. Nielsen `<simon@freebsd.org>`

### Notes

[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.

Prev | Home | Next
A project model for the FreeBSD Project |  | Overview

This, and other documents, can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/.

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.