[Framework-Team] package syndication: practical problems + possible solution

[Johannes Raggam]

Hey FWT,

I want to share a problematic experience with the Python-package
syndication effort, the https://dev.plone.org/ticket/13283 PLIP.

At wine/beer sprint we moved plone.app.event's timezone vocabs to
plone.app.vocabulary, because we found that generally useful and worth
to be used elsewhere.
Then we moved plone.app.event's controlpanel to P.CMFPlone,  because it
just does datetime related settings, not necessarily specific to the
calendaring framework plone.app.event.

Now, the current refactored plone.app.event 2.0 branch, which somehow
depends on newest p.a.vocabularies and P.CMFPlone, cannot easily be used
in Plone < 5, just because of the dependency on CMFPlone.

With the package syndication effort, we might give up some inter-version
compatibility of selected packages like plone.app.event, and others,
just because other dependencies like p.a.controlpanels cannot be
released independently from CMFPlone anymore.

SOLUTION (?)

That would actually be different, if we don't do these refactorings like
the controlpanel one, but merge the package namespaces into another
umbrella namespace, just called "plone.app", and refactor the packages
to not have any code in it's __init__.py, which is a requirement for
these namespace packages to work. That would also be less work, than
refactoring everything into CMFPlone. Also, for backwards compatibility,
individual packages/namespaces can still be released independently.

Makes sense?

Actually, that's not a new idea. rnixx and I were talking about this 17
months ago and commenting it here:
https://dev.plone.org/ticket/13283#comment:9


Best, Johannes






-- 
programmatic  web development
di(fh) johannes raggam / thet
python plone zope development
plone framework  team  member
mail: office at programmatic.pro
web:  http://programmatic.pro
      http://bluedynamics.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20140407/da82e589/attachment.asc>