On Fri, Feb 6, 2009 at 1:10 AM, Tres Seaver <tsea...@palladion.com> wrote:
> Hash: SHA1
> Martijn Faassen wrote:
>> Fred Drake wrote:
>>> On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver <tsea...@palladion.com> wrote:
>>>> I'm fixing dependent packages broken by my changes:  could you add me to
>>>> zope.app.container as well?
>>> Done.
>> Great work in further reducing dependencies Tres!
>> Note that Stephan Richter has a Magic Script that he can run to give you
>> access to all zope.* packages that he has access to. I'm sure he'll do
>> that if you drop him a mail.
>> For newly created packages such as zope.broken, could you make sure it
>> gives owner access to the list of current package owners for other
>> zope.* packages? It's a bit of clicking around to do that as it's quite
>> a list, but it would help people from getting stuck releasing an update
>> in the future.
> I'm glad to grant ownership, but I seriously doubt that anybody will
> ever touch the package. ;)  It's whole purpose in life is to hold a
> single interface, after all.

True, but one never knows (perhaps some modification to setup.py,
say), and I think we should have a general rule any PyPI package
that's part of the Zope 3 framework (handwave that here for now)
should be owned by a group of people.


Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to