Mike Auty kirjoitti:
Petteri Räty wrote:
Defining required amount of activity for ebuild devs. I would like us to raise the required amount of activity for ebuild devs.

Given that the low number of developers is ranked as our number one problem in Donnie's informal survey[1], taking any kind of action against infrequently-committing developers is likely to reduce the number of devs we have, and potentially make the problem worse.

What benefits are you aiming to get from the suggestion? I can think og keeping the books tidy and reducing management time required to maintain the devs. Are there others I've missed? If they're worth the cost/effort involved with putting someone through the dev tests and getting them trained, then it seems a good idea, but otherwise probably not...

Mike  5:)

[1] http://dberkholz.wordpress.com/2008/02/21/redux-gentoos-top-3-issues/

If you can't manage weekly commits, you can't respond to security issues either. This means that you should have devaway on.

Regards,
Petteri

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to