[SciPy-dev] Giving write access to SciPy SVN

eric jones eric at enthought.com
Fri Oct 6 22:36:13 CDT 2006

I am for a very open approach to this.  I think we should give people 
access once they have (1) submitted 2-3 patches, (2)proven themselves 
trust worthy and committed to the community by activity on the mailing 
lists, and (3) asked for write access.  This approach ensures a maximum 
number of capable hands tending the garden, and our experience up to now 
has been that people are generally well behaved.  If trust is ever 
abused, then we can re-evaluate the policy.

My .02,

Travis Oliphant wrote:

>Hi all,
>What is the attitude toward members on this list of growing write-access 
>to SVN.  It seems to me that SciPy will need a lot of people who have 
>write access in order to keep up with the different domains of tools 
>that SciPy has.  Do we want to open up the SVN tree to a lot of 
>developers or in concert with developing a peer-review and "publication" 
>strategy for SciPy have "associate editors" in different problem domains 
>who have write access to SVN and encourage others to contribute patches.
>I'd love to hear your opinions.
>Scipy-dev mailing list
>Scipy-dev at scipy.org

More information about the Scipy-dev mailing list