[ZF] Please comment! Re: Zope Development Process

Jim Fulton jim at zope.com
Thu Sep 28 09:42:11 EDT 2006


Christian Theune wrote:
...
>> On Sep 25, 2006, at 5:44 PM, Jim Fulton wrote:
...
>>> This is a *lot* of organization. :)
> 
> And it needs to be transparent.

I don't know what you mean by this.

...

>>> - We need a process for contributing 3rd-party code to the
>>>   respository. (I would like to see this kept to a minimum, if
>>>   possible, by using eggs, rather than code copying, to manage
>>>   dependencies on 3rd-party code.
>>>
>>> - We need a way to invite committer members.
>>>
>>> The first two issues are pretty urgent, as I don't think we can
>>> establish a Foundation repository without resolving them.
> 
> That's my impression too. On the second issue: Maybe we can have a
> 3rd-party repository that acts as a mirror.

Yes, where "repository" in this case might just be a collection of eggs
on a web server.


> My biggest concern would be
> that repositories that manage software we depend on go away or don't
> provide historic versions that we need anymore.

Yup

...


>>> - The process requires project-management committees and projects,
>>>   which we don't have yet.
>>>
>>> We need to find a way to move forward, either by interpreting and
>>> following requirements set forth on these documents, or by trying to
>>> simplify them and following the result.
>>>
>>> I wonder what projects there should be.  Do we need want many
>>> projects?  Some obvious projects are Zope 2, Zope 3, and ZODB.  What
>>> about smaller efforts?  Should ZConfig be a separate project?  If not,
>>> what project does it fall under.  It is used by all 3 of Zope 2, Zope
>>> 3, and ZODB.  What about a project like zc.buildout?  Should the
>>> repsository contain code that doesn't fit under any project?  For
>>> example, zc.ngi is an experimental testable networking library that I
>>> plan to use in ZEO someday.  Should that be in the repository?  Should
>>> it be a project? Should the packages in the zc (or z3c or lovely)
>>> namespaces be their own projects? Should each namespace be a project?
> 
> Do we have an idea of a schedule? Do we want those to be in place this
> year, Q1 next year, ...?

That all depends on (and, of course, influences) what we decide to do.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org


More information about the Foundation mailing list