Re: Frustrated with Python and Frameworks. Zope, Grok, , Django, CherryPy
Tres Seaver wrote:
Martijn Faassen wrote:
Hey,
On Nov 28, 2007 12:16 AM, Martijn Jacobs <martijn-r20ZR6Wpu0Qq0XJkksQ3qw@public.gmane.org> wrote:
We could also consider putting them in some kind of collective-like SVN repository so that people can make changes when they need to. I think this is a great idea as it works with the Plone collective this way as well. Just to make it utterly clear: this stuff won't happen by itself. We need a bunch of self-driven volunteers to do this work: look up the relevant codebases, contact their authors, check them into a SVN if they look orphaned (if they aren't of course don't fork them!) and make an index page describing what is going on. This can be done independently from zope.org, and should later become part of the zope.org website.
You will need a SVN repository somewhere. svn.zope.org could be used if you have committer access, but it would be somewhat restricted as GPL-ed products can't be placed in there. Anyway, all these questions I'm thinking of now someone else should take the lead on, as it won't be me. :)
For clarity, nobody but a ZC employee (at present) is supposed to be checking in any code with any license other than the ZPL; in the future, such a checkin will need to be approved by some agent / organ of the Zope Foundation.
It's actually even more restrictive than that: If I read paragraph 5 of the contributor agreement [1] right, then whoever checks things in must have the intellectual property over the code, otherwise s/he would not be able to donate half of it to ZC. So effectively you can't check in somebody else's code, even if it's covered by the ZPL. [1] http://www.zope.org/DevHome/CVS/Contributor.pdf
sorry, meant to CC zope@zope.org, not zope-dev@zope.org Philipp von Weitershausen wrote:
Tres Seaver wrote:
Martijn Faassen wrote:
Hey,
On Nov 28, 2007 12:16 AM, Martijn Jacobs <martijn@fourdigits.nl> wrote:
We could also consider putting them in some kind of collective-like SVN repository so that people can make changes when they need to. I think this is a great idea as it works with the Plone collective this way as well. Just to make it utterly clear: this stuff won't happen by itself. We need a bunch of self-driven volunteers to do this work: look up the relevant codebases, contact their authors, check them into a SVN if they look orphaned (if they aren't of course don't fork them!) and make an index page describing what is going on. This can be done independently from zope.org, and should later become part of the zope.org website.
You will need a SVN repository somewhere. svn.zope.org could be used if you have committer access, but it would be somewhat restricted as GPL-ed products can't be placed in there. Anyway, all these questions I'm thinking of now someone else should take the lead on, as it won't be me. :)
For clarity, nobody but a ZC employee (at present) is supposed to be checking in any code with any license other than the ZPL; in the future, such a checkin will need to be approved by some agent / organ of the Zope Foundation.
It's actually even more restrictive than that: If I read paragraph 5 of the contributor agreement [1] right, then whoever checks things in must have the intellectual property over the code, otherwise s/he would not be able to donate half of it to ZC. So effectively you can't check in somebody else's code, even if it's covered by the ZPL.
[1] http://www.zope.org/DevHome/CVS/Contributor.pdf _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
On Wed, 28 Nov 2007 15:52:01 -0800, Philipp von Weitershausen <philipp@weitershausen.de> wrote:
It's actually even more restrictive than that: If I read paragraph 5 of the contributor agreement [1] right, then whoever checks things in must have the intellectual property over the code, otherwise s/he would not be able to donate half of it to ZC. So effectively you can't check in somebody else's code, even if it's covered by the ZPL.
That's correct from a legal point of view. Which is why code in the Collective is a separate repository and isn't covered by the contributor agreement in our particular case. -- Alexander Limi ยท http://limi.net
participants (2)
-
Alexander Limi -
Philipp von Weitershausen