Re: [gentoo-dev] rfc: stabilization policies

[Sergey Popov]

21.08.2013 13:13, Tom Wijsman пишет:
> On Wed, 21 Aug 2013 12:32:35 +0400
> Sergey Popov <pinkbyte@g.o> wrote:
>
>> 21.08.2013 12:13, Tom Wijsman пишет:
>>> Recruiting shows to be a hard task; so, the suggestions I am doing
>>> are assuming that that doesn't work out. In which case, I wonder
>>> what "by some other ways" you would think of...
>>
>> Dropping some keywords to unstable on minor arches.
>
> If we grow (like you said below), then doing less seems like a decision
> that we shouldn't take; it is rather about "doing it different" to use
> our resources in a better way. Crowd sourcing users is an option here...

What crowd sourcing do you talking about? We have Arch Tester for that.
Do you see vast interest in this initiative? I think not(thus, for major
arches we have some amount of testers, some of them are became
developers lately).
And if you want to move stabilization checks to unqualified users, then
it is way to nowhere.

> Came across three types of people already trying to find a mentee:
>
> 1. The first one doesn't want to go through the amount of time it takes;
>    this depends a bit on the queue, but it can take months.
>
> 2. The second one's interest to become a Gentoo Developer depends from
>    time to time; so, tries to start over and over to become one.
>
> 3. The third one writes a lot of ebuilds (and has an overlay that
>    looks like a gold mine), but there is a language barrier that keeps
>    the user from contributing; so, we take things slowly instead...
>
> 4. The fourth one leaves a message on IRC and quits before you return.
>
> 5. ...
>
> So, recruiting in the terms of "finding recruits" appears to be hard.
>

But, at my POV, it is only one way that we can improve current situation.

-- 
Best regards, Sergey Popov
Gentoo developer
Gentoo Desktop Effects project lead
Gentoo Qt project lead
Gentoo Proxy maintainers project lead