Wichert Akkerman wrote:
Previously Tim Hicks wrote:
Hi,
I'm working on the Quills weblog product this summer - supported by
Google SoC. As part of this work, I'm factoring out various bits of
functionality. One example is the MetaWeblog API code that allows for
authoring with external blog clients. Quite a lot of this code doesn't
need to be in the 'Products/' hierarchy, so I'm packaging it so it works
from 'lib/python/'.
My question is, are there conventions for what namespace package(s) I
should use? Is 'plone.' reserved for code spun out from the core? Do
people have views on whether I should be using, say, 'plone.blogging.*'?
http://plone.org/documentation/manual/plone-developer-reference/conventions/package-naming-conventions
Although that does not document to be the current practice completely,
which seems to additionally specify: plone.* only for Plone
Foundation-owned code in the plone repository and collective.* for code
found in the collective.
You can of course choose any name you want. quills.* would work, for
example.
Martin
--
Acquisition is a jealous mistress
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
