<div>I'm all for it. I submitted a few pull requests to jbpm in the past and I think it's the best way forward.</div><div><br></div><div>Cheers,</div><div><br></div><div>Antoine<br><br><div class="gmail_quote">On Tue, May 10, 2011 at 01:56, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We've been monitoring github over the last few weeks. Github now makes<br>
it trivial for people to work in their own forks and submit pull<br>
requests. We have found that from time to time people don't rebase<br>
properly or check their commits after a push, and thus end up<br>
overwritting other people's work. We are thinking of trialing the<br>
leuitenant model for a while, where just core people are responsible for<br>
accepting and applying pull requests. With git's distributedd model,<br>
this should hopefully work out well.<br>
<br>
So from this point on, unless you are a core developer responsible for a<br>
specific module, can I ask that you submit pull requests for future work?<br>
<br>
thanks<br>
<br>
Mark<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></div><br></div>