<p dir="ltr">Antoine,</p>
<p dir="ltr">Why do only some EG members have access to merge PRs?</p>
<div class="gmail_quote">On May 3, 2016 9:44 AM, "Antoine Sabot-Durand" <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi guys,<div><br></div><div>As you know we plan to release CDI 2.0 before the end of January. It let's us around 6 months to complete the spec.</div><div><br></div><div>I think we really should find a way to enhance our focus on reviewing proposal and code.</div><div>Adding special Hangout meetings proved itself a good solution to go that way, but I think we should also work on rules adoption for PR.</div><div><br></div><div>So I propose that:</div><div>- PR should stay open at least one week.</div><div>- It could be merged (after at least a week) if 4 EG members votes for it (+1 on the PR).</div><div>- As no one is error proof if someone has an objection to a PR to be merged he could raise his concern and justify his objection.</div><div>- The following discussion should lead either to a revision of the PR or a +1 from the objector</div><div>- If no agreement is reached, to avoid blocage a vote will be called on this ML to adopt or reject the PR. </div><div><br></div><div>I'm not a big fan of over processed team work, but we really have to deliver.<span style="line-height:1.5"> </span></div><div>For the moment I think we can avoid having too much process on ticket choice (we don't have enough contributors to go that way)</div><div><br></div><div>Wdyt ?</div><div><br></div><div>Antoine</div></div>
<br>_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br></blockquote></div>