Zope 3

Some discussion topics:

- Automatic dependency settings for zope packages:
  http://pypi.python.org/pypi/vanguardistas.pydebdep does this now, but is not perfect, specifically:
    * What would be the affect of the new python version numbering scheme currently discussed on distutils-sig?
    * Pydebdep currently does not take into account extras (zope packages use them a lot) leading to broken dependency chains. How should they be modeled in packages? (The safe route obviously being to depend on everything specified in extras)
    * Default naming schema, pydebdep currently uses python-${setuptools_project_name} for both source and binary package. This leads to zope.interface being python-zope.interface. This is probably wrong. How should this be? For example the twisted packages use a - replacing a . http://packages.ubuntu.com/karmic/python-twisted-runner.
    * Rules file: pydebdep includes a makefile that is adequate for most cases. Can this be improved? What about using one of the automated setuptools->deb packagers?

- How much of the ZTK dependency tree should be packaged? Can we set a well defined policy for the packages that we will commit to maintaining? It may be an idea to exclude packages with extensive/convoluted dependencies which should be cleaned up. This limits the "churn" of new packages.
- Testing: Zope packages include extensive functional tests. How can these best be run to ensure the integrity of the software stack. Can we setup a buildout? autopkgtest?

2009-06-15: I don't see a spec, so I will assume this is an informational blueprint that doesn't require any approval. -robbie.w