7 Who's Who

John is the manager of the SMPng Project, and has authority over the architectural design and implementation of the move to fine-grained kernel threading and locking. He's also the editor of the SMPng Architecture Document. If you are working on fine-grained SMP and locking, please coordinate with John. You can learn more about the SMPng Project on its home page: http://www.FreeBSD.org/smp/

Jake and Thomas are the maintainers of the sparc64 hardware port.

Nik oversees the Documentation Project. As well as writing documentation he put together the infrastructure under doc/share/mk and the stylesheets and related code under doc/share/sgml. If you have questions about these you are encouraged to send them via the FreeBSD documentation project mailing list <freebsd-doc@FreeBSD.org>. Committers interested in contributing to the documentation should familiarize themselves with the Documentation Project Primer.

Ruslan is Mister mdoc(7). If you are writing a manual page and need some advice on the structure, or the markup, ask Ruslan.

Bruce is the Style Police-Meister. When you do a commit that could have been done better, Bruce will be there to tell you. Be thankful that someone is. Bruce is also very knowledgeable on the various standards applicable to FreeBSD.

These are the primary developers and overseers of the DEC Alpha AXP platform.

David is the overseer of the VM system. If you have a VM system change in mind, coordinate it with David.

These are the primary developers and overseers of the Intel IA-64 platform, officially known as the Itanium Processor Family (IPF).

These are the members of the Release Engineering Team <re@FreeBSD.org>. This team is responsible for setting release deadlines and controlling the release process. During code freezes, the release engineers have final authority on all changes to the system for whichever branch is pending release status. If there is something you want merged from FreeBSD-CURRENT to FreeBSD-STABLE (whatever values those may have at any given time), these are the people to talk to about it.

Bruce is also the keeper of the release documentation (src/release/doc/*). If you commit a change that you think is worthy of mention in the release notes, please make sure Bruce knows about it. Better still, send him a patch with your suggested commentary.

Benno is the official maintainer of the PowerPC port.

Official maintainer of /usr/sbin/ppp.

Jacques is the FreeBSD Security Officer and oversees the Security Officer Team <security-officer@FreeBSD.org>.

If you need advice on obscure network internals or are not sure of some potential change to the networking subsystem you have in mind, Garrett is someone to talk to. Garrett is also very knowledgeable on the various standards applicable to FreeBSD.

cvs-committers is the entity that CVS uses to send you all your commit messages. You should never send email directly to this list. You should only send replies to this list when they are short and are directly related to a commit.

All committers are subscribed to -developers. This list was created to be a forum for the committers ``community'' issues. Examples are Core voting, announcements, etc. This list is not intended as a place for code reviews or a replacement for the FreeBSD architecture and design mailing list <freebsd-arch@FreeBSD.org> or the FreeBSD source code audit mailing list <freebsd-audit@FreeBSD.org>. In fact using it as such hurts the FreeBSD Project as it gives a sense of a closed list where general decisions affecting all of the FreeBSD using community are made without being ``open''. Last, but not least never, never ever, email the FreeBSD developers mailing list <freebsd-developers@FreeBSD.org> and CC:/BCC: another FreeBSD list. Never, ever email another FreeBSD email list and CC:/BCC: the FreeBSD developers mailing list <freebsd-developers@FreeBSD.org>. Doing so can greatly diminish the benefits of this list. Also, never publicly post or forward emails sent to the FreeBSD developers mailing list <freebsd-developers@FreeBSD.org>. The act of sending to the FreeBSD developers mailing list <freebsd-developers@FreeBSD.org> vs. a public list means the information in the email is not for public consumption.