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.

Advertising

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