>> plone.reload.addons >> plone.reload.coredev > > -1 for nesting namespaces and replacing renaming plone.reload, which is in > wide use. > How about plone.autoreload or something like that?
I still don't grok what the issue with nested namespaces is. To avoid nesting, one could do: plone.reload_addons plone.reload_coredev but that comes to the same thing, except with different punctuation. Choosing names like: plone.autoreload plone.zetareload just to make sure they don't sort anywhere close to each other :-p doesn't seem helpful to me. Basically if you have two packages addressing the same use case in different ways, or closely related use cases, isn't the package name a good place to convey how they relate to each other? Both packages do autoreload, so that name doesn't help much to distinguish them. We can work with any name, and metadata, documentation and the community will help to point out relevant packages, so good names aren't really critical. They are quite nice though. -- jean . .. .... //\\\oo///\\ _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
