Governance revisited

[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.

-- 
Troy Rollo - wine at troy.rollo.name