On Wed, 19 Dec 2012 07:56:56 +0100 Jeroen Roovers <j...@gentoo.org> wrote:
> On Mon, 17 Dec 2012 10:40:06 +0100 > Michał Górny <mgo...@gentoo.org> wrote: > > > > People aren't bothering. It's not because of any fundamental > > > problem -- it's because the process is obscure and potentially a > > > waste of time. > > > > I agree with that. The process takes a lot of time for a minor > > benefit, and most of it doesn't prove really helpful. I think the > > process should mostly prove that someone is able to find and read > > docs, write ebuilds and understand the major concepts. > > Please show me some numbers that prove your point about the recruitment > process > having "little benefit". Opinions don't come with numbers. > > Honestly, I see no reason to ask recruits for a lot of things we do > > right now. There's no point in telling them to summarize a large piece > > of the docs. From my personal experience, there is a lot of things > > which you learn and then forget because you don't need them for a > > long time. > > I could go all cynical here and give a few examples of how a couple of people > recently got through and actually managed to mess up a few very basic > things you would never contemplate quizzing them about. > > But I would much rather see to it that those few bits get fixed, rather than > the even greater mess we would be in if everybody with the "right mindset" got > commit privileges. Since nobody's perfect, we already have enough work to do, > thank you. Doesn't this prove that the recruitment process fails to work? If I were to throw random ideas, I'd think about letting new recruits did all commits through a proxy (mentor?). Of course, it all would be easier if we used git. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
