Date: Sun, 17 Jun 2001 10:31:19 +0100 From: Nik Clayton <nik@FreeBSD.org> To: Warner Losh <imp@harmony.village.org>, doc@freebsd.org Subject: Re: Updates to committer's guide for getting commit bits. Message-ID: <01061710311913.01838@clan.nothing-going-on.org> In-Reply-To: <200106170542.f5H5gsV44690@harmony.village.org> References: <200106170542.f5H5gsV44690@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 17 June 2001 6:42 am, Warner Losh wrote: > Please find enclosed the first set of patches updating the commiter's > guide to reflect the current policy on obtaining one's commit. Excellent. More documentation. I'll buy you a beer at Usenix. I see Dima's already made some comments, so I won't duplicate them. A few extra bits. > + <sect1 id="new.committer"> id="new-committer" Oh look, my MUA has screwed up the quoting. > + <para>If the commit bit is for src, send your request (and > justification) + to <email>core@FreeBSD.org</email>. If the commit > bit is for ports, + send your request to &a.asami;. If the commit > bit is for doc, send + your request to &a.nik;. The mentor for this > new person should make + the request. You should get an ack of your > request > + back within 24 hours. You should get resolution of your request, > + one way or another within one week. If you fail to get these > things + in a timely fashion, then write to core.</para> Ha ha ha ha ha ha. You should get an ack in 48 to 72 hours, depending on how busy they are, and whether or not real life has taken them away from e-mail. If you don't, feel free to send a followup reminder. FWIW, I also pass commit bit requests through -core. It's never happened yet, but it's feasible that someone might have played well on -doc, but have been a pain in the arse on -net, or -ports, or whatever. Adding in a few more eyeballs doesn't significantly slow the process down, and if -core don't respond I take that as being "no objection". > + <para>If you are a doc committer, you can commit to both the src > + and doc trees. But only to documentation in the src tree. > + Otherwise, you should get approval from the issuing authority > + to start making commits outside of the area for which you > + were originally approved.</para> Ditto for ports? Perhaps: [...] If you were bought in to commit to the doc/ or ports/ trees then you should not, in general, commit to the src/ tree (save for documentation fixes). If you want to commit to the src/ tree as well you must agree this with your mentor (or find an additional mentor if mentor #1 is not a src/ committer), who must pass this by -core as well. [...] N - -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsseOcACgkQk6gHZCw343VERQCcDNUwwywtA11apll7B+BqPCJ6 cIoAoI6r9JNhx0r0cJm19r8+3DuuaV6q =76LS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01061710311913.01838>