Re: [gentoo-dev] Gentoo World Domination. a 10 step guide

[Simon Stelling]

Thomas Cort wrote:
> The number of opened bugs has always been higher than the number of
> closed bugs in the bug stats listed in every 2006 GWN. How is this
> 'going forward'? It seems to me like we are falling behind.

Take a closer look at the statistics. The numbers seem drastic, but once 
you've seen the queries behind them you know how to interprete them and 
things don't look that bad anymore.

>> > - Make every dev a member of at least 1 arch team
>>
>> Which doesn't mean he will ever keyword stuff stable, other than his
>> own, which he already can... Let's face it: most devs are mainly
>> interested in their stuff, getting their stuff keyworded, and many
>> wouldn't anyway have the time to efficiently work on an arch-team, as
>> members of such I mean, not just as "I'm a member, so I keyword my
>> stuff, that's it"... For that I agree with the current practice: if you
>> want that, ask the arch-team first. ;)
>
> Every developer should have access to at least 1 Gentoo system. They
> should also be able to determine if something is stable or not. It
> would cut down on the number of keyword/stable bugs if developers did
> a lot of their own keywording.

We had this model already, the x86 arch team did not always exist. We 
could revert to the old one, would be less bureaucratic. Would also take 
quite some load off the arch teams. Would also result in worse overall 
quality of the tree. *shrug*

>> > - Double the number of developers with aggressive recruiting
>>
>> That's something that goes on since... forever! Gentoo's continuously
>> recruiting new people, more aggressive recruiting has already been
>> proposed many times, but it was always agreed to try to maintain a
>> relatively high standard of new recruits, and if you want quality,
>> finding loads of people who "just happen" to have the time and
>> dedication to become a Gentoo dev isn't that easy.
>
> Even when someone is found it is hard for them to find mentors. We
> need to improve this. I had found someone who wanted to join the sound
> team and I was unable to locate a mentor for him (I wasn't a dev for 6
> months then, so I couldn't do it myself). I e-mailed sound@g.o and
> only one person offered. The person who offered fell through because
> he didn't have enough free time.
>
>> > - No competing projects
>>
>> Kills innovation... Who comes first has total monopoly of that branch of
>> things basically... I'd never agree to something like this, personally.
>
> What happened to working together? Should we work together instead of
> competing against each other?

Sometimes you want to achieve the same goal by totally different means. 
Sometimes there are good reasons for a complete new start. It does not 
even mean you don't communicate anymore. Brian Harring, although working 
on pkgcore which basically competes portage, communicates a lot with the 
portage team and vice versa, in a very productive manner. Nevertheless, 
you won't find anybody on the portage or pkgcore team saying that it 
would have been better to incorporate the ideas of pkgcore into portage. 
Sometimes it's simply better to start all over again.


-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 developer
-- 
gentoo-dev@g.o mailing list