j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
Guido van Rossum wrote:
It's official: I've changed the patch submission guidelines (http://www.python.org/patches/) to point to the patch manager at SourceForge. We are no longer bound by CNRI's legal department, so the requirement for disclaimers or wet signatures is gone.
We'll have to see how it works in practice. I've set the address where new patches are mailed to email@example.com; this should send notifications to the patches list. We could change this to python-dev perhaps, so we can retire the patches address completely (giving it an auto-respond pointing to the SF patch manager, as barry suggested).
Will there be a list which gets the patches mailed to it by SF ?
I'm just asking because the current setup of having the patches available through mail really helps in discussing patch details.
There are several tasks to be assigned now: we need a triage person who should go through the list of new patches regularly to assign them to developers; we need developers who are willing to have patches assigned to them.
I'll volunteer for the Unicode side of things :-)
We also need a consensus process to decide which patches will be allowed through. I'm hoping to experiment with SF in the coming days to come up with something.
Finally, we still need to do something about the existing backlog of patches. The PythonLabs team will try to do something reasonable here.
This is not the end -- it's the beginning!
-- Marc-Andre Lemburg