On Wed, Apr 11, 2012 at 8:29 AM, Héctor Velarde
<[email protected]> wrote:
> is there any convention on package names on the collective? where do I find
> that information?
While I am not a huge fan of nested namespaces, a name like
collective.twitter.portlets reads like a natural English noun-phrase
with tokens split on dot. Of course, to attain this seemingly
friendly name (saying aloud "Collective Twitter Portlets" is a lot
easier to find easy/memorable than "collective dot portlets dot
twitter"), you have to sacrifice big-endianness of the namespace
package order. The fact that Python's packaging machinery does not
really care leads me to believe that it really is just not that big of
a deal enough to be forced to take sides between linguistic simplicity
("rolls off the tongue" -- at least it does for English speakers) and
mathematical clarity (endian order), unless you perceive a likely
collision of names across two or more collective projects. Barring
that possibility of conflict, just choose what sounds right for the
project and its likely audience.
Sean
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
