Over the past week, a lot of Bugzilla triage has been done, and quite a few bugs closed or fixed. Gustavo Carneiro, Johan Dahlin, Xavier Orduquoy, Lorenzo Gil Sanchez and Erik Grinaker have done some great work and we managed to close a number of bugs; you can see the code changes by following the Bonsai link below:
http://cvs.gnome.org/bonsai/cvsquery.cgi?treeid=default&branch=HEAD&branchtype=match&dir=gnome-python%2Fpygtk&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=month&mindate=&maxdate=&cvsroot=%2Fcvs%2Fgnome I'm trying to put together some permanent resources on pygtk.org to make it easier for people to find out what sort of tasks you can take up to help the project. I'll be working on http://pygtk.org/developer.html (though the page may take some time to update given our cvs autoupdater isn't going yet), and I'll be adding some links and queries to make it easier to find out how we're doing. I've started out by creating a [EMAIL PROTECTED] Bugzilla account, to which bugs that aren't being worked on by anybody will be assigned. This will make it easier for other people to pick a bug to help us out. If you're working on a bug over a period of time, it's a good idea to reassign this bug from the default to yourself; if you need to drop it for any reason, just reassign to [EMAIL PROTECTED] I'd like to encourage users to file bugs in Bugzilla, and help us triage out whatever is wrong or missing in PyGTK and gnome-python for you. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
