<br><br><div class="gmail_quote">On 19 August 2012 08:00, Jens Vagelpohl <span dir="ltr"><<a href="mailto:jens@dataflake.org" target="_blank">jens@dataflake.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Aug 19, 2012, at 3:58 , Alex Clark <<a href="mailto:aclark@aclark.net">aclark@aclark.net</a>> wrote:<br>
<br>
> IANAL but from my perspective the legitimate issue here is that Domen Kožar has not signed the Zope Contributor's Agreement, but Jim has added him to the Buildout organization on GitHub and he has been committing fixes. If I were the ZF, I would either:<br>
><br>
> - Make sure everyone in any ZF organizations on GitHub (e.g. buildout) has signed the contributor agreement, or<br>
> - Declare that nothing on GitHub (or at least in the buildout organization) is a valid contribution to "the work".<br>
><br>
> In either case, AFAICT zc.buildout development has stopped on <a href="http://svn.zope.org" target="_blank">svn.zope.org</a> and started on GitHub so let us let the commit stand to reflect this real world circumstance.<br>
<br>
</div>Right now it can only be the second option. There's no "ZF organization" on GitHub. Legally, the zc.buildout fork now existing on GitHub is independent of the ZF, and the developers maintaining it are acting independent of the ZF. Don't get me wrong, they have every right to do so. But right now they cannot claim their software as being part of the Zope Foundation set of software. The same is true for all packages forked onto GitHub that were maintained on <a href="http://svn.zope.org" target="_blank">svn.zope.org</a> before.<br>
</blockquote><div><br></div><div>It may be useful for the sake of this thread to articulate why the people who did fork it and move it to GitHub might benefit from the above.</div><div><br></div><div>Martin</div></div>