Re: [Zope] Frustrated with Python and Frameworks. Zope, Grok, , Django, CherryPy
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. -- Martijn Jacobs Four Digits, Internet Solutions a: Willemsplein 15-1 6811 KB Arnhem NL e-mail: martijn@fourdigits.nl | web: http://www.fourdigits.nl tel: +31 (0)26 44 22 700 | fax: +31 (0)84 22 06 117 _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
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. :) Once you figure out who are going to take the lead on this project, please *do* let me know so I can keep in touch with you guys. Regards, Martijn
Hi Martijn.
Just to make it utterly clear: this stuff won't happen by itself. I understand. It's good to hear that zope 2 is in good hands, at least for working on the code. If a new zope.org is in development I can volunteer to make some tutorials or even documentation. Will get back on this one later.
Martijn. -- Martijn Jacobs Four Digits, Internet Solutions a: Willemsplein 15-1 6811 KB Arnhem NL kvk: 091621370000 | btw: 8161.22.234.B01 e-mail: martijn@fourdigits.nl | web: http://www.fourdigits.nl tel: +31 (0)26 44 22 700 | fax: +31 (0)84 22 06 117
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFHTekj+gerLs4ltQ4RAoD8AKCjJ7poD7/lPvkOlOnoXhTxe/UIzQCbBZgw Oc5Hzbv9zE7uuAZMrhf1GbU= =9Fjb -----END PGP SIGNATURE-----
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
Hey, On Nov 29, 2007 12:53 AM, Philipp von Weitershausen <philipp@weitershausen.de> wrote:
Tres Seaver wrote: [snip]
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.
All right. Good point too! The svn.zope.org repository doesn't sound like a good place then for this project. If anyone wants to pick this project up, we should arrange something else. I'm sure that's quite doable, however. Regards, Martijn
Hey, On Nov 28, 2007 11:18 PM, Tres Seaver <tseaver@palladion.com> 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.
Thanks, I had forgotten about that. Anyway, it could be any SVN repository - and this project will only happen if one or two volunteers do the work of collecting interesting Zope 2 products, contacting the authors (not strictly necessary but always a good thing to do) and checking them in, possibly cleaning things up here and there. I know for one Formulator could be a candidate. I haven't been doing much with it for quite a while now. Needs to be squared with Infrae, which is doing some low-level maintenance on it, and it's safe in the Infrae SVN, but should there be a good new home and enough volunteers to help maintain it, it's quite possible Infrae would be interested in having it most. I'm not speaking for Infrae here, just as the original author of Formulator. Regards, Martijn
Martijn Faassen wrote:
the work of collecting interesting Zope 2 products, contacting the authors (not strictly necessary but always a good thing to do) and checking them in, possibly cleaning things up here and there.
Well, I think is is fine for products where the original maintainer has "gone away" and the original repository is no longer available, but I think that having multiple forks on products with active repositories is asking for trouble. I would have thought the key thing would be to build something like the cheeseshop but for zope products. But that's really one of the key things that zope.org should be, no? Maybe http://products.zope.org would be a simpler thing to build and get running? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Hey, On Nov 29, 2007 8:43 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Martijn Faassen wrote:
the work of collecting interesting Zope 2 products, contacting the authors (not strictly necessary but always a good thing to do) and checking them in, possibly cleaning things up here and there.
Well, I think is is fine for products where the original maintainer has "gone away" and the original repository is no longer available, but I think that having multiple forks on products with active repositories is asking for trouble.
Of course, so we should avoid this by trying to contact the original developer(s). I guess I wasn't clear about 'not strictly necessary'; I'd consider it less necessary if there has been no development for years, but of even then sending off an email makes sense. It might not make sense to wait indefinitely for an answer, however.
I would have thought the key thing would be to build something like the cheeseshop but for zope products. But that's really one of the key things that zope.org should be, no?
Maybe http://products.zope.org would be a simpler thing to build and get running?
I think a Plone site should be able to run something like this, as plone.org does, right? Anyway, I don't think the technology is the most work here. We need someone to go through and create the content. Even a simple web-page listing interesting products and where to find them would already be tremendous progress. Content will be our challenge, let's not worry about technology too much, which should be in good hands. Regards, Martijn
(Fri, Nov 30, 2007 at 09:24:25PM +0100) Martijn Faassen wrote/schrieb/egrapse:
I don't think the technology is the most work here. We need someone to go through and create the content. Even a simple web-page listing interesting products and where to find them would already be tremendous progress. Content will be our challenge, let's not worry about technology too much, which should be in good hands.
How about http://www.contentmanagementsoftware.info/ It doesn't have everything, but I found it to be useful some times. Regards, Sascha
Hey, On Dec 1, 2007 7:34 PM, Sascha Welter <zopelist@betabug.ch> wrote:
(Fri, Nov 30, 2007 at 09:24:25PM +0100) Martijn Faassen wrote/schrieb/egrapse:
I don't think the technology is the most work here. We need someone to go through and create the content. Even a simple web-page listing interesting products and where to find them would already be tremendous progress. Content will be our challenge, let's not worry about technology too much, which should be in good hands.
How about http://www.contentmanagementsoftware.info/
It doesn't have everything, but I found it to be useful some times.
The list of Zope products looks quite nice! Who maintains this site? Quintagroup? I wonder whether they'd be willing to have someone take the Zope related list, go through it and edit it, and host it on zope.org (when *that* is ready). I've cc-ed Myroslav at quintagroup. :) Regards, Martijn
On Dec 3, 2007 1:59 PM, Martijn Faassen <faassen@startifact.com> wrote:
Hey,
On Dec 1, 2007 7:34 PM, Sascha Welter <zopelist@betabug.ch> wrote:
(Fri, Nov 30, 2007 at 09:24:25PM +0100) Martijn Faassen wrote/schrieb/egrapse:
I don't think the technology is the most work here. We need someone to go through and create the content. Even a simple web-page listing interesting products and where to find them would already be tremendous progress. Content will be our challenge, let's not worry about technology too much, which should be in good hands.
How about http://www.contentmanagementsoftware.info/
It doesn't have everything, but I found it to be useful some times.
The list of Zope products looks quite nice! Who maintains this site? Quintagroup?
I wonder whether they'd be willing to have someone take the Zope related list, go through it and edit it, and host it on zope.org (when *that* is ready). I've cc-ed Myroslav at quintagroup. :)
Regards,
Martijn
Hi Martijn, I need to say that we had hard time lately gathering and updating the contentmanagementsoftware.info and we are running short on hands. The most we can propose is we can generate a XML export (or Marshall) of our existing Zope products directory if it can be useful in anyway. Regards, Volodymyr. -- Volodymyr Cherepanyak e-mail: chervol@gmail.com skype : callto://chervol?chat
participants (7)
-
Chris Withers -
Martijn Faassen -
Martijn Jacobs -
Philipp von Weitershausen -
Sascha Welter -
Tres Seaver -
Volodymyr Cherepanyak