[SciPy-dev] Giving write access to SciPy SVN

John Hunter jdhunter at ace.bsd.uchicago.edu
Mon Oct 9 11:07:10 CDT 2006

>>>>> "eric" == eric jones <eric at enthought.com> writes:

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

    eric> My .02, eric

This is the loose policy we've used for matplotlib, and we've had
between 12 and 20 people with commit access in the last year or so.
We ask people to note non-trivial changes to a CHANGELOG and post to
API_CHANGES when there are API changes.  This has worked fairly well
and I haven't seen any abuse or rogue commits to date.  I recently
purged anyone who hasn't made a commit in they last year just to keep
the list manageable.


More information about the Scipy-dev mailing list