Help keep Plone dependencies tidied up

[gforcada]

As it seems to be a new trend, to post either new PLIPs, or status updates of them, I hereby do the same

I just posted this on the PLIP: keep track of dependencies:

Issue: PLIP: keep track of dependencies

This PLIP is ready for review:

• documentation: http://jenkinsploneorg.readthedocs.io/en/latest/qa-dependencies.html

• buildout.coredev (branch 5.2) has been updated to the latest version of z3c.dependencychecker (after running buildout use bin/dependencychecker script)

• global jenkins job: https://jenkins.plone.org/view/QA/job/qa-undeclared-dependencies/

  • with some graphs to see the trend: https://jenkins.plone.org/view/QA/job/qa-undeclared-dependencies/plot/

• single package jenkins job: https://jenkins.plone.org/view/QA/job/qa-pkg-dependencies/

• mr.roboto changes are already merged and deployed: https://github.com/plone/mr.roboto/pull/53 and quite some follow up commits afterwards

  • as a side note: mr.roboto is now running on python 3.6 as well

• a package, as a proof of concept has been cleaned up: https://github.com/plone/Products.ExtendedPathIndex/pull/5

With the global jenkins job we are tracking around 130 packages (all packages defined in sources.cfg in branch 5.2 of buildout.coredev that are either in plone or collective GitHub organizations) which should have their dependencies reviewed. It would be cool if that could be done for almost as many persons as packages

I will be totally happy to mentor/help anyone interested in reaching the goal of keep track of package dependencies on all our packages.

For starters, some packages that might be easy targets:

• https://github.com/plone/borg.localrole
• https://github.com/plone/plone.app.event
• https://github.com/plone/plone.app.lockingbehavior
• https://github.com/plone/plone.app.querystring
• https://github.com/plone/plone.app.registry
• https://github.com/plone/plone.app.uuid
• https://github.com/plone/plone.batching
• https://github.com/plone/plone.browserlayer
• https://github.com/plone/plone.cachepurging
• https://github.com/plone/plone.caching
• https://github.com/plone/plone.contentrules
• https://github.com/plone/plone.event
• https://github.com/plone/plone.indexer
• https://github.com/plone/plone.intelligenttext
• https://github.com/plone/plone.keyring
• https://github.com/plone/plone.memoize
• https://github.com/plone/plone.portlet.static
• https://github.com/plone/plone.registry
• https://github.com/plone/plone.schema
• https://github.com/plone/plone.supermodel
• https://github.com/plone/plone.theme
• https://github.com/plone/plone.uuid

Have fun cleaning dependencies, you will learn a lot !

[jaroel (Roel Bruggink)]

Hi Gil,

Wouldn't keeping the usermapping in all the repos a maintenance nightmare?
It would lead to duplicate definitions all over the place by the looks of it, or am I missing something here?

[jaroel (Roel Bruggink)]

We probably could use whatever collective.omelette does to generate a usermapping that can be used for specific Plone versions as it already creates symlinks from module to the egg - ie Products/Five links to the Zope2 egg.