public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* [gentoo-dev] Re: ML changes
@ 2007-07-13 20:39 99% Simon Cooper
  0 siblings, 0 replies; 1+ results
From: Simon Cooper @ 2007-07-13 20:39 UTC (permalink / raw
  To: gentoo-dev

As another invisible AT, theres a couple of points I want to make about 
blanket blacklisting:

1. gentoo-dev has an outside image. The current, anyone-can-post, 
projects the image that the developers are happy to receive outside 
opinions that may be different to 'how things are done'. This is, 
mostly, a good thing. More ideas can only improve the technical quality 
of gentoo, even if those ideas are discarded. Moderating -dev will only 
reinforce the image of cliquiness within the developers. This is bad.
2. It will kill recruitment. This point has been made before, iirc.
3. A dilbert quote (paraphrase?) comes to mind - 'Something must be 
done. This is something, so we must do it'

Personally, I agree with ttuttle's idea about being able to whitelist 
non-devs - a blanket blacklist is simply not the way to do it - people 
do not have to be developers to contribute to gentoo. I can also see the 
benefit of introducing -project and waiting to see what happens. When 
you introduce lots of changes to a software project at once, and 
something breaks, you do not know what broke it. It pays to introduce 
things one at a time and testing between. The same can be applied here.

Simon Cooper

-- 
Change the world - move a rock

GnuPG Key: http://thecoop.me.uk/gpgkey.asc
-- 
gentoo-dev@gentoo.org mailing list



^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2007-07-13 20:39 99% [gentoo-dev] Re: ML changes Simon Cooper

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox