[Zope-dev] Please use launchpad bugtracking/blueprints more

[Gary Poster]

On Mar 25, 2009, at 2:21 PM, Martijn Faassen wrote:

> Sidnei da Silva wrote:
>> Hi Martijn,
>>
>> On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen
>> <faassen at startifact.com> wrote:
>>> One question is what launchpad project we should use.
>>>
>>> The current launchpad is for "Zope 3". The steering group isn't  
>>> about
>>> Zope 3. It's about a whole bunch of libraries. Creating a separate
>>> launchpad project for each library in the framework seems like a  
>>> bit of
>>> overkill at this stage, though it would please those people who  
>>> come at
>>> us at the perspective from libraries the most.
>>
>> It smells like 'Zope Framework' (zope-framework) should be a Project
>> Group then, and there should be a 'Zope Steering Group Project'
>> (zope-steering-group-project) as part of it, and sibling of Zope 3  
>> and
>> any other libraries that are part of Zope Framework. For an example  
>> of
>> what this looks like, look at:
>
> Why would the steering group be a project as part of the Zope  
> Framework?
> The steering group isn't a project?
>
> I'm all for setting something up, but I'm still not clear on what  
> you'd
> set up. A Zope Framework project group with what inside?

My take would be the following.  It's probably contentious.

- The current zope3 project is regarded as a project for the  
aggregation of the pieces into the old tgz and the old mgmt UI.  This  
should be clarified on the project page.

- There is a new Zope Framework (I would prefer Zope Libraries myself,  
but let's not start that again ;-) ) umbrella project, controlled by a  
new Zope Framework team.

- There are multiple zope.* (and z3c.* and whatever) library  
projects.  They are part of the umbrella project (if so desired by the  
pertinent parties).

- The current zope3 project should be considered part of the Zope  
Framework *at least for now* because it has legacy information.  If  
someone reassigns the bugs and blueprints and so on to the pertinent  
library projects (or to the Zope Framework), "zope3" could no longer  
be part of the Zope Framework umbrella project, if desired.  That's  
work, though, so I'd be inclined to see if it happens and meanwhile be  
happy to take the zope3 project in as legacy.

Gary