Re: collective packages on pypi

Op 23-08-13 23:49, Alex Clark schreef:
> Giacomo Spettoli <giacomo.spettoli@...> writes:
>
>> maybe a way in the middle of between total closure and total openess is to
> give that "collective account" to a team that is active but not completely
> open. ATM one solution could be the FTW, but I think there should be a new
> team for that, let's say the "release team", that will be responsible for
> releases and can be asked to cut releases. My main concerns are about
> responsability, there should always be a one responsible. The collective
> membership is not enought cause anyone can join, even malicious developer.
> Plus, what happen if a disagreement happen between two developer that have
> same powers but different thought? There could be a "release war" and that's
> definitely not a good thing.
>
> I played with something like this when working on PythonPackages, going so
> far as to create a pythonpackages user on PyPI which I then added to any
> package I wanted to release via pythonpackages.com. But I gave up when PyPI
> began supporting Oauth (which then allowed me to get users' permission to
> release packages in a much more elegant way, via token exchange, etc.)
>
> I mention this because: while I support the idea of "collective ownership"
> of all our collective packages, I'm not convinced a collective user is good
> approach (it might be, and we can certainly try). However: I do feel that we
> should be looking to PyPI, which is under heavy development now, for all our
> package hosting needs. We broke PSC in some meaningful way during our
> "configuration bankruptcy" a while back and only a single person has
> complained so far, which tells me no one is really using the package hosting
> features. Conversely if plone.org goes down, I hear about it within about 5
> seconds.

Package uploading via 'python setup.py sdist mupload' (well, fullrelease 
from zest.releaser of course) at least works.  I got an error doing this 
last week on a package I recently got upload rights to, tried it again 
and it worked.

I think I am not really using the uploaded packages, as buildout gets 
them from PyPI, but uploading at least still works for me.  I keep 
uploading because then the products with their latest info can be found 
on plone.org.


In other news, updating plone.org to Plone 4.3 has broken Poi, giving a 
validation error when creating a new issue, and only one person has 
complained to me so far, which tells something about how much Poi is 
being used on plone.org.  Probably more people have seen it and have 
simply gone to issue trackers on github.  The error was fixed a few 
months before, but the Poi version on plone.org is old.  I created a 
pull request for plone.org here, in case someone wants to have a go at 
that: https://github.com/plone/Products.PloneOrg/pull/11

Cheers,

-- 
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl


------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk