A project model for the FreeBSD Project

Niklas Saers

Copyright © 2002-2005 Niklas Saers

[ Split HTML / Single HTML ]
Table of Contents
Foreword
1 Overview
2 Definitions
2.1. Activity
2.2. Process
2.3. Hat
2.4. Outcome
2.5. FreeBSD
3 Organisational structure
4 Methodology model
4.1. Development model
4.2. Release branches
4.3. Model summary
5 Hats
5.1. General Hats
5.1.1. Contributor
5.1.2. Committer
5.1.3. Core Team
5.1.4. Maintainership
5.2. Official Hats
5.2.1. Documentation project manager
5.2.2. CVSup Mirror Site Coordinator
5.2.3. Internationalisation
5.2.4. Postmaster
5.2.5. Quality Assurance
5.2.6. Release Coordination
5.2.7. Public Relations & Corporate Liaison
5.2.8. Security Officer
5.2.9. Source Repository Manager
5.2.10. Election Manager
5.2.11. Web site Management
5.2.12. Ports Manager
5.2.13. Standards
5.2.14. Core Secretary
5.2.15. GNATS Administrator
5.2.16. Bugmeister
5.2.17. Donations Liaison Officer
5.2.18. Admin
5.3. Process dependent hats
5.3.1. Report originator
5.3.2. Bugbuster
5.3.3. Mentor
5.3.4. Vendor
5.3.5. Reviewers
5.3.6. CVSup Mirror Site Admin
6 Processes
6.1. Adding new and removing old committers
6.2. Adding/Removing an official CVSup Mirror
6.3. Committing code
6.4. Core election
6.5. Development of new features
6.6. Maintenance
6.7. Problem reporting
6.8. Reacting to misbehaviour
6.9. Release engineering
7 Tools
7.1. Concurrent Versions System (CVS)
7.2. CVSup
7.3. GNATS
7.4. Mailman
7.5. Perforce
7.6. Pretty Good Privacy
7.7. Secure Shell
8 Sub-projects
8.1. The Ports Subproject
8.2. The FreeBSD Documentation Project
References
List of Figures
3-1. The FreeBSD Project's structure
3-2. The FreeBSD Project's structure with committers in categories
4-1. Jørgenssen's model for change integration
4-2. The FreeBSD release tree
4-3. The overall development model
5-1. Overview of official hats
6-1. Process summary: adding a new committer
6-2. Process summary: removing a committer
6-3. Process summary: adding a CVSup mirror
6-4. Process summary: A committer commits code
6-5. Process summary: A contributor commits code
6-6. Process summary: Core elections
6-7. Jørgenssen's model for change integration
6-8. Process summary: problem reporting
6-9. Process summary: release engineering
8-1. Number of ports added between 1996 and 2005
    Next
    Foreword