Date: Mon, 10 Nov 2003 12:25:59 -0800 From: Eric Anholt <eta@lclark.edu> To: Will Andrews <will@csociety.org> Cc: freebsd-ports@freebsd.org Subject: Re: Ability for maintainers to update own ports Message-ID: <1068495958.690.72.camel@leguin> In-Reply-To: <20031110163623.GC93583@procyon.firepipe.net> References: <1068458390.38101.19.camel@dirk.no.domain> <20031110152000.622db381.lehmann@ans-netz.de> <1068471598.38101.77.camel@dirk.no.domain> <20031110163623.GC93583@procyon.firepipe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2003-11-10 at 08:36, Will Andrews wrote: > On Tue, Nov 11, 2003 at 12:39:58AM +1100, Sam Lawrance wrote: > > I guess that's one of the challenges to be dealt with. Having briefly > > examined nbsd's pkgsrc-wip I think it is a good source of QA. I would > > like to combine this with a better way of channeling changes back into > > the tree. Best of both worlds - faster/wider distribution of new > > changes, larger base of reviewers. > > > > But you are right - anything that lowers the quality of the ports tree > > would be an absolute no-go. > > Sorry, but if you are unhappy with the speed at which ports get > updated, become a regular and you'll get a commit bit. It's just > that simple. For most maintainers it's not worth the effort > because practice makes a better porter. One thing I've wondered about, though, is the process for people getting commit bits. Is it always on the initiative of an existing committer (as it was in my case) or would it be considered acceptable for people who would like to become committers and maintain their ports directly to propose themselves on a list for someone to pick them up as a new committer? -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1068495958.690.72.camel>