[Zope3-dev] Official Zope packages

[Jim Fulton]

Some high-level comments.

I think you raise some good questions.

I'm not sure that what namespace package something is in is a good  
indicator of "officialness" or quality.

I'm not sure what the value of "officialness" is.

It might be good to have some sort of rating system to help address  
quality.  Of course, rating systems are hard. :)

It might be good to have some processes for indicating commitment to  
a package.  Like (brainstorming...) maybe someone should be required  
to periodically assert that they are maintaining something, even if  
they aren't doing any work.

Just some thoughts.

I think this discussion might be better held on the foundation list.

Jim

On Jul 25, 2007, at 8:50 AM, Christian Theune wrote:

> Hi,
>
> if I remember correctly we don't have a conclusion on what "official"
> Zope packages are.
>
> I have a specific motivation and a (hopefully) specific question:
>
> I am happy to take a part of a broader maintenance/development effort
> from the "Zope Project" into my hands and contribute on a larger scale
> than what my daily needs are. I do this because my mid-term/long-term
> needs hopefully benefit from what I contribute now, especially in  
> terms
> of quality.
>
> My personal feeling is that zope.* is the large scale effort of shared
> maintenance/development with the assurance of quality, etc. that has
> been the monolithic release up until now. For me it signals that the
> software deals with problems that are solved on a level that leverages
> interest of more than one party and is maintened in a more solid way
> than just by one or two people.
>
> We started working on the dependencies of the new satellite packages
> today and saw that there are packages in the zope.* namespace that
> weren't part of the monolithic releases. We didn't touch those as we
> couldn't completely figure out whether touching them was  
> appreciated and
> actually reasonable.
>
> So the specific question: How do we want to manage packages in the
> zope.* namespace and is the idea of the collaborative development and
> maintenance perceived the same way by others?
>
> Just-some-cents-from-me,
> Christian
>
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub: http://mail.zope.org/mailman/options/zope3-dev/jim%40zope.com
>

--
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