-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> On Nov 28, 2007 12:16 AM, Martijn Jacobs <[EMAIL PROTECTED]> 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.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -