Mailman 3 January 2011 - python-committers

rc delayed, waiting for Mac issues
by Georg Brandl 09 Jan '11

09 Jan '11

Hi, you may have noticed that 3.2rc1 was planned for today. Since there are quite a few critical Mac issues unresolved, Ned's contacted Ronald about them, but we haven't heard back yet. I'm going to delay the rc for a few days to give him a bit of time (if maybe has was on vacation this past week). cheers, Georg

1 0

Commit privileges for Eli Bendersky
by Terry Reedy 09 Jan '11

09 Jan '11

Two years ago, Eli Bendersky submitted to the tracker one of several duplicate reports about problems with difflib.SequenceMatcher. After I consolidated and closed all issues but one, he wrote me, said he wanted to get more involved in Python development, and offered to help with that and other issues. Since then he has actively participated in 34 issues, submitting 1 or more patches to 20 issues, listed below. Of those, 14 are closed. I believe his work always or nearly always contributed to the commit. Another has been committed to 3.2 and is only open for backports and possible tweaks. Another is waiting for 3.3, another for my response. His activity has covered core, library, and doc issues. He can work on C, Python, and .rst code and text He has shown himself to be a careful reader of both code and text. He has also participated a bit on pydev. I believe he said last September, in private email in response to my query, that he would like full developer privileges 'someday'. Before I reviewed his tracker activity, I was merely going to recommend that we 'start thinking about' a promotion. But then I discovered that he had done much I did not know about, as several developers (me, Alexander B, Georg B. Eric A, Michael F., ...) have done commits involving his patches. So I now think, 'why wait?' I am confident that he will start with whatever cautions he is given, with issues that are either trivial or that have been reviewed by others. http://bugs.python.org/issue9132 http://bugs.python.org/issue9282 http://bugs.python.org/issue9214 http://bugs.python.org/issue1397474 needs comment from me http://bugs.python.org/issue9323 http://bugs.python.org/issue9315 http://bugs.python.org/issue9317 open http://bugs.python.org/issue10439 http://bugs.python.org/issue10470 http://bugs.python.org/issue9222 http://bugs.python.org/issue10468 http://bugs.python.org/issue766910 open http://bugs.python.org/issue10534 http://bugs.python.org/issue10693 http://bugs.python.org/issue9312 http://bugs.python.org/issue9264 open for backport http://bugs.python.org/issue10461 http://bugs.python.org/issue10801 http://bugs.python.org/issue10516 waiting for 3.3 http://bugs.python.org/issue10594 -- Terry Jan Reedy

5 4

Commit rights for Ned Deily
by Antoine Pitrou 09 Jan '11

09 Jan '11

Hello, Based on his work to diagnose and fix many issues related to OS X and/or IDLE/tk, I would like to propose that we give Ned Deily commit rights. He seems to already have developer rights on the tracker. Regards Antoine.

5 5

Partial commit privileges
by Victor Stinner 09 Jan '11

09 Jan '11

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. The idea is to imply more people in the Python development and recognize their work. I remember that a rule to imply someone into the Python development is that we look for people in the long-term. Is the artial commit privilege compatible with this rule? What do you think? Would it be dangerous? As the current process, we should have mentors, maybe more than one mentor for one new developer. I would be happy to be the mentor of someone even if I don't have suggestion currently. Victor

5 4