[Python-Dev] Reviewed patches [was: SoC proposal: "fix some old, old bugs in sourceforge"]

[Jim Jewett]

> If there are too many patches waiting for a committer to assess them,
> that probably points up the need for more committers.

Perhaps; part of the problem is with the SF workflow.

New bug or patch comes in.  Shows up on the list of new bugs, but not
obviously ready for action.  Not assigned to anyone, because it says
not to.

Patch added.  email sent to anyone who made an explicit comment, but
perhaps not to any committers.

More comments.

More patches.

Finally ready.

Another comment is made, maybe saying so, but certainly not with any
magic words.

The patch isn't even on the front page any more.

...

So how are the committers supposed to even know that it is waiting for
assessment?  The solutions that I've seen work are

(a)  A committer gets involved (at least to be sent email) early
(b)  Someone bugs a committer out of band (despite the don't-assign rhetoric)
(c)  It gets fixed really fast, before it can fall off the first screen
(d)  Someone (such as Georg, recently) makes a point of going through
old tickets almost at random.

These are all pretty ad-hoc

-jJ