On Wed, 2004-02-18 at 15:03, Xavier Ordoquy wrote: > At the moment we will try to flush a bit the bugzilla patch and bugs > pending.
Cool, that would be a good place to start. There seems to be quite a few of us willing to do an effort, so we should be able to pull this off within a reasonable timeframe. Now, I've been thinking a bit about how we should organize this, and have a few issues I'd like to discuss. - should we explicitly notify james and the rest of the guys, and get some of his thoughts on this? doesn't seem like he's reading the list nowadays... - should we start by doing a bugfix / extension release of the 2.0.x series, or do a release for gtk+ 2.2 / gnome 2.4, or just start working on a complete 2.4 / 2.6 right away? - should we set up a new pygtk-devel mailing list (I don't know if there's one already), or just use the normal pygtk list and the bugzilla to communicate? - how do we do the development? should we submit patches against the current cvs, get write access (at least a couple of us) to cvs, or set up our own cvs tree? - i'd really like to put an emphasis on documentation. I don't know how this is handled currently, but since pygtk will be the first contact many people have with gtk I think good-quality docs are very important. The current docs are not at all bad, but they could be improved and there doesn't seem to be any python-gnome documentation at all. -- Erik Grinaker <[EMAIL PROTECTED]> http://erikg.wired-networks.net/ "We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about." -- Albert Einstein _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
