Re: [Zope3-dev] z3c - be or not to be
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 nothing. Yes renaming the z3c namspace whould technicaly possible, but for me(us) it's just a waist of time right now. Could be that I will change my mind in the future but not in the next couple of months. I have no opinion on namespaces (especially, whether or not z3c should be renamed). But technically, it would be extremely easy: If nothing else would change than the top level name, then a single module alias (e.g. sys.modules['z3c'] = zorg) would suffice to let all existing software work as before. -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 namespace z3c is a bit unwieldier than something like zorg. We could consider establishing a more coherent pattern in the future, perhaps. [snip] BTW, I am not aggravated about the mail; I am just very tired of those pointless namespace discussions. I'm glad you're not aggravated by something Benji brought something up this time.. He's certainly not trying to waste your time, but brings up things that he considers are important. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 in the future, perhaps. As mentioned in another thread, I'd like to avoid namespace clutter, but I have come to realize I have no good arguments for that. :-) So, if we can't agree, then it's just yet another namespace. zope, zc, lovely, schooltool, codespeak(?), nuxeo, z3lab, z3c and now zorg. If there is no interest in merging basic toolkits into the same namespace (which there overwhelmingly was not in the other discussion) then having both z3c and zorg can't be a problem either. ;) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 more coherent pattern in the future, perhaps. As mentioned in another thread, I'd like to avoid namespace clutter, but I have come to realize I have no good arguments for that. :-) So, if we can't agree, then it's just yet another namespace. zope, zc, lovely, schooltool, codespeak(?), nuxeo, z3lab, z3c and now zorg. If there is no interest in merging basic toolkits into the same namespace (which there overwhelmingly was not in the other discussion) then having both z3c and zorg can't be a problem either. ;) 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 all these nice zorg components. That said, it isn't a big deal at all, you're right. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 all these nice zorg components. Yes. Especially if components get packaged as eggs and advertised on the cheeseshop. Just a quick glance on you RSS feed and you spot all the new releases of Zope3 related components. This will probably make a lot of good publicity for Zope3 w.r.t. the rest of the python dev community. -- Olivier ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 more coherently; look at all these nice zorg components. I completely agree. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] z3c - be or not to be
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 statement before it turns me crazy. I only speak for myself here, but I guess the rest of the active z3c developer, package user team can agree on the following: I (we) will *NOT* rename the z3c namspace. We never told that z3c is the *ONLY* namespace for z3 community. Let's see the z3c namspace as some usefull packages commited from a team of z3 developers they work and share its work. I'm sure and hope there is more space for other developer teams using it's own namespace. 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 nothing. Yes renaming the z3c namspace whould technicaly possible, but for me(us) it's just a waist of time right now. Could be that I will change my mind in the future but not in the next couple of months. btw, Onw of my next task, whould be to update the documentation and write more tests, but for sure not to change a namespace. Philipp, Renaming sandbox to trunk in some z3c pkgs is one of my first steps I will do if I'm finished the next project. Or does anybody else take this task? Regards Roger Ineichen _ Projekt01 GmbH ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
+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
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 personally (and at least a couple other people feel the same way) like zorg better than z3c. I'd like to propose that zorg become the name space package for otherwise homeless modules/packages. (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 packages currently use the package name zorg. I personally (and at least a couple other people feel the same way) like zorg better than z3c. I'd like to propose that zorg become the name space package for otherwise homeless modules/packages. (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). Right, thus I am clearly -1. :-) (Wow, now I do not even have to argue myself anymore. ;-) Note that we spent a lot of time coming up with this name and pretty much all the contributors to the namespace were involved in the discussion. 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. Zope Corp decided to use zc, Lovely Systems lovely and a bunch of us not representing a company decided to use z3c. So what's wrong with that? Should I create a foundation called Z3C to have the right get this namespace? Other people can feel free to work on another namespace. (BTW, I would without a thought change the working in the ZSCP document to be less asserting and globalizing.) I wonder how Zope Corp. would feel if I would ask them to use zcorp, because zc stands for Zope Community? BTW, I am not aggravated about the mail; I am just very tired of those pointless namespace discussions. Regards. Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c vs. the zorg
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 the Zope Zoftware Zystems Consortium, so should be freely used by the Z3C's members according to the usage rules established by that august body. The rest of us shouldn't be wasting time worrying about it. I'm sorry. It's off my chest now, so if this (mercifully) peters out soon, we'll all be better off. Indeed. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
