Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
Oops, s/make clean/make check ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
On Fri, Apr 5, 2013 at 1:56 AM, Dieter Verfaillie wrote: > The .doap file is incomplete and/or outdated. > The most recent active maintainer is/was John > Stowers . Thank you, E-mail sent. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
FYI, as noted in https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/981376/comments/4 There is older bug with patch but unfortunately seems unnoticed at all. https://bugzilla.gnome.org/show_bug.cgi?id=660216 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
On Sat, Apr 6, 2013 at 2:42 AM, Federico Mena Quintero wrote: > I've pushed Owen's patch from bug #660216, as it also contains fixes for > two other leaks. There seem to have another duplicate bug: https://bugzilla.gnome.org/show_bug.cgi?id=599730 > I've also pushed a little update to pygtk.doap to list John Stowers as > the last active maintainer, per Dieter's mail > (https://mail.gnome.org/archives/desktop-devel-list/2013-April/msg00085.html). Thank you for your work! > If you want, I can guide you through the basic process of making a > release. I tried a quick "autogen.sh" of pygtk and it doesn't work, but > I didn't actually check to see if it is due to me not having some of the > dependencies for building Gnome 2 stuff, or if pygtk's autofoo is just > bit-rotten. I guess that would be your first task - sorry that it's not > the most fun thing in the world to start with, but a maintainer's life > is hard :) I don't know what you mean by "it doesn't work" As I tried on an Ubuntu 12.04 box. There some glitches during the execution of autogen.sh, seemingly ignorable. Some "Could not write XXX" during the build (make), doesn't sound good. http://paste.ubuntu.com/5681985/ 3 out of 103 tests failed during "make clean" > Also, please read the following: > > https://live.gnome.org/MaintainersCorner > https://live.gnome.org/MaintainersCorner/Releasing > https://git.gnome.org/browse/pygtk/tree/docs/random/release-checklist > > It may all seem overwhelming at first, but it becomes second nature > after the first two or three release tarballs you make. > > Please ask John Stowers if he'd agree to pass maintainership on to you, > starting with making a release tarball. > > The MATE team is interested in keeping the maintainership of Gnome 2 > going, so if you are not in contact with them already, please do so! > I'm sure they can help you with infrastructural stuff. Thank you for your information. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
On Fri, 2013-04-05 at 01:23 +0800, Ma Xiaojun wrote: > If you can trust me, I had fun with writing a Python 3.2 extension > recently (using plain C/API), this is not open sourced yet. > > I know some basic Git, honestly need to learn branching stuff though. > > My vision: > Currently I'm only motivated by previously mentioned bug. > But I'm also become a bit more interested after hearing some bug statistics. Good; thanks for stepping up to keep the maintanership of pygtk going. I've pushed Owen's patch from bug #660216, as it also contains fixes for two other leaks. I've also pushed a little update to pygtk.doap to list John Stowers as the last active maintainer, per Dieter's mail (https://mail.gnome.org/archives/desktop-devel-list/2013-April/msg00085.html). If you want, I can guide you through the basic process of making a release. I tried a quick "autogen.sh" of pygtk and it doesn't work, but I didn't actually check to see if it is due to me not having some of the dependencies for building Gnome 2 stuff, or if pygtk's autofoo is just bit-rotten. I guess that would be your first task - sorry that it's not the most fun thing in the world to start with, but a maintainer's life is hard :) Also, please read the following: https://live.gnome.org/MaintainersCorner https://live.gnome.org/MaintainersCorner/Releasing https://git.gnome.org/browse/pygtk/tree/docs/random/release-checklist It may all seem overwhelming at first, but it becomes second nature after the first two or three release tarballs you make. Please ask John Stowers if he'd agree to pass maintainership on to you, starting with making a release tarball. The MATE team is interested in keeping the maintainership of Gnome 2 going, so if you are not in contact with them already, please do so! I'm sure they can help you with infrastructural stuff. Federico ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
I appreciate that you are doing something constructive and trying to learn. Thank you. It goes a long way in building trust and friendship. sri On Thu, Apr 4, 2013 at 10:23 AM, Ma Xiaojun wrote: > ( I registered "ubunturocks" just to make some fun about Microsoft, > don't get me wrong. ) > > I'm sorry to many people as I was a rude asshole. > > It seems that no one else want to take PyGTK even after my harsh > request, OK, let me give a try. > > My skills: > I definitely know C, some C++, some Python (both 2 and 3) also Bash, > PHP, JS, MATLAB, Java, C#, BASIC, whatever. > ( I have non-trivial project experience with all above languages, but > I honestly may only have used a limited set of available features in > many languages. ) > > If you can trust me, I had fun with writing a Python 3.2 extension > recently (using plain C/API), this is not open sourced yet. > > I know some basic Git, honestly need to learn branching stuff though. > > My vision: > Currently I'm only motivated by previously mentioned bug. > But I'm also become a bit more interested after hearing some bug > statistics. > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
On 2013-04-04 19:33, Stef Walter wrote: https://git.gnome.org/browse/pygtk/tree/pygtk.doap The .doap file is incomplete and/or outdated. The most recent active maintainer is/was John Stowers . Regards, Dieter ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Apologize and to take PyGTK (was: How long should it take to fix a obvious memory leak?)
On 04.04.2013 19:23, Ma Xiaojun wrote: > ( I registered "ubunturocks" just to make some fun about Microsoft, > don't get me wrong. ) > > I'm sorry to many people as I was a rude asshole. > > It seems that no one else want to take PyGTK even after my harsh > request, OK, let me give a try. Each GNOME module has one or more maintainers, whether or not they actually maintain anything (anymore), heh. So to take on a module, first ask the previous module mantainers. They're listed in a doap file, like here: https://git.gnome.org/browse/pygtk/tree/pygtk.doap People are almost always willing to help a new maintainer take over modules they no longer have time for, or interest in. If the listed maintainers are completely unresponsive, that's when others might get involved WRT to taking over maintainership of a module. Cheers, Stef ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
