Re: [Zope3-dev] z3c - be or not to be

2006-08-27 Thread Dieter Maurer
Roger Ineichen wrote at 2006-8-25 18:27 +0200: ... The reason why; We really have no time to do this in the next couple of month. And the option sombody else doing it is also *NO* option because we have allready productive projects build on this libraries and have no time to migrate them for

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Martijn Faassen
Stephan Richter wrote: [snip] Also, z3c does not try to be the holy grail of community work. It is just another namespace and I think this should be accepted. I actually think it would be *nice*, if not at all essential, to have a common namespace for community work. For such a common

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Lennart Regebro
On 8/25/06, Martijn Faassen [EMAIL PROTECTED] wrote: I actually think it would be *nice*, if not at all essential, to have a common namespace for community work. For such a common namespace z3c is a bit unwieldier than something like zorg. We could consider establishing a more coherent pattern

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Martijn Faassen
Lennart Regebro wrote: On 8/25/06, Martijn Faassen [EMAIL PROTECTED] wrote: I actually think it would be *nice*, if not at all essential, to have a common namespace for community work. For such a common namespace z3c is a bit unwieldier than something like zorg. We could consider establishing a

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Olivier Grisel
Martijn Faassen a écrit : Technically it isn't a problem, that's why it's not at all essential. But it might be nice for some other reasons: * people who write a new community package knows which namespace to use * we could present this to the outside world a bit more coherently; look at

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Lennart Regebro
On 8/25/06, Martijn Faassen [EMAIL PROTECTED] wrote: Technically it isn't a problem, that's why it's not at all essential. But it might be nice for some other reasons: * people who write a new community package knows which namespace to use * we could present this to the outside world a bit

[Zope3-dev] z3c - be or not to be

2006-08-25 Thread Roger Ineichen
Hi to all Zope3 Visionairs ;-) CC: to some of the z3c namespace chooser which are to busy to answer, flying back to Boston or are at holiday this week ;-) Yes, I didn't do much for Zope3 core the last couple month, except publishing to z3c. But as on of the initiator of z3c I need to give a

Re: [Zope3-dev] z3c vs. the zorg

2006-08-25 Thread Baiju M
+1 for zorg 3 is an unlucky number, it should be killed sooner or later :) -- Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

[Zope3-dev] z3c vs. the zorg

2006-08-24 Thread Benji York
Stephan's ZSCP proposal suggests using the package name z3c for community packages. IOW, packages that aren't part of a larger collection like lovely.*, zc.*, etc.. There are currently several z3c packages in existence. The zope3.org packages currently use the package name zorg. I

Re: [Zope3-dev] z3c vs. the zorg

2006-08-24 Thread Stephan Richter
On Thursday 24 August 2006 16:54, Benji York wrote: Stephan's ZSCP proposal suggests using the package name z3c for community packages. IOW, packages that aren't part of a larger collection like lovely.*, zc.*, etc.. There are currently several z3c packages in existence. The zope3.org

Re: [Zope3-dev] z3c vs. the zorg

2006-08-24 Thread Fred Drake
On 8/24/06, Benji York [EMAIL PROTECTED] wrote: If zc were to become zope community, I'd be *totally* for it (but I don't speak for ZC here, so that may not be cool with others, like say Jim). We'd either keep using zc under the new meaning, or switch to something else. z3c clearly stands for