<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Steven Edwards</b> <<a href="mailto:winehacker@gmail.com">winehacker@gmail.com</a>><br>Date: Sep 25, 2006 1:27 AM
<br>Subject: Re: Governance revisited<br>To: Troy Rollo <<a href="mailto:wine@troy.rollo.name">wine@troy.rollo.name</a>><br><br></span><br><br><div><span class="q"><span class="gmail_quote">On 9/25/06, <b class="gmail_sendername">
Troy Rollo</b> <<a href="mailto:wine@troy.rollo.name" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wine@troy.rollo.name</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The present system turns people off even before you've had time to learn<br>whether they are capable or not.</blockquote></span><div><br>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.Z sucks and julliard most likely will not merge it.<br></div><br></div><div><span class="e" id="q_10de3714304dc4b4_3">-- <br>Steven Edwards<br><br>"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
</span></div><br clear="all"><br>-- <br>Steven Edwards<br><br>"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo