4 Conventions and Traditions

As a new committer there are a number of things you should do first.

• Add your author entity to doc/en_US.ISO8859-1/share/sgml/authors.ent; this should be done first since an omission of this commit will cause the next commits to break the doc/ build.

  This is a relatively easy task, but remains a good first test of your CVS skills.

• Add yourself to the “Developers” section of the Contributors List and remove yourself from the “Additional Contributors” section.

• Add an entry for yourself to www/en/news/news.xml. Look for the other entries that look like “A new committer” and follow the format.

• You should add your PGP or GnuPG key to doc/share/pgpkeys (and if you do not have a key, you should create one). Do not forget to commit the updated doc/share/pgpkeys/pgpkeys.ent.

  Dag-Erling C. Smørgrav <des@FreeBSD.org> has written a shell script to make this extremely simple. See the README file for more information.

  Note: It is important to have an up-to-date PGP/GnuPG key in the Handbook, since the key may be required for positive identification of a committer, e.g. by the FreeBSD Administrators <admins@FreeBSD.org> for account recovery. A complete keyring of FreeBSD.org users is available for download from http://www.FreeBSD.org/doc/pgpkeyring.txt.

• Some people add an entry for themselves to ports/astro/xearth/files/freebsd.committers.markers.

• Some people add an entry for themselves to src/usr.bin/calendar/calendars/calendar.freebsd.

• Introduce yourself to the other committers, otherwise no one will have any idea who you are or what you are working on. You do not have to write a comprehensive biography, just write a paragraph or two about who you are and what you plan to be working on as a committer in FreeBSD. Email this to the FreeBSD developers mailing list and you will be on your way!

• Log into hub.FreeBSD.org and create a /var/forward/user (where user is your username) file containing the e-mail address where you want mail addressed to yourusername@FreeBSD.org to be forwarded. This includes all of the commit messages as well as any other mail addressed to the FreeBSD committer's mailing list and the FreeBSD developers mailing list. Really large mailboxes which have taken up permanent residence on hub often get “accidentally” truncated without warning, so forward it or read it and you will not lose it.

  Due to the severe load dealing with SPAM places on the central mail servers that do the mailing list processing the front-end server does do some basic checks and will drop some messages based on these checks. At the moment proper DNS information for the connecting host is the only check in place but that may change. Some people blame these checks for bouncing valid email. If you want these checks turned off for your email you can place a file named ~/.spam_lover in your home directory on freefall.FreeBSD.org to disable the checks for your email.

• If you are subscribed to the FreeBSD CVS commit message mailing list, you will probably want to unsubscribe to avoid receiving duplicate copies of commit messages and their followups.

All new committers also have a mentor assigned to them for the first few months. Your mentor is responsible for teaching you the rules and conventions of the project and guiding your first steps in the committer community. He or she is also personally responsible for your actions during this initial period. Until your mentor decides (and announces with a forced commit to access) that you have learned the ropes and are ready to commit on your own, you should not commit anything without first getting your mentor's review and approval, and you should document that approval with an Approved by: line in the commit message.

All src commits should go to FreeBSD-CURRENT first before being merged to FreeBSD-STABLE. No major new features or high-risk modifications should be made to the FreeBSD-STABLE branch.