Date: Sun, 18 Nov 2001 19:56:52 +0200 From: Giorgos Keramidas <charon@labs.gr> To: Paul Richards <paul@freebsd-services.com> Cc: Warner Losh <imp@harmony.village.org>, developers@FreeBSD.org, ports@FreeBSD.org, core@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: Portmgr duties expand Message-ID: <20011118175651.GB2600@hades.hell.gr> In-Reply-To: <688520000.1006087432@lobster.originative.co.uk> References: <200111180201.fAI21j757358@harmony.village.org> <688520000.1006087432@lobster.originative.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-11-18 12:43:52, Paul Richards wrote: > --On Saturday, November 17, 2001 19:01:45 -0700 Warner Losh > <imp@harmony.village.org> wrote: > > > > Core is pleased to announce that as of Tuesday, November 11, we've > > delegated the maintenance of the ports tree to the portsmgr team. > > They have been maintaining the infrastructure make system for a while > > now. To that list, we've added the ability to approve ports > > committers; to resolve disputes within the ports tree; and to generally > > manage the ports tree as appropriate. > > Will committers approved by the postmgr team be restricted to working in > the ports tree or will they have free reign as other committers do? > > What's the process for becoming a src or docs committer if you were > originally approved by portsmgr and not by core? I think that this boils down to the first question. Does a doc committer (like me) commit freely to the other parts of the tree? The answer is, unless I'm mistaken, `no, he goes through the usual test, review, diff, test again, review again' cycle that everyone else uses. If we need a formal procedure for 'expanding horizons', that will have to be similar to the way a contributor, who shows increasing interest and expertise in parts of the tree, becomes a committer. A mentor with experience to the relevant parts of the tree be assigned for some time, and take care of the new areas a committer is interested in. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011118175651.GB2600>