Committer's Guide

The FreeBSD Documentation Project

$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.223 2005/04/14 02:08:38 hrs Exp $

This document provides information for the FreeBSD committer community. All new committers should read this document before they start, and existing committers are strongly encouraged to review it from time to time.

[ Split HTML / Single HTML ]

Table of Contents
1 Administrative Details
2 Commit Bit Types
3 CVS Operations
4 Conventions and Traditions
5 Preferred License for New Files
6 Developer Relations
7 GNATS
8 Who's Who
9 SSH Quick-Start Guide
10 The FreeBSD Committers' Big List of Rules
11 Support for Multiple Architectures
12 Ports Specific FAQ
13 Perks of the Job
14 Miscellaneous Questions

1 Administrative Details

Main Repository Host	`ncvs.FreeBSD.org`
Login Methods	ssh(1), protocol 2 only
Main CVSROOT	`ncvs.FreeBSD.org:/home/ncvs` (although also see Section 3).
Main CVS Repository Meisters `<cvsadm@FreeBSD.org>`	Peter Wemm `<peter@FreeBSD.org>` and Mark Murray `<markm@FreeBSD.org>`, as well as Josef Karthauser `<joe@FreeBSD.org>` and Joe Marcus Clarke `<marcus@FreeBSD.org>` for `ports/`
Mailing Lists	FreeBSD doc/ developers mailing list, FreeBSD doc/ committer's mailing list; FreeBSD ports/ developers mailing list, FreeBSD ports/ committer's mailing list; FreeBSD src/ developers mailing list, FreeBSD src/ committer's mailing list. (Each project repository has its own -developers and -committers mailing lists. Archives for these lists may be found in files `/home/mail/repository-name-developers-archive` and `/home/mail/repository-name-committers-archive` on the `FreeBSD.org` cluster.)
Core Team monthly reports	`/home/core/public/monthly-report` on the `FreeBSD.org` cluster.
Noteworthy CVS Tags	`RELENG_4` (4.X-STABLE), `RELENG_5` (5.X-STABLE), `HEAD` (-CURRENT)

It is required that you use ssh(1) or telnet(1) with Kerberos 5 to connect to the project hosts. For ssh(1) only protocol 2 is allowed. These are generally more secure than plain telnet(1) or rlogin(1) since credential negotiation will always be encrypted. All traffic is encrypted by default with ssh(1). With utilities like ssh-agent(1) and scp(1) also available, ssh(1) is also far more convenient. If you do not know anything about ssh(1), please see Section 9.

		Next
		Commit Bit Types