[Framework-Team] Re: Organisation of Plone components in Collective and Plone svn
rocky at serverzen.com
Sun Apr 30 22:33:57 UTC 2006
Well, this is a bit of a grey area.
Based on how the zope3 naming conventions are going these days, this is
what i would leans towards:
This would be for the portlets project:
This would be for the contextualhelp project:
In other words, most of the 2nd level packages warrant their own
projects and the toplevel svn directory name would actually be
This convention can quickly be seen by perusing http://svn.zope.org/
An example would be http://svn.zope.org/zope.formlib/
Zope Corp even does this with their own pkgs which they prefix with zc.*
On Sun, 2006-30-04 at 23:01 +0100, Martin Aspeli wrote:
> Hi guys,
> A lot of the Archipelago work, like plone.portlets (a top-level package on
> itself?) and LinkIntegrity and ploneKukit landed in the Collective. I'm
> not sure that's the optimal place for all of them. The things that are
> part of plone core and are maintained as such should live in the main
> plone repo, with the protection that enjoys.
> For example, I think we should have:
> plone/ajax (for the kukit/bling stuff)
> plone/contextualrefs (to be broken out of contextualhelp)
> the LinkIntegrity stuff may need to be moved, but I'm not quite sure.
> What's the Foundation's and our position on this?
ServerZen Software -- http://www.serverzen.com
News About The Server -- http://www.serverzen.net
More information about the Framework-Team