On Jan 3, 2008 11:40 AM, Titus Brown <titus at caltech.edu> wrote: > On Thu, Jan 03, 2008 at 11:15:04AM -0800, Guido van Rossum wrote: > -> We're getting a fair number of doc contributions, especially since the > -> docs were converted from Latex to ReST, and especially since the start > -> of the GHOP project. > -> > -> My main gripe is with code contributions to Py3k and 2.6; Py3k is > -> mostly done by a handful of people, and almost nobody is working much > -> on 2.6. > > What needs to be done with 2.6? I'm happy to review patches, although > even were commit access on offer I'm too scatterbrained to do a good job > of it. IMO the main issue with 2.6 is not handling bugs and patches but backporting 3.0 stuff. There's a spreadsheet somewhere that shows there's a huge amount of work to be done: http://spreadsheets.google.com/ccc?key=pCKY4oaXnT81FrGo3ShGHGg (if you can't access it, try the published version: http://spreadsheets.google.com/pub?key=pCKY4oaXnT81FrGo3ShGHGg ) > Incidentally, I'm planning to set up an SVK repos containing the GHOP > doc patches; that way they can stay sync'ed with 2.6 work. I'd be happy > to do the same thing with reviewed-and-probably-OK patches, although I > don't know if repository proliferation is a generally good idea ;). IMO patches should just be applied to the trunk ASAP. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4