Legally this must be a fork then and I'm not sure it can be released as
official Zope Foundation software anymore if you make releases from GitHub.
Reason: the ZF can no longer ascertain that only official ZF contributor
agreement signers have modified code in the package, which is a core
requirement for software released from Zope Foundation repositories/under Zope
Apart from those legal points which are still not entirely clear, since this
can only be a fork I would say that last checkin must still be reverted. Don't
get me wrong, I'm not trying to be facetious, but until those legal questions
are cleared up you should not make any checkins on svn.zope.org that basically
"shut down" development of that package from there, such as deleting the trunk.
On Aug 18, 2012, at 10:21 , Hanno Schlichting <ha...@hannosch.eu> wrote:
> Please note that development of buildout 2 happens on github since April this
> year. The buildout developers decided to do the move after Jim suggested it.
> Legally you could see this move as a fork, but it was done by Jim and others.
> Alex just wanted to clarify the situation and also move the development of
> the stable branch into the same place.
> On 18.08.2012, at 09:49, Jens Vagelpohl <j...@dataflake.org> wrote:
>> Hi Alex,
>> Please revert this checkin. You can't just take core software pieces from
>> Zope Foundation-hosted repositories and move them somewhere else.
>> On Aug 18, 2012, at 3:09 , J. Alexander Clark <cvs-ad...@zope.org> wrote:
>>> Log message for revision 127519:
>>> Moved to github
>>> A zc.buildout/README_MOVED_TO_GITHUB.txt
>>> D zc.buildout/trunk/
>>> Added: zc.buildout/README_MOVED_TO_GITHUB.txt
>>> --- zc.buildout/README_MOVED_TO_GITHUB.txt (rev
>>> +++ zc.buildout/README_MOVED_TO_GITHUB.txt 2012-08-18 01:09:06 UTC (rev
>>> @@ -0,0 +1 @@
>>> checkins mailing list
>> Zope-Dev maillist - Zope-Dev@zope.org
>> ** No cross posts or HTML encoding! **
>> (Related lists -
>> https://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -