| 1 |
On Mon, 17 Dec 2012 10:40:06 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> > People aren't bothering. It's not because of any fundamental |
| 5 |
> > problem -- it's because the process is obscure and potentially a |
| 6 |
> > waste of time. |
| 7 |
> |
| 8 |
> I agree with that. The process takes a lot of time for a minor |
| 9 |
> benefit, and most of it doesn't prove really helpful. I think the |
| 10 |
> process should mostly prove that someone is able to find and read |
| 11 |
> docs, write ebuilds and understand the major concepts. |
| 12 |
|
| 13 |
Please show me some numbers that prove your point about the recruitment process |
| 14 |
having "little benefit". |
| 15 |
|
| 16 |
> Honestly, I see no reason to ask recruits for a lot of things we do |
| 17 |
> right now. There's no point in telling them to summarize a large piece |
| 18 |
> of the docs. From my personal experience, there is a lot of things |
| 19 |
> which you learn and then forget because you don't need them for a |
| 20 |
> long time. |
| 21 |
|
| 22 |
I could go all cynical here and give a few examples of how a couple of people |
| 23 |
recently got through and actually managed to mess up a few very basic |
| 24 |
things you would never contemplate quizzing them about. |
| 25 |
|
| 26 |
But I would much rather see to it that those few bits get fixed, rather than |
| 27 |
the even greater mess we would be in if everybody with the "right mindset" got |
| 28 |
commit privileges. Since nobody's perfect, we already have enough work to do, |
| 29 |
thank you. |
| 30 |
|
| 31 |
|
| 32 |
jer |
Archives