SatellitesAndLaunchpad

Problem

The launchpad infrastructure, as we use it, seems unsuitable to manage the on-going development of our satellite projects.

We use launchpad bugs and launchpad blue prints. Both are assigned to a single project "Zope 3" within the "Zope.org" project group.

Assigning bugs and proposals to the "Zope 3" project doesn't make sense any more because the release-cycles became independent.

Proposal

I propose that we create individual projects in launchpad for the various satellites. (Steve Alexander offered to provide a CSV import feature for the existing set of projects.)

I propose that the existing bugs in the Zope 3 project get slowly attached to upstream projects as we work on them.