On 1/8/2011 9:18 PM, Victor Stinner wrote:
> Hi,
>
> The process to gain the commit priviledges is long, and it is sometimes
> difficult to decide if someone should have it or not. Would it be
> possible to have different "levels" of commit priviledes to simplify the
> process? Eg. first only be able to commit on a specific module, and then
> maybe more modules, to finally be able to commit everywhere. It doesn't
> need to be a technical limitation.
'Limited' privileges have been granted in the past, especially with GSOC
students. The 'limit' is by agreement (and the fact that all commits are
public to python-checkins subscribers.
Last summer, Guido discovered that the real problem is not overuse of
privileges, but underuse. Some people have be given commit access and
never used it. As a neophytes, I can imagine that some are too scared of
making an embarrassing mistake.
> The idea is to [involve] more people in the Python development and
recognize
> their work.
Until we start fighting over a limited supply of issues, we can use a
few more ;-)/
> I would be happy to be the mentor of someone even if I don't have
> suggestion currently.
In general, I believe more mentoring could be useful. Possible
suggestion: find someone without commit access who has submitted a patch
for an issue of interest to you that you think should get a committed
patch. Review it and as necessary help the person improve it until you
think it ready to commit. (You could even ask if they want that or
really want someone to take it over from them.) Then commit it. Or help
a new person *with* access and let (help) them commit it.
---
Terry Jan Reedy
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
