Governance revisited

[Steven Edwards]

---------- Forwarded message ----------
From: Steven Edwards 
Date: Sep 25, 2006 1:27 AM
Subject: Re: Governance revisited
To: Troy Rollo

On 9/25/06, Troy Rollo  wrote:
> The present system turns people off even before you've had time to learn
> whether they are capable or not.

Which is why we want to have the ambassadors project to help new people in
to wine. The thinking goes that if we have some people to help hold the
hands of new developers and the developers that are defacto maintainers of a
certain section of code will respond to patches as they seem them, this will
free julliard from having to answer every single patch with a reply. Now in
the case of Ge where he was patching core functions of
ntdll,kernel32,wineserver,etc I guess it would still fall to julliard to
reply personally but in the case of other modules the experts in that area
should take a step up and monitor wine-patches and say what patch
X.Y.Zsucks and julliard most likely will not merge it.

[Troy Rollo]

On Monday 25 September 2006 15:27, Steven Edwards wrote:
> Which is why we want to have the ambassadors project to help new people in
> to wine. ... if... the developers that are defacto maintainers of
> a certain section of code will respond to patches as they seem them...
> the experts in that area should take a step up and monitor wine-patches and
> say what patch X.Y.Zsucks and julliard most likely will not merge it.this
> will free julliard from having to answer every single patch with a reply.

So when it comes to code, everything must be done exactly the "right" way, but 
when it comes to process defects, we're happy to hack around them? :-)

Presumably nobody who's gratuitously abusive would be counted among those 
experts since it's not helpful to get "feedback" from somebody who's in a 
truckload of filters.
> Now in the case of Ge where he was patching core functions of
> ntdll,kernel32,wineserver,etc I guess it would still fall to julliard to
> reply personally but in the case of other modules

It's also remains a haphazard process where things can (and so will) fall 
through the cracks.