Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
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. Hanno 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. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Hanno, 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 Foundation auspices. 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. jens 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. Hanno 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. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On 2012-8-18 10:39, Jens Vagelpohl wrote: Hi Hanno, 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. Doesn't the name zc.buildout imply that it is a Zope Corp project instead of a Zope Foundation one? The author has also never been listed as the foundation but Jim personally, which seems to imply zc.buildout never was Zope Foundation-owned software. Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Sat, Aug 18, 2012 at 6:46 AM, Wichert Akkerman wich...@wiggy.net wrote: Doesn't the name zc.buildout imply that it is a Zope Corp project instead of a Zope Foundation one? The author has also never been listed as the foundation but Jim personally, which seems to imply zc.buildout never was Zope Foundation-owned software. Jim *wrote* the software (and is therefore the author, regardless of who *owns* it), and gave it to the Zope Foundation under his contributor's agreement. Therefore, the Foundation and Zope Corporation both have equal ownership stakes. -Fred -- Fred L. Drake, Jr.fdrake at acm.org A person who won't read has no advantage over one who can't read. --Samuel Langhorne Clemens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi, I approve your position Jens. Moving to git can make sense. Moving to github as primary platform does not make sense. Github is a proprietary platform. There is really no justification in using a proprietary platform for open source projects, especially considering that many open source alternatives exist and that nothing prevents from using github as a mirror (for marketing purpose for example). It is not only depressing to see open source communities not eating their own dog food but also irresponsible. It is irresponsible because Cloud / SaaS is far from reliable. Please read this to get an idea. (http://iwgcr.org/paris-university-and-telecom-paristech-publish-availability-ranking-of-world-cloud-computing/). Service outages are not rare. It is irresponsible because it sends a message to the market that open source is not competitive (else open source communities would use it for themselves). Many open source git hosting solutions do exist (incl. gitorious, gitlab, indefero). Why not use them ? On a more positive side, Nexedi is currently sponsoring the port of Gitlab (http://gitlabhq.com/) open source git platform to SlapOS ( http://www.slapos.org/) open source Cloud. This means that there will in a few days a python based, Zope based, buildout based and fully resilient platform to host open source projects, with the ability to manage copies of source code on servers all around the world in a true community fashion. And after reading today's message, I got so upset that I decided that Nexedi will use SlapOS to offer hosting to any open source Zope community project which believes enough in open source values to use open source tools rather than proprietary ones. This will include free support to any open source Zope project willing to manage its own SlapOS platform rather rely on ours. Let us see if Zope community will be the first or the last to eat its own dog food ;-). Regards, JPS. Nexedi CEO PS. I do not mind behind hated for using the word irresponsible, whooever took the decision to use github. I do mean it. Le 18/08/2012 09:49, Jens Vagelpohl a écrit : Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clarkcvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt 2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist -Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Jens, On 18/08/2012 09:39, Jens Vagelpohl wrote: 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, Actually, with the cryptographically signed nature of git commits, I'm not sure this is true... which is a core requirement for software released from Zope Foundation repositories/under Zope Foundation auspices. Well, I guess releases would be made outside of these auspices then, whatever that means... The license looks the same, the same people are doing the development. Quite frankly, given the hard time we have getting people to help out, anything that eases that can only be a good thing. Chris McDonough and the rest of the Pyramid folk seem happy enough with the GitHub model, and I've found it's made life very much easier for the python-excel project and the other packages I maintain. 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. No history has been destroyed, it's just a clear marker of where active development is happening. That said, I don't have a strong opinion on this, I'd suggest Jim just makes the call... cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
I'm not going to dignify this with a fuller response other than to say that Jean-Paul Smets' entire email is nothing but bullshit written to try and promote an inferior competing product ;-) Chris On 18/08/2012 13:31, Jean-Paul Smets wrote: Hi, I approve your position Jens. Moving to git can make sense. Moving to github as primary platform does not make sense. Github is a proprietary platform. There is really no justification in using a proprietary platform for open source projects, especially considering that many open source alternatives exist and that nothing prevents from using github as a mirror (for marketing purpose for example). It is not only depressing to see open source communities not eating their own dog food but also irresponsible. It is irresponsible because Cloud / SaaS is far from reliable. Please read this to get an idea. (http://iwgcr.org/paris-university-and-telecom-paristech-publish-availability-ranking-of-world-cloud-computing/). Service outages are not rare. It is irresponsible because it sends a message to the market that open source is not competitive (else open source communities would use it for themselves). Many open source git hosting solutions do exist (incl. gitorious, gitlab, indefero). Why not use them ? On a more positive side, Nexedi is currently sponsoring the port of Gitlab (http://gitlabhq.com/) open source git platform to SlapOS ( http://www.slapos.org/) open source Cloud. This means that there will in a few days a python based, Zope based, buildout based and fully resilient platform to host open source projects, with the ability to manage copies of source code on servers all around the world in a true community fashion. And after reading today's message, I got so upset that I decided that Nexedi will use SlapOS to offer hosting to any open source Zope community project which believes enough in open source values to use open source tools rather than proprietary ones. This will include free support to any open source Zope project willing to manage its own SlapOS platform rather rely on ours. Let us see if Zope community will be the first or the last to eat its own dog food ;-). Regards, JPS. Nexedi CEO PS. I do not mind behind hated for using the word irresponsible, whooever took the decision to use github. I do mean it. Le 18/08/2012 09:49, Jens Vagelpohl a écrit : Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clarkcvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt 2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist -Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Am 18.08.2012, 15:35 Uhr, schrieb Chris Withers ch...@simplistix.co.uk: I'm not going to dignify this with a fuller response other than to say that Jean-Paul Smets' entire email is nothing but bullshit written to try and promote an inferior competing product. The issues of hosting and vcs were aired a few months ago and should be considered separately. The TC's of any of the these products should be read carefully and I, for one, do not like the indemnification clause at Github. I would, therefore, agree with Jean-Paul in this respect. I agree with Jens, that new work should be considered as a fork. It currently feels very much cloak dagger. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Sat, Aug 18, 2012 at 10:39 AM, Jens Vagelpohl j...@dataflake.org wrote: 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 Foundation auspices. Is this because of the support for merging pull requests? Is that really legally different than a contributor making a merge from a patch? //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 12:46 , Wichert Akkerman wich...@wiggy.net wrote: On 2012-8-18 10:39, Jens Vagelpohl wrote: Hi Hanno, 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. Doesn't the name zc.buildout imply that it is a Zope Corp project instead of a Zope Foundation one? The author has also never been listed as the foundation but Jim personally, which seems to imply zc.buildout never was Zope Foundation-owned software. Hi Wichert, Clearly, Jim is the father of that software and it has been developed in large part for Zope Corporation, hence the name zc.buildout. However, that's not all there is to ownership of code on svn.zope.org. If you read the contributor agreements[1] all committers to svn.zope.org signed, submitting code to svn.zope.org also meant you entered into a legal agreement with the Zope Foundation regarding that code. Code submitted to svn.zope.org is from that moment on half-owned by the Zope Foundation. That means you cannot unilaterally just declare code removed from svn.zope.org, which is my point about the last checkin to the zc.buildout package. Everyone is free to fork code. But removing stuff from svn.zope.org requires approval from you as the original owner *and* the ZF as legal co-owner of anything stored on svn.zope.org. Caveat: I'm not a lawyer, that's just how I interpret the contributor agreement. jens [1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 14:31 , Jean-Paul Smets j...@nexedi.com wrote: Hi, I approve your position Jens. Moving to git can make sense. Moving to github as primary platform does not make sense. Hi Jean-Paul, Technical pros and cons are valid arguments, correct, but that wasn't my point here. I'm trying to look at the contractual issues involved, that's all. I'm not saying only platform X is acceptable, just that right now I only have proof that our self-hosted Subversion repositories on svn.zope.org appear to meet all the legal requirements laid out by the contributor agreements and the role of the Zope Foundation as the guard of these contributions as well as contributors' private data held by the Zope Foundation. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 15:46 , Lennart Regebro rege...@gmail.com wrote: On Sat, Aug 18, 2012 at 10:39 AM, Jens Vagelpohl j...@dataflake.org wrote: 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 Foundation auspices. Is this because of the support for merging pull requests? Is that really legally different than a contributor making a merge from a patch? Hi Lennart, The contributor agreement requires you as the contributor to be able to enter into the contract with the Zope Foundation transferring one half ownership to the Zope Foundation. You can only enter into this contract if you own (as in wrote) the code yourself - you cannot assign ownership to someone else for something you don't fully own. The goal of these contractual requirements is to make sure software stored in the Zope Foundation is as clean as possible from an ownership standpoint. People who use code from svn.zope.org have a reasonable assurance that no third party will show up on your doorstep demanding money or license fees for code that third party claims to own. I've just recently seen what can happen for projects not following this kind of strict policy: The python-ldap package developers are unable to e.g. assign a new license to their code because since they don't hold any ownership and would need to ask every single developer who ever touched that code - an impossible task. For us that kind of issue does not arise. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/18/2012 03:46 PM, Lennart Regebro wrote: On Sat, Aug 18, 2012 at 9:36 PM, Jens Vagelpohl j...@dataflake.org wrote: The contributor agreement requires you as the contributor to be able to enter into the contract with the Zope Foundation transferring one half ownership to the Zope Foundation. You can only enter into this contract if you own (as in wrote) the code yourself - you cannot assign ownership to someone else for something you don't fully own. The goal of these contractual requirements is to make sure software stored in the Zope Foundation is as clean as possible from an ownership standpoint. People who use code from svn.zope.org have a reasonable assurance that no third party will show up on your doorstep demanding money or license fees for code that third party claims to own. I've just recently seen what can happen for projects not following this kind of strict policy: The python-ldap package developers are unable to e.g. assign a new license to their code because since they don't hold any ownership and would need to ask every single developer who ever touched that code - an impossible task. For us that kind of issue does not arise. Yes, but my question is why this changes with github. Because the ability to check into svn.zope.org is based on a chain of custody managed by the ZF (web account, verified e-mail address, and SSH key). J. Random Hacker's account on Github has no such chain. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAwAwgACgkQ+gerLs4ltQ7/wwCgpdrjdb1ER6P7FS3lqO91FlwO ucQAnRpbKzABEIXDrDg5vsgJcCxz7DNX =0tGk -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/18/2012 03:18 PM, Jens Vagelpohl wrote: But removing stuff from svn.zope.org requires approval from you as the original owner *and* the ZF as legal co-owner of anything stored on svn.zope.org. Actually, it requires the permission of the ZF. The original owner has no more say in it than any other contributor: her rights are purely to incorporate forks (of her contributions) into non-ZPL'ed software. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAwA6wACgkQ+gerLs4ltQ4l+wCgxrYPGdrpBDnlts3Vp1D4wDDp 6+UAoKf8hEYjQOTwfzGmHGMkjZS1bgNy =pWcR -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Jens, On 2012-08-18 07:49:59 +, Jens Vagelpohl said: Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! I think you are confused. I would suggest you ask Jim Fulton about it, as he moved Buildout to GitHub months ago. Both 1.6.x and 2.x are under active development there. Further, I committed the *message* about the move and I removed trunk to avoid confusion, I didn't personally move anything (Jim moved 2.x and Domen Kožar moved trunk to the 1.6.x branch). Also please see the distutils-sig list for more information about recent zc.buildout 1.6.x development. Alex jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt 2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- Alex Clark · http://pythonpackages.com ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi On 2012-08-18 22:01:51 +, Alex Clark said: Hi Jens, On 2012-08-18 07:49:59 +, Jens Vagelpohl said: Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! I think you are confused. I would suggest you ask Jim Fulton about it, as he moved Buildout to GitHub months ago. Both 1.6.x and 2.x are under active development there. Further, I committed the *message* about the move and I removed trunk to avoid confusion, I didn't personally move anything (Jim moved 2.x and Domen Kožar moved trunk to the 1.6.x branch). Also please see the distutils-sig list for more information about recent zc.buildout 1.6.x development. And… sorry. Using a new client and I missed the ongoing thread :-) Alex Alex jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: 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 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt 2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- Alex Clark · http://pythonpackages.com ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 114, OK: 15
This is the summary for test reports received on the zope-tests list between 2012-08-17 00:00:00 UTC and 2012-08-18 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [1]winbot / ZODB_dev py_265_win32 [2]winbot / ZODB_dev py_265_win64 [3]winbot / ZODB_dev py_270_win32 [4]winbot / ZODB_dev py_270_win64 [5]winbot / z3c.form_py_265_32 [6]winbot / z3c.ptcompat_py_265_32 [7]winbot / zc.catalog_py_265_32 [8]winbot / zc.configuration_py_265_32 [9]winbot / zc.lockfile_py_265_32 [10] winbot / zc.monitor_py_265_32 [11] winbot / zc.ngi_py_265_32 [12] winbot / zc.queue_py_265_32 [13] winbot / zc.sourcefactory_py_265_32 [14] winbot / zc.table_py_265_32 [15] winbot / zope.annotation_py_265_32 [16] winbot / zope.app.applicationcontrol_py_265_32 [17] winbot / zope.app.appsetup_py_265_32 [18] winbot / zope.app.authentication_py_265_32 [19] winbot / zope.app.basicskin_py_265_32 [20] winbot / zope.app.broken_py_265_32 [21] winbot / zope.app.component_py_265_32 [22] winbot / zope.app.container_py_265_32 [23] winbot / zope.app.content_py_265_32 [24] winbot / zope.app.debug_py_265_32 [25] winbot / zope.app.dependable_py_265_32 [26] winbot / zope.app.error_py_265_32 [27] winbot / zope.app.exception_py_265_32 [28] winbot / zope.app.folder_py_265_32 [29] winbot / zope.app.form_py_265_32 [30] winbot / zope.app.generations_py_265_32 [31] winbot / zope.app.http_py_265_32 [32] winbot / zope.app.i18n_py_265_32 [33] winbot / zope.app.interface_py_265_32 [34] winbot / zope.app.locales_py_265_32 [35] winbot / zope.app.localpermission_py_265_32 [36] winbot / zope.app.pagetemplate_py_265_32 [37] winbot / zope.app.principalannotation_py_265_32 [38] winbot / zope.app.publication_py_265_32 [39] winbot / zope.app.publisher_py_265_32 [40] winbot / zope.app.renderer_py_265_32 [41] winbot / zope.app.rotterdam_py_265_32 [42] winbot / zope.app.schema_py_265_32 [43] winbot / zope.app.security_py_265_32 [44] winbot / zope.app.server_py_265_32 [45] winbot / zope.app.session_py_265_32 [46] winbot / zope.app.testing_py_265_32 [47] winbot / zope.app.wsgi_py_265_32 [48] winbot / zope.app.zcmlfiles_py_265_32 [49] winbot / zope.app.zopeappgenerations_py_265_32 [50] winbot / zope.applicationcontrol_py_265_32 [51] winbot / zope.authentication_py_265_32 [52] winbot / zope.browser_py_265_32 [53] winbot / zope.browsermenu_py_265_32 [54] winbot / zope.browserpage_py_265_32 [55] winbot / zope.browserresource_py_265_32 [56] winbot / zope.cachedescriptors_py_265_32 [57] winbot / zope.catalog_py_265_32 [58] winbot / zope.component_py_265_32 [59] winbot / zope.componentvocabulary_py_265_32 [60] winbot / zope.configuration_py_265_32 [61] winbot / zope.container_py_265_32 [62] winbot / zope.contentprovider_py_265_32 [63] winbot / zope.contenttype_py_265_32 [64] winbot / zope.copy_py_265_32 [65] winbot / zope.copypastemove_py_265_32 [66] winbot / zope.datetime_py_265_32 [67] winbot / zope.deferredimport_py_265_32 [68] winbot / zope.deprecation_py_265_32 [69] winbot / zope.dottedname_py_265_32 [70] winbot / zope.error_py_265_32 [71] winbot / zope.event_py_265_32 [72] winbot / zope.exceptions_py_265_32 [73] winbot / zope.filerepresentation_py_265_32 [74] winbot / zope.formlib_py_265_32 [75] winbot / zope.generations_py_265_32 [76] winbot / zope.hookable_py_265_32 [77] winbot / zope.i18n_py_265_32 [78] winbot / zope.i18nmessageid_py_265_32 [79] winbot / zope.index_py_265_32 [80] winbot / zope.interface_py_265_32 [81] winbot / zope.intid_py_265_32 [82] winbot / zope.keyreference_py_265_32 [83] winbot / zope.lifecycleevent_py_265_32 [84] winbot / zope.location_py_265_32 [85] winbot / zope.login_py_265_32 [86] winbot / zope.mimetype_py_265_32 [87] winbot / zope.minmax_py_265_32 [88] winbot / zope.pagetemplate_py_265_32 [89] winbot / zope.password_py_265_32 [90] winbot / zope.pluggableauth_py_265_32 [91] winbot / zope.principalannotation_py_265_32 [92] winbot / zope.principalregistry_py_265_32 [93] winbot / zope.processlifetime_py_265_32 [94] winbot / zope.proxy_py_265_32 [95] winbot / zope.ptresource_py_265_32 [96] winbot / zope.publisher_py_265_32 [97] winbot / zope.ramcache_py_265_32 [98] winbot / zope.schema_py_265_32 [99] winbot / zope.security_py_265_32 [100] winbot / zope.securitypolicy_py_265_32 [101] winbot / zope.sendmail_py_265_32 [102] winbot /
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Sat, Aug 18, 2012 at 11:03 PM, Tres Seaver tsea...@palladion.com wrote: Because the ability to check into svn.zope.org is based on a chain of custody managed by the ZF (web account, verified e-mail address, and SSH key). J. Random Hacker's account on Github has no such chain. Sure, but Random J Hacker shouldn't have write permission to the repository, so I don't understand why that makes a difference. //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi, On 2012-08-19 01:24:31 +, Lennart Regebro said: On Sat, Aug 18, 2012 at 11:03 PM, Tres Seaver tsea...@palladion.com wrote: Because the ability to check into svn.zope.org is based on a chain of custody managed by the ZF (web account, verified e-mail address, and SSH key). J. Random Hacker's account on Github has no such chain. Sure, but Random J Hacker shouldn't have write permission to the repository, so I don't understand why that makes a difference. 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: - Make sure everyone in any ZF organizations on GitHub (e.g. buildout) has signed the contributor agreement, or - Declare that nothing on GitHub (or at least in the buildout organization) is a valid contribution to the work. In either case, AFAICT zc.buildout development has stopped on svn.zope.org and started on GitHub so let us let the commit stand to reflect this real world circumstance. Alex //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- Alex Clark · http://pythonpackages.com___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
