<div dir="ltr">Hi<div><br></div><div>(Note: be careful, you reply only to me and not to the ML)<br><div><div><br></div><div> - I don't want to give the power to a few people to do this selection. It will lead to bikeshed bitter arguments (why am I not included ? Why is Y included I don't think he should ? It can get very personal very quickly). Rock is not big enough to already start having an overseeing team. Let the coding decide.</div>
<div> - people that have committed a lot are the ones that know the codebase, so that is IMO the best people as a starting point</div><div> - this is an INITIAL list. Obviously, it will be updated over time. Now, I would NOT add anybody in there that did not already contribute a significant amount of code, simply because they are probably not familiar with the codebase (and therefore is not suited to decide what to push or not push there).</div>
<div><br></div><div>Sylvain</div><div><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 15, 2014 at 12:37 PM, Jakob Schwendner <span dir="ltr"><<a href="mailto:jakob.schwendner@dfki.de" target="_blank">jakob.schwendner@dfki.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">> Also, I don't agree with the last section. I would not want to rule who<br>
</div><div class="">> has committed the most in the dicision on who gets the rights.<br>
><br>
><br>
> I don't understand your last sentence ... Can you explain ?<br>
<br>
</div>In the text you suggest using the numbers on who commited the most to give out commit rights.<br>
Quantity is not quality, and I would argue its better to select these people. These decisions should come from a management team.<br>
<span class="HOEnZb"><font color="#888888"><br>
Jakob<br>
<br>
</font></span></blockquote></div><br></div>