Re: collective packages on pypi

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.

my 2¢

Giacomo

On 08/22/2013 11:56 PM, Encolpe Degoute wrote:
> +1
>
> Le 21/08/2013 17:32, Alan Runyan a écrit :
>> Hi everyone.
>>
>> I was wondering if anyone felt that for all collective packages
>> we automatically give project owner to a "collective" user in pypi.
>> This way someone can always make new releases; even if the
>> original owner goes away or becomes unresponsive.  Maybe
>> the release manager and FWT members plus others can have
>> the l/p.  Just a thought. I registered 'collective'
>>
>> cheers
>>
>


-- 

Giacomo Spettoli

Twitter: http://twitter.com/giacomospettoli
LinkedIn: http://linkedin.com/in/giacomospettoli


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