<div class="gmail_quote">On Sat, Nov 21, 2009 at 10:50 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@bleepbleep.org.uk">pmuir@bleepbleep.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
On 21 Nov 2009, at 14:15, Steven Boscarine wrote:<br>
<br>
> Works for me, personally.<br>
><br>
> As an outsider, it's obviously more friendly for non-JBoss employees<br>
> like me to contribute. I am still waiting on someone to tag those Weld<br>
> Maven archetypes I submitted so I can commit to trunk for review without<br>
> worrying about breaking anything. With git, that wouldn't be an issue.<br>
<br>
</div>You are welcome to tag whenever you want :-)<br>
<br>
But I agree, GIT supports distributed development much better.<br></blockquote><div><br>+1<br><br>I think this is amongst the most compelling reasons, perhaps even the most compelling. It was so simple for me to get involved with the maven-cli-plugin because it was hosted with git, and I want that same experience for developers getting involved with Seam and Weld.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>