Formal request: non-responsive maintainer Gavin Romig-Koch for squeak-vm
Bug here, with no response: https://bugzilla.redhat.com/show_bug.cgi?id=861970 Gavin isn't responding to bugs or to email. Note that also note that Jaroslav Škarvada has an updated package in testing, has asked to become a co-maintainer, and in fact has been trying to get a response for almost a year. I checked with Jaroslav and he's still ready to take over. I'm an interested party because I want to package Scratch, and an updated Squeak VM will significantly simplify that package -- and make sound work. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Formal request: non-responsive maintainer Gavin Romig-Koch for squeak-vm
On Mon, 22 Oct 2012 12:04:59 -0400 Matthew Miller mat...@fedoraproject.org wrote: Bug here, with no response: https://bugzilla.redhat.com/show_bug.cgi?id=861970 Gavin isn't responding to bugs or to email. Note that also note that Jaroslav Škarvada has an updated package in testing, has asked to become a co-maintainer, and in fact has been trying to get a response for almost a year. I checked with Jaroslav and he's still ready to take over. I'm an interested party because I want to package Scratch, and an updated Squeak VM will significantly simplify that package -- and make sound work. As a FESCo member I will ack this per the process. I'm going to reassign the squeak-vm package now. In addition, gavin also maintains: collection | package name | description | owner | co-maintainers/cc Fedora|etoys|A media-rich model, game, and simulation construction kit and authoring tool|gavin||dcorking,sdz,tuxbrewr Fedora|fastback|File uploader, configureable file uploader|gavin|| Fedora|report|Incident reporting library|gavin||jmoskovc Fedora|squeak-image|The image files for Squeak|gavin||dcorking,jskarvad,tuxbrewr Fedora|squeak-vm|The Squeak virtual machine|gavin||dcorking,jskarvad,tuxbrewr Fedora EPEL|fastback|File uploader, configureable file uploader|gavin|| Fedora EPEL|report|Incident reporting library|gavin|| If anyone would like to take over any of these packages, please let me know. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Formal request: non-responsive maintainer Gavin Romig-Koch for squeak-vm
If anyone would like to take over any of these packages, please let me know. I will also take squeak-image thanks regards Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Formal request: non-responsive maintainer Gavin Romig-Koch for squeak-vm
On Mon, 22 Oct 2012 17:17:53 -0400 (EDT) Jaroslav Skarvada jskar...@redhat.com wrote: If anyone would like to take over any of these packages, please let me know. I will also take squeak-image Done. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive maintainer: Lubomir Rintel (cglib, jfreechart)
Hi, I'm currently trying to get OSGi metadata added to the cglib and jfreechart packages. Unfortunately I've heard no response for ~3 weeks. Does anybody know how to contact him (bug-email of maintainer CC'd)? I'm willing to take ownership/co-maintenance of cglib and jfreechart, fwiw. Bugzilla links: https://bugzilla.redhat.com/show_bug.cgi?id=854249 https://bugzilla.redhat.com/show_bug.cgi?id=848503 https://bugzilla.redhat.com/show_bug.cgi?id=842744 Cheers, Severin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer: Lubomir Rintel (cglib, jfreechart)
On Mon, Sep 17, 2012 at 4:22 AM, Severin Gehwolf sgehw...@redhat.com wrote: Hi, I'm currently trying to get OSGi metadata added to the cglib and jfreechart packages. Unfortunately I've heard no response for ~3 weeks. Does anybody know how to contact him (bug-email of maintainer CC'd)? I'm willing to take ownership/co-maintenance of cglib and jfreechart, fwiw. Bugzilla links: https://bugzilla.redhat.com/show_bug.cgi?id=854249 https://bugzilla.redhat.com/show_bug.cgi?id=848503 https://bugzilla.redhat.com/show_bug.cgi?id=842744 CCd FP email. -J Cheers, Severin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive Maintainer for pdns
Hello, Currently there are no working pdns (PowerDNS) builds for Fedora 18, because the maintainer is unavailable. 3 weeks ago I sent an email to the maintainer (Ruben), but so far no response. Yesterday, I sent him an email if he accepted me as co-maintainer for pdns, but again, no response. Does anyone know how to contact him? Otherwise, I have built working pdns packages for F18. See: https://bugzilla.redhat.com/show_bug.cgi?id=856825 Best regards, Morten -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive Maintainer for pdns
On Fri, 14 Sep 2012, Morten Stevens wrote: Currently there are no working pdns (PowerDNS) builds for Fedora 18, because the maintainer is unavailable. 3 weeks ago I sent an email to the maintainer (Ruben), but so far no response. Yesterday, I sent him an email if he accepted me as co-maintainer for pdns, but again, no response. Does anyone know how to contact him? He is known to be away for a few days. I've pinged upstream about it, and they would contact him. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non responsive maintainer: lkundrak
Hi, Does someone know how to contact lkundrak ? I have requested a jgraphx update (scilab dependency) for months. Account Name: lkundrak Full Name: Lubomir Rintel Email: lkund...@v3.sk IRC Nick: lkundrak Account Status: Active Bug: (open 2011-10-15, ping 2011-10-24, 2011-12-13, 2012-02-09, 2012-03-13) https://bugzilla.redhat.com/show_bug.cgi?id=746391 Direct request for co-maintainer via pkgdg without answer. Direct email without answer. Without response, I would like to take ownership of jgraphx (scilab direct dependency) Clément davidcl DAVID -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: lkundrak
On Tue, 2012-03-20 at 13:37 +0100, Clément David wrote: Hi, Does someone know how to contact lkundrak ? $ ./fedora_active_user.py --user lkundrak --email lkund...@v3.sk Last login in FAS: lkundrak 2012-03-20 Last action on koji: Tue, 21 Feb 2012 package list entry created: perl-OpenOffice-UNO in dist-6E-epel by pkgdb [still active] Last package update on bodhi: 2012-02-20 13:33:05 on package perl-Net-IRC-0.79-3.el6 658 bugs assigned or cc to lkund...@v3.sk Bugzilla information: [...] He seems to still be around and based on the number of bugs assigned or cc to him, he might just be busy. When did you request acl on pkgdb? Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: lkundrak
On Tue, Mar 20, 2012 at 7:46 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, 2012-03-20 at 13:37 +0100, Clément David wrote: Hi, Does someone know how to contact lkundrak ? $ ./fedora_active_user.py --user lkundrak --email lkund...@v3.sk Last login in FAS: lkundrak 2012-03-20 Last action on koji: Tue, 21 Feb 2012 package list entry created: perl-OpenOffice-UNO in dist-6E-epel by pkgdb [still active] Last package update on bodhi: 2012-02-20 13:33:05 on package perl-Net-IRC-0.79-3.el6 658 bugs assigned or cc to lkund...@v3.sk Bugzilla information: [...] He seems to still be around and based on the number of bugs assigned or cc to him, he might just be busy. When did you request acl on pkgdb? He's usually pretty busy, and has in the past been receptive to co-maintainers. If you need assistance, I doubt he'd object to reasonable actions being taken be provenpackagers. If you need one for that purpose, I can help. -J Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: lkundrak
Hi, Right, it was busy. I got the ACLs for co-maintaining jgraphx now. PS: that was just a gentle ACLs reminder :) Clément Le 20/03/2012 13:50, Jon Ciesla a écrit : On Tue, Mar 20, 2012 at 7:46 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, 2012-03-20 at 13:37 +0100, Clément David wrote: Hi, Does someone know how to contact lkundrak ? $ ./fedora_active_user.py --user lkundrak --email lkund...@v3.sk Last login in FAS: lkundrak 2012-03-20 Last action on koji: Tue, 21 Feb 2012 package list entry created: perl-OpenOffice-UNO in dist-6E-epel by pkgdb [still active] Last package update on bodhi: 2012-02-20 13:33:05 on package perl-Net-IRC-0.79-3.el6 658 bugs assigned or cc to lkund...@v3.sk Bugzilla information: [...] He seems to still be around and based on the number of bugs assigned or cc to him, he might just be busy. When did you request acl on pkgdb? He's usually pretty busy, and has in the past been receptive to co-maintainers. If you need assistance, I doubt he'd object to reasonable actions being taken be provenpackagers. If you need one for that purpose, I can help. -J Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Mon, 2011-12-05 at 23:08 +0100, Pierre-Yves Chibon wrote: (download via git clone http://ambre.pingoured.fr/cgit/fedora-misc.git/ ) Move to its own repo on: http://ambre.pingoured.fr/cgit/fedora-active-user.git/ Mirrored on github at: https://github.com/pypingou/fedora-active-user Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/12/11 23:08, Pierre-Yves Chibon wrote: Hi, Once in a while comes back the question: is insert nick here around ? Normally followed by: I have opened and pinged him several time on bugzilla #/email/irc/insert what I missed here. Great work! There was/is some tool around/mentioned some time doing nearly the same. Is this yours? Did it someone else? I would check some other mailing lists, too,e.g. t...@lists.fedoraproject.org, Some people are hanging in irc, too. irc-nick is listed in fedora account system. I would watch on channels #fedora, #fedora-devel and maybe in #fedora-(lang), if country is listed in fas. There is a vacation list in wiki https://fedoraproject.org/wiki/Vacation which may be checked, too. Should vacation be moved to fas? Hope this helps and feel free to give suggestions, Pierre - -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO3d3uAAoJEOnz8qQwcaIWgBcH/j7dAGr59qJutob1uf+Ksl94 70Mm14Wt5asLH5RMDDuefTyHQOznBMzVzrSpdiFOEHBVZEil/F7xBuzcrIy3aFFn MCHh7gSRHhD9S64rVyYyEqO7cL7HvQM/pXx5kDGiY5nSypawBvjw5MBw7X/Ja651 +zX0p1ObcZ+IAW7Ue5EYuVTESUBzFct2Im983bfnEJHbEFSqTqdotnlv9fBbL5j1 NZXJUYB7biWonYvIVanXMBt94EFGXtyCZbOrEy18bsAq2KUQ/U8u9gt19pJjoY7G 2MN1CQWMJID1fS00i64rAI6OUvGO1geiabxiXpwF4oGxsoSGgQKgJ3ycAUVD1Bw= =IaI6 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
2011/12/5 Pierre-Yves Chibon pin...@pingoured.fr: - koji ➙ last build... This doesn't seem to work correctly. My last build was 2 days ago: http://koji.fedoraproject.org/koji/userinfo?userID=988 And the script says it was Nov 2... Otherwise a great start :) Thanks, Tom -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, 2011-12-06 at 11:07 +0100, Thomas Spura wrote: 2011/12/5 Pierre-Yves Chibon pin...@pingoured.fr: - koji ➙ last build... This doesn't seem to work correctly. My last build was 2 days ago: http://koji.fedoraproject.org/koji/userinfo?userID=988 And the script says it was Nov 2... That is indeed a bug, I am looking into it but atm I cannot find where it comes from, I'll have to dig further. Thanks for pointing it out! Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, 2011-12-06 at 10:18 +0100, Matthias Runge wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/12/11 23:08, Pierre-Yves Chibon wrote: Hi, Once in a while comes back the question: is insert nick here around ? Normally followed by: I have opened and pinged him several time on bugzilla #/email/irc/insert what I missed here. Great work! There was/is some tool around/mentioned some time doing nearly the same. Is this yours? Did it someone else? It was not me no, this is like a couple of days old, but the idea came from this list (maybe from you, I don't remember who made this remark). Some people are hanging in irc, too. irc-nick is listed in fedora account system. I would watch on channels #fedora, #fedora-devel and maybe in #fedora-(lang), if country is listed in fas. For this, I guess the nicest would be if I could query zodbot or something, but to be honest I don't feel like coding in an irc client just to ask zodbot .seen chan nick. There is a vacation list in wiki https://fedoraproject.org/wiki/Vacation which may be checked, too. Should vacation be moved to fas? Since one has to log in to edit this page this should be covered (more or less) by the info of the last log in in FAS, but true this would give an estimate time of return to life :-) Sochotni had some ideas on how we may improve this Vacation system. Thanks for the feedback, Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, 6 Dec 2011 10:26:00 + Daniel P. Berrange berra...@redhat.com wrote: It might be interesting to run this script across every single user in the Fedora accounts system, and proactively identify any users whom have not done anything in Fedora for a period longer than say 6-9 months. Yeah, it's worth noting however, that anyone who hasn't been active in the last 3 months or so likely didn't reset their password and upload a new ssh key, so their account would be marked inactive. But this might find some people who were active in say bugzilla but missed the fas changes, etc. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On 12/06/2011 05:26 AM, Daniel P. Berrange wrote: On Mon, Dec 05, 2011 at 11:08:32PM +0100, Pierre-Yves Chibon wrote: snip It might be interesting to run this script across every single user in the Fedora accounts system, and proactively identify any users whom have not done anything in Fedora for a period longer than say 6-9 months. Daniel If we have a FAS account and don't use it often but review several fedora lists weekly, would we show up in this scenario? -- Regards, OldFart -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, 2011-12-06 at 10:53 -0700, Kevin Fenzi wrote: But this might find some people who were active in say bugzilla but missed the fas changes, etc. Just for reference, the bugzilla check doesn't work on F16, something changed between the version 0.6.0 and 0.6.2 and what's returned has changed so I cannot compare the email of the comments. I'll have to see with wwoods on that. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, 2011-12-06 at 13:52 -0500, Clyde E. Kunkel wrote: On 12/06/2011 05:26 AM, Daniel P. Berrange wrote: On Mon, Dec 05, 2011 at 11:08:32PM +0100, Pierre-Yves Chibon wrote: snip It might be interesting to run this script across every single user in the Fedora accounts system, and proactively identify any users whom have not done anything in Fedora for a period longer than say 6-9 months. Daniel If we have a FAS account and don't use it often but review several fedora lists weekly, would we show up in this scenario? It does check few mailing-list through gmane, more can be added of course. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
2011/12/6 Kevin Fenzi ke...@scrye.com: On Tue, 6 Dec 2011 10:26:00 + Daniel P. Berrange berra...@redhat.com wrote: It might be interesting to run this script across every single user in the Fedora accounts system, and proactively identify any users whom have not done anything in Fedora for a period longer than say 6-9 months. Yeah, it's worth noting however, that anyone who hasn't been active in the last 3 months or so likely didn't reset their password and upload a new ssh key, so their account would be marked inactive. But this might find some people who were active in say bugzilla but missed the fas changes, etc. Hmm, will the packages of inactive account holders be orphaned then? Don't know of an example and if it's relevant at all... (Or if that's already implemented in pkgdb...) Greetings, Tom -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer ?
On Tue, Dec 06, 2011 at 09:44:33PM +0100, Thomas Spura wrote: 2011/12/6 Kevin Fenzi ke...@scrye.com: On Tue, 6 Dec 2011 10:26:00 + Daniel P. Berrange berra...@redhat.com wrote: It might be interesting to run this script across every single user in the Fedora accounts system, and proactively identify any users whom have not done anything in Fedora for a period longer than say 6-9 months. Yeah, it's worth noting however, that anyone who hasn't been active in the last 3 months or so likely didn't reset their password and upload a new ssh key, so their account would be marked inactive. But this might find some people who were active in say bugzilla but missed the fas changes, etc. Hmm, will the packages of inactive account holders be orphaned then? Don't know of an example and if it's relevant at all... (Or if that's already implemented in pkgdb...) Packages of inactive accont holders will be orphaned in January. We decided in the last infra meeting that we'd go ahead with inactivating accounts now and give people some time to reset those in case they just missed the deadline. If they're still inactive in January (or sooner on a case by case basis), we'll orphan the packages so that people can pick them up if they're so inclined. -Toshio pgpm8ww7mhn4m.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive maintainer ?
Hi, Once in a while comes back the question: is insert nick here around ? Normally followed by: I have opened and pinged him several time on bugzilla #/email/irc/insert what I missed here. And there the hunt for the last trace of activity starts. Some days ago someone on the list was asking if there wasn't such a program that would help identifying if someone has been active recently. Well, I gave this a try. http://ambre.pingoured.fr/cgit/fedora-misc.git/tree/fedora_active_user.py (download via git clone http://ambre.pingoured.fr/cgit/fedora-misc.git/ ) This checks for the last activity on - FAS ➙ return the last time the user logged in on a Fedora web-app: wiki, fas, bodhi (requires FAS auth) - koji ➙ last build... - bugzilla ➙ this takes a while as it retrieves all the bugs on which the given email is either CC or Assigned and then check them all to return the date of the last comment by this user. - bodhi ➙ well this is not done yet (and I expect we will have similar results as before) but the patch which will allow it should make it to the next release - mailing lists ➙ For this I use gmane which allow to search for email coming from an email address. I used a define set of mailing list, this can of course be extended. output: ./fedora_active_user.py --user pingou --email=pin...@pingoured.fr --nobz Last login in FAS: FAS password for pingou: pingou 2011-12-05 22:07:35.996974+00:00 Last action on koji: Fri Nov 11 14:35:20 2011 package list entry created: python-straight-plugin in dist-f11 by pkgdb [still active] Last action on Bodhi: Not yet implemented Last email on mailing list: 2011-12-03 gmane.linux.redhat.fedora.devel 2009-11-04 gmane.linux.redhat.fedora.artwork 2011-08-10 gmane.linux.redhat.fedora.epel.devel 2011-10-13 gmane.linux.redhat.fedora.extras.packaging 2011-12-01 gmane.linux.redhat.fedora.infrastructure Hope this helps and feel free to give suggestions, Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614982] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614982 Bug 614982 depends on bug 611015, which changed state. Bug 611015 Summary: perl-Pugs-Compiler-Rule fails to build https://bugzilla.redhat.com/show_bug.cgi?id=611015 What|Old Value |New Value Resolution||RAWHIDE Status|ASSIGNED|CLOSED -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Non-responsive Maintainer: Andreas Osowski (th0br0)
Hello, all. I have been trying to contact Andreas Osowski (CC-ed) about updating Almanah to upstream 0.8.0 (bug 720544 [1]). I have pinged him twice on this bug report (once on August 19 and again on September 3). I also emailed him directly just over two days ago; but have unfortunately received no response to any of these inquiries. I also attempted to contact him on IRC (user th0br0 on Freenode); but his WHOIS shows him unavailable (Auto Away at Fri Jul 8 23:14:02 2011). He is not listed on the Vacation wiki page [2]; and his user info page [3] shows his current status as Active. According to Koji, his last activity was a rebuild of the mumble package, dated September 12. In accordance with the Fedora Non-responsive Maintainer Policy [4], does anyone know an alternative method to contact Andreas? Thank you, and regards. [1] https://bugzilla.redhat.com/show_bug.cgi?id=720544 [2] https://fedoraproject.org/wiki/Vacation [3] https://admin.fedoraproject.org/accounts/user/view/th0br0 [4] https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers P.S. Andreas, if you're out there, please let us know! :-) -- Peter Gordon (codergeek42) pe...@thecodergeek.com Who am I? :: http://thecodergeek.com/about-me signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive Maintainer: Andreas Osowski (th0br0)
Hello all, sorry for this small hassle, I was planning to answer Peter's last e-mail tomorrow as I was unable to do so today. @Peter: The update is the first thing on my todo list for tomorrow together with a rebuild of mumble for F16 rawhide. - Andreas On Wed, Sep 14, 2011 at 11:50 PM, Peter Gordon pe...@thecodergeek.comwrote: Hello, all. I have been trying to contact Andreas Osowski (CC-ed) about updating Almanah to upstream 0.8.0 (bug 720544 [1]). I have pinged him twice on this bug report (once on August 19 and again on September 3). I also emailed him directly just over two days ago; but have unfortunately received no response to any of these inquiries. I also attempted to contact him on IRC (user th0br0 on Freenode); but his WHOIS shows him unavailable (Auto Away at Fri Jul 8 23:14:02 2011). He is not listed on the Vacation wiki page [2]; and his user info page [3] shows his current status as Active. According to Koji, his last activity was a rebuild of the mumble package, dated September 12. In accordance with the Fedora Non-responsive Maintainer Policy [4], does anyone know an alternative method to contact Andreas? Thank you, and regards. [1] https://bugzilla.redhat.com/show_bug.cgi?id=720544 [2] https://fedoraproject.org/wiki/Vacation [3] https://admin.fedoraproject.org/accounts/user/view/th0br0 [4] https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers P.S. Andreas, if you're out there, please let us know! :-) -- Peter Gordon (codergeek42) pe...@thecodergeek.com Who am I? :: http://thecodergeek.com/about-me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Resolved] Re: Non-responsive Maintainer: Andreas Osowski (th0br0)
On 09/14/2011 02:57 PM, Andreas Osowski wrote: Hello all, sorry for this small hassle, I was planning to answer Peter's last e-mail tomorrow as I was unable to do so today. @Peter: The update is the first thing on my todo list for tomorrow together with a rebuild of mumble for F16 rawhide. Thanks for the heads-up, Andreas. Good to hear that you're alright and working on it. I'll calm down now. =) -- Peter Gordon (codergeek42) pe...@thecodergeek.com Who am I? :: http://thecodergeek.com/about-me signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non responsive maintainer : gouldwp [FORMAL REQUEST]
Hi, I'm following http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers It seems gouldwp is non-responsive. User: gouldwp, Name: None, email: w...@gouldfamily.org, Creation: 2008-01-19, Status: active Approved Groups: cla_fpca cla_fedora fedorabugs cla_done packager * Bug (open 2011-08-06, ping 2011-08-25) https://bugzilla.redhat.com/show_bug.cgi?id=728665 * Direct request for co-maintainer via pkgdb without answer * Direct email without answer * Last build from gouldwp : 2009-11-09 http://koji.fedoraproject.org/koji/userinfo?userID=591 * Mail to devel ML (CC to gouldwp) : 04/09/2011 Without response, I like to take ownership on perl-Net-NBName (required by another package I own) Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non responsive maintainer : gouldwp
Hi, It seems gouldwp is non-responsive. User: gouldwp, Name: None, email: w...@gouldfamily.org, Creation: 2008-01-19, Status: active Approved Groups: cla_fpca cla_fedora fedorabugs cla_done packager Bug (open 2011-08-06, ping 2011-08-25) https://bugzilla.redhat.com/show_bug.cgi?id=728665 Direct request for co-maintainer via pkgdb without answer Direct email without answer Last build from gouldwp : 2009-11-09 http://koji.fedoraproject.org/koji/userinfo?userID=591 Without response, I like to take ownership on perl-Net-NBName (required by another package I own) Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
On Sat, 09 Apr 2011 11:14:54 -0700 Christopher Aillon cail...@redhat.com wrote: On 11/15/2010 08:57 AM, Kevin Fenzi wrote: On Mon, 15 Nov 2010 05:16:43 -0500 (EST) Jaroslav Skarvadajskar...@redhat.com wrote: Please could any FESCo member approve the takeover of rrdtool (according to nonresponsive package maintainers policy)? Or should I open ticket for this? I'll approve it and orphan rrdtool. Five months later and Chris Ricker (kaboom) is still MIA. Yeah. ;( I sure hope he's ok. I'd like to propose we orphan all his packages. https://admin.fedoraproject.org/pkgdb/users/packages/kaboom as nothing's really changed since the nonresponsive maintainer process was invoked on him. I'll take gnuchess and xboard. Sounds reasonable. I sent him another email with no reply as well. Toshio is going to orphan his packages later today... kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
On Mon, Apr 11, 2011 at 11:53:41AM -0600, Kevin Fenzi wrote: On Sat, 09 Apr 2011 11:14:54 -0700 Christopher Aillon cail...@redhat.com wrote: I'd like to propose we orphan all his packages. https://admin.fedoraproject.org/pkgdb/users/packages/kaboom as nothing's really changed since the nonresponsive maintainer process was invoked on him. I'll take gnuchess and xboard. Sounds reasonable. I sent him another email with no reply as well. Toshio is going to orphan his packages later today... Orphaned. Feel free to take. -Toshio pgpJtUSxr911p.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
On 11/15/2010 08:57 AM, Kevin Fenzi wrote: On Mon, 15 Nov 2010 05:16:43 -0500 (EST) Jaroslav Skarvadajskar...@redhat.com wrote: Please could any FESCo member approve the takeover of rrdtool (according to nonresponsive package maintainers policy)? Or should I open ticket for this? I'll approve it and orphan rrdtool. Five months later and Chris Ricker (kaboom) is still MIA. I'd like to propose we orphan all his packages. https://admin.fedoraproject.org/pkgdb/users/packages/kaboom as nothing's really changed since the nonresponsive maintainer process was invoked on him. I'll take gnuchess and xboard. In addition to the evidence raised by Jaroslav Skarvada in November, attempts to contact him still are failing. Also * all 8 of the 8 open bugs assigned to kaboom[1] have had zero activity from him including # 593629 [2] is an upstream release monitor bug which shows multiple upstream releases with no response going back to nearly a year ago (May 2010) # 646466 [3] is for the Remove Setuid F15 feature[4] filed in Oct 2010 with no response. # There's also a second upstream release monitor bug, a FTBFS bug, and two crash bugs there, as well as a bug going back to 2007, all with no response. * he has only ever commented on 11 [5] of his 46 [6] assigned bugs, the last comment coming in 2008, and most of his bugs being closed by other contributors. (this doesn't count any which were re-assigned to others due to lack of response, such as the rrdtool bugs). * Also of note, the last activity I can find from him in bugzilla is end of 2009 when he filed bug 538817 [7], well over a year since his last comment on any bug he had asignee responsibility on, and there were open bugs assigned to him at the time (eg 221344 and 485364). * kaboom's last koji build is well over a year ago.[8] * Google searches don't turn up anything on him in a few years, save for this non-responsive maintainer thread. [1] https://bugzilla.redhat.com/buglist.cgi?quicksearch=221344,485364,593629,622075,631091,632434,646466,672646 [2] https://bugzilla.redhat.com/593629 [3] https://bugzilla.redhat.com/646466 [4] https://fedoraproject.org/wiki/Features/RemoveSETUID [5] https://bugzilla.redhat.com/buglist.cgi?query_format=advancedemaillongdesc1=1field0-0-0=assigned_toemail1=kaboom%40oobleck.nettype0-0-0=equalsvalue0-0-0=kaboom%40oobleck.netemailtype1=exact [6] https://bugzilla.redhat.com/buglist.cgi?quicksearch=ALL+%40kaboom [7] https://bugzilla.redhat.com/538817 [8] http://koji.fedoraproject.org/koji/userinfo?userID=214 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
non-responsive maintainer for qcomicbook
Per https://bugzilla.redhat.com/show_bug.cgi?id=663151 I've not received any response in my attempts to make contact over the past couple of months, and would ask FESCo to approve my taking ownership. -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: non-responsive maintainer for qcomicbook
On Mon, 24 Jan 2011 07:58:43 -0600 Rex Dieter rdie...@math.unl.edu wrote: Per https://bugzilla.redhat.com/show_bug.cgi?id=663151 I've not received any response in my attempts to make contact over the past couple of months, and would ask FESCo to approve my taking ownership. I'll approve it as a fesco member... kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive maintainer: pysvn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been trying to contact the maintainer of pysvn for a few weeks (Since December 14th) but have not received a reply. According to Koji, the owner (ravenoak) has not been active since July. I'd like to formally request being added as a comaintainer of this package, as it is a broken dependency in EPEL 6 for one of the packages I maintain (ReviewBoard). I am also willing to assume comaintainership in Fedora. - -- Stephen Gallagher RHCE 804006346421761 Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk0iJbwACgkQeiVVYja6o6O2TQCgqcQP7Nxk63xd88wbCBIa4M6a TmYAoIDWaUYlynvgcFy42PyeookyONDU =4Jk1 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
non-responsive maintainer: Scott Baker
Anyone know how to contact Scott Baker, maintainer of qcomicbook? I've been attempting to contact him for a couple of months, and have started the non- responsive maintainer policy, https://bugzilla.redhat.com/show_bug.cgi?id=663151 -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614982] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614982 Iain Arnell iarn...@gmail.com changed: What|Removed |Added Status|NEW |CLOSED Resolution||NOTABUG Last Closed||2010-12-07 22:53:25 --- Comment #5 from Iain Arnell iarn...@gmail.com 2010-12-07 22:53:25 EST --- Oops. Should have closed this a while back. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
On Sat, 20 Nov 2010 07:14:41 +0100 Jan Kratochvil jan.kratoch...@redhat.com wrote: Hello, filed month+ ago: https://bugzilla.redhat.com/show_bug.cgi?id=643296 Simple fix of memory corruption affecting various applications incl. Firefox. Completed Policy for nonresponsive package maintainers there, got an off-list reply but still no fix commit or commit rights approval. Lennert is surely around... but I think it might be good to get a few motivated maintainers for the fedora package. (Folks who could triage bugs, pull commits from upstream, etc). Especially since Lennart is busy with systemd. Any folks willing to step up? Lennart: any folks you trust to do this or would be willing to help get up to speed? Just I am not going to takeover the package but requesting a commit right for this Bug - therefore for the package pulseaudio: https://admin.fedoraproject.org/pkgdb/acls/name/pulseaudio I'd suppose if it's just one commit and is urgent, it would be a job for a provenpackager, not a take over request. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
On Sat, 2010-11-20 at 14:52 -0700, Kevin Fenzi wrote: On Sat, 20 Nov 2010 07:14:41 +0100 Jan Kratochvil jan.kratoch...@redhat.com wrote: Hello, filed month+ ago: https://bugzilla.redhat.com/show_bug.cgi?id=643296 Simple fix of memory corruption affecting various applications incl. Firefox. Completed Policy for nonresponsive package maintainers there, got an off-list reply but still no fix commit or commit rights approval. Lennert is surely around... but I think it might be good to get a few motivated maintainers for the fedora package. (Folks who could triage bugs, pull commits from upstream, etc). Especially since Lennart is busy with systemd. Any folks willing to step up? Lennart: any folks you trust to do this or would be willing to help get up to speed? Just I am not going to takeover the package but requesting a commit right for this Bug - therefore for the package pulseaudio: https://admin.fedoraproject.org/pkgdb/acls/name/pulseaudio I'd suppose if it's just one commit and is urgent, it would be a job for a provenpackager, not a take over request. This doesn't feel appropriate to me, since it's obviously a patch which should go upstream if it goes anywhere. A provenpackager can't commit it to upstream PA. (note that Lennart doesn't check his redhat.com email much, he prefers the poettering.net address). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
On Sat, 20 Nov 2010 22:52:51 +0100, Kevin Fenzi wrote: but I think it might be good to get a few motivated maintainers for the fedora package. Also think so. Twinkle sound is choppy when using pulseaudio, the details are not important here as I have not even filed it when the pulseaudio Bugs get ignored. I'd suppose if it's just one commit and is urgent, it would be a job for a provenpackager, not a take over request. Done by Matej Cepl mc...@redhat.com: https://admin.fedoraproject.org/updates/pulseaudio-0.9.21-7.fc13 Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
Hi, On Sat, Nov 20, 2010 at 4:52 PM, Kevin Fenzi ke...@scrye.com wrote: filed month+ ago: https://bugzilla.redhat.com/show_bug.cgi?id=643296 Simple fix of memory corruption affecting various applications incl. Firefox. Completed Policy for nonresponsive package maintainers there, got an off-list reply but still no fix commit or commit rights approval. Lennart is surely around... I wonder if the nonresponsive package maintainers policy should have a provision for ping maintainer on irc --Ray -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
On Sun, 21 Nov 2010 01:52:02 +0100, Ray Strode wrote: On Sat, Nov 20, 2010 at 4:52 PM, Kevin Fenzi ke...@scrye.com wrote: Completed Policy for nonresponsive package maintainers there, got an off-list reply but still no fix commit or commit rights approval. Lennart is surely around... I wonder if the nonresponsive package maintainers policy should have a provision for ping maintainer on irc BTW I mailed him also (off-list) and got a reply on 10 Nov 2010 so I did not try to skip any attempt. Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: pulseaudio crashes: non-responsive maintainer Lennart Poettering
Ray Strode wrote: I wonder if the nonresponsive package maintainers policy should have a provision for ping maintainer on irc Most (potentially) nonresponsive folks aren't even on IRC in the first place. (Lennart is, though. His IRC nick is mezcalero.) Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
pulseaudio crashes: non-responsive maintainer Lennart Poettering
Hello, filed month+ ago: https://bugzilla.redhat.com/show_bug.cgi?id=643296 Simple fix of memory corruption affecting various applications incl. Firefox. Completed Policy for nonresponsive package maintainers there, got an off-list reply but still no fix commit or commit rights approval. Just I am not going to takeover the package but requesting a commit right for this Bug - therefore for the package pulseaudio: https://admin.fedoraproject.org/pkgdb/acls/name/pulseaudio Thanks, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
On Mon, 15 Nov 2010 05:16:43 -0500 (EST) Jaroslav Skarvada jskar...@redhat.com wrote: Please could any FESCo member approve the takeover of rrdtool (according to nonresponsive package maintainers policy)? Or should I open ticket for this? I'll approve it and orphan rrdtool. Were you going to take the EPEL branches as well? kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
I'll approve it and orphan rrdtool. Were you going to take the EPEL branches as well? Thanks, taken all Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
I have to second someone taking over rrdtool. I handed it off to Chris a while back, but have still done far more work on it since then than he has, and I've not seen him touch an rrdtool bz in ages. :( (And no, I don't want maintainership back.) I am ready to take it (I already own it in RHEL). I think all steps in non-responsive maintainer process have been fulfilled Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer - Chris Ricker
On Nov 10, 2010, at 5:54 AM, Jaroslav Skarvada wrote: Hi, I was unsuccessful in all attempts to contact Chris Ricker (kaboom AT oobleck.net). He seems non-responsive for a long time, I did not receive any reply from him at least from February. Tracker bug: http://bugzilla.redhat.com/show_bug.cgi?id=554334 Previous attempt to contact through devel: http://lists.fedoraproject.org/pipermail/devel/2010-November/144873.html Personally I am interested in rrdtool (and I can take it), but there are also more packages with unresolved bugs I have to second someone taking over rrdtool. I handed it off to Chris a while back, but have still done far more work on it since then than he has, and I've not seen him touch an rrdtool bz in ages. :( (And no, I don't want maintainership back.) -- Jarod Wilson ja...@wilsonet.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Non-responsive maintainer - Chris Ricker
Hi, I was unsuccessful in all attempts to contact Chris Ricker (kaboom AT oobleck.net). He seems non-responsive for a long time, I did not receive any reply from him at least from February. Tracker bug: http://bugzilla.redhat.com/show_bug.cgi?id=554334 Previous attempt to contact through devel: http://lists.fedoraproject.org/pipermail/devel/2010-November/144873.html Personally I am interested in rrdtool (and I can take it), but there are also more packages with unresolved bugs Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
openjpeg non-responsive maintainer
It's been since July, https://bugzilla.redhat.com/show_bug.cgi?id=492218 ( and recently, https://bugzilla.redhat.com/show_bug.cgi?id=579548#c12 ) and previously, https://www.redhat.com/archives/fedora-devel-list/2009-September/msg01223.html where Callum suggested dropping his maintainer duties (but seemed to not have followed through). Can any FESCo member ACK this? -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: non-responsive maintainer: thomasvs (2nd attempt)
W dniu 11.09.2010 20:53, Julian Sikorski pisze: Dear all, I unfortunately have to start the non-responsive process for thomasvs again [1]. The bug to update twisted to the latest upstream version has been opened for several months now [2], and I have also prepared the updates myself on a fedorapeople repo [3].In the bug report, all responses were positive - I assume other maintainers don't care. Even debian has a newer version right now [4]. It seems that Thomas' last bugzilla activity was on 24th May, and he was not responding to my later emails either. My application for comaintainership is left untouched as well. I'm not sure if this qualifies for the fast track procedure, but the long lack of response might favour that. Thomas, if you can read this, please accept my twisted co-maintainership, and I'll be happy to reduce your burden. Regards, Julian [1] http://thread.gmane.org/gmane.linux.redhat.fedora.devel/131415 [2] https://bugzilla.redhat.com/show_bug.cgi?id=572372 [3] http://repos.fedorapeople.org/repos/belegdol/twisted/ [4] http://packages.debian.org/squeeze/python-twisted After giving it some thought, I decided to go for fast track process: https://fedorahosted.org/fesco/ticket/463 Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
non-responsive maintainer: thomasvs (2nd attempt)
Dear all, I unfortunately have to start the non-responsive process for thomasvs again [1]. The bug to update twisted to the latest upstream version has been opened for several months now [2], and I have also prepared the updates myself on a fedorapeople repo [3]. In the bug report, all responses were positive - I assume other maintainers don't care. It seems that Thomas' last bugzilla activity was on 24th May, and he was not responding to my later emails either. My application for comaintainership is left untouched as well. I'm not sure if this qualifies for the fast track procedure, but the long lack of response might favour that. Thomas, if you can read this, please accept my twisted co-maintainership, and I'll be happy to reduce your burden. Regards, Julian [1] http://thread.gmane.org/gmane.linux.redhat.fedora.devel/131415 [2] https://bugzilla.redhat.com/show_bug.cgi?id=572372 [3] http://repos.fedorapeople.org/repos/belegdol/twisted/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
non-responsive maintainer: thomasvs (2nd attempt)
Dear all, I unfortunately have to start the non-responsive process for thomasvs again [1]. The bug to update twisted to the latest upstream version has been opened for several months now [2], and I have also prepared the updates myself on a fedorapeople repo [3].In the bug report, all responses were positive - I assume other maintainers don't care. Even debian has a newer version right now [4]. It seems that Thomas' last bugzilla activity was on 24th May, and he was not responding to my later emails either. My application for comaintainership is left untouched as well. I'm not sure if this qualifies for the fast track procedure, but the long lack of response might favour that. Thomas, if you can read this, please accept my twisted co-maintainership, and I'll be happy to reduce your burden. Regards, Julian [1] http://thread.gmane.org/gmane.linux.redhat.fedora.devel/131415 [2] https://bugzilla.redhat.com/show_bug.cgi?id=572372 [3] http://repos.fedorapeople.org/repos/belegdol/twisted/ [4] http://packages.debian.org/squeeze/python-twisted -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614982] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614982 Bug 614982 depends on bug 611015, which changed state. Bug 611015 Summary: perl-Pugs-Compiler-Rule fails to build https://bugzilla.redhat.com/show_bug.cgi?id=611015 What|Old Value |New Value Status|CLOSED |ASSIGNED Resolution|RAWHIDE | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Non-responsive maintainer: Deji Akingunola
On Sun, Aug 8, 2010 at 3:39 PM, Robert Scheck rob...@fedoraproject.org wrote: Hi, as per non-responsive maintainer policy at https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I have filed: https://bugzilla.redhat.com/show_bug.cgi?id=600992 Does somebody know how to contact Deji Akingunola? I've been unsuccessful via e-mail and Red Hat Bugzilla so far. And it seems he isn't around in the IRC. While the truth is you never contacted me by email, and you went ahead threatening me with AWOL policy and orphaning all my packages just 2 weeks after filing a bug for package upgrade on EPEL 4. I will get to the bug when I have the time. And it seems he isn't around in the IRC. I don't use IRC. Deji -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer: Deji Akingunola
Am Montag, den 09.08.2010, 09:46 -0400 schrieb Deji Akingunola: While the truth is you never contacted me by email, and you went ahead threatening me with AWOL policy and orphaning all my packages just 2 weeks after filing a bug for package upgrade on EPEL 4. The truth is that the bug 600992 was opened June 6th, this is way more than 2 weeks. 2 weeks is just the normal time span from one step of the AWOL policy to the next. I will get to the bug when I have the time. Nobody says that you need to update the package within 2 weeks, but you should at least respond to the bug as you have been doing now. Writing a sentence like this one isn't that hard, is it? Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer: Deji Akingunola
Robert Scheck wrote, at 08/09/2010 04:39 AM +9:00: Hi, as per non-responsive maintainer policy at https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I have filed: https://bugzilla.redhat.com/show_bug.cgi?id=600992 Does somebody know how to contact Deji Akingunola? I've been unsuccessful via e-mail and Red Hat Bugzilla so far. And it seems he isn't around in the IRC. Greetings, Robert I surely think that deji is active: http://koji.fedoraproject.org/koji/userinfo?userID=217 Regards, Mamoru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer: Deji Akingunola
On Sun, Aug 8, 2010 at 4:12 PM, Mamoru Tasaka wrote: Robert Scheck wrote, at 08/09/2010 04:39 AM +9:00: Hi, as per non-responsive maintainer policy at https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I have filed: https://bugzilla.redhat.com/show_bug.cgi?id=600992 Does somebody know how to contact Deji Akingunola? I've been unsuccessful via e-mail and Red Hat Bugzilla so far. And it seems he isn't around in the IRC. Greetings, Robert I surely think that deji is active: http://koji.fedoraproject.org/koji/userinfo?userID=217 Regards, Mamoru True, but does the non-responsive package maintainer policy not apply to those who are active? If so, why? Being active/passive is not the same thing as being responsive/non-responsive. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer: Deji Akingunola
On Sun, Aug 08, 2010 at 09:39:44PM +0200, Robert Scheck wrote: Hi, as per non-responsive maintainer policy at https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I have filed: https://bugzilla.redhat.com/show_bug.cgi?id=600992 Imho the bug report should be as informative as the other one you filed earlier and explain why you want to get the package updated: https://bugzilla.redhat.com/show_bug.cgi?id=600925 It might even help to get a response... Also the bug blocks a closed bug, which contradicts the meaning of blocking. Regards Till pgpBa7cwO6fOc.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614982] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614982 --- Comment #4 from Steven Pritchard st...@silug.org 2010-08-01 18:54:15 EDT --- I'm still here. I've looked at the package to try to figure out why it won't build once, but I didn't get anywhere. I'll take another look ASAP. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On 07/07/10 20:16, Thomas Spura wrote: To get such a button, to apply for becoming real maintainership makes this possible and is the easiest way, because it doesn't need e.g. a fast track procedure or anyone agreeing from fesco or anyone to change it manually in pkgdb. When you have another solution for this, let me hear. :) I have an idea that people who spent the hard yards to create a package/improve it enough to get into fedora are proud of their accomplishment - for non-prolific packagers, like my self, having yourself listed as maintainer can be a bit of status symbol. Having to officially say I don't want that any more would not be easy. It would be good if the package db grew a history of (co)maintainers: Package developed: 2007-06-01 fschepsi Retired maintainers: 2009-12-06 - 2010-04-13 bcandoit 2008-07-01 - 2009-09-13 jbloggers Anymay, just wanting to put a view from a basic (10 packages) maintainer. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614980] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614980 Iain Arnell iarn...@gmail.com changed: What|Removed |Added Status|NEW |CLOSED Blocks||555496, 611014 Depends on|555496, 611014 | Resolution||NOTABUG --- Comment #2 from Iain Arnell iarn...@gmail.com 2010-07-24 02:10:36 EDT --- Congratulations! I tried adding myself to both packages, but pkgdb seems to be confused with DBI-Dumper. I'll take a look at both pkgs again to see if we can get some positive result. And I'll try to keep an eye on the rest of your pkgs too. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614980] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614980 --- Comment #1 from Chris Weyl cw...@alumni.drew.edu 2010-07-23 13:33:24 EDT --- I'm going to be (and have been) rather busy for a while -- over the next month I'm getting married, moving to Oregon, and changing my $job So my priority has been, and has to be, Real Life. Iain, I trust your judgment here. I'm not sure either of them should be retired, but neither do I have the time to sort through it all right now. Data::Alias looks like it's being actively worked (at least by the Debian people), so hopefully some good will come of that. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Thu, Jul 15, 2010 at 1:17 AM, Kevin Fenzi wrote: On Wed, 14 Jul 2010 20:42:57 -0400 Orcan Ogetbil wrote: I have got news. The other day, my ACL request (that I made last year!) for F-10 was approved by ixs. 1 minute later, it was set back to Awaiting Review. Anyone have any idea of what's going on? Not sure. Ixs was active the other day. Perhaps he approved you, then decided he didn't know who you were and unapproved you. Drop him an email to introduce yourself and ask whats going on? I sent him an email as you asked, once again. And didn't get a response, once again. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Fri, 23 Jul 2010, Orcan Ogetbil wrote: I sent him an email as you asked, once again. And didn't get a response, once again. Good morning. Sorry for the non-responsiveness. Work has been kinda taxing for some time now... Someone pointed me at the discussion here. It was indeed as mentioned. I think it was nirik, who contacted me on irc and suggested to approve mhlavink for that package. I approved mhlavink and accidentially approved someone else as well, who I then didn't recognize. Thus I reverted that. Seems that was you. That should be fixed now. About your email: You wrote that you fixed the problem with the uberpackager permissions. Thanks for that. I just assumed the problem is fixed and you were happy. Didn't know about the part with the approve permissions. cheers, andreas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 614980] New: non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: non-responsive maintainer https://bugzilla.redhat.com/show_bug.cgi?id=614980 Summary: non-responsive maintainer Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-DBI-Dumper AssignedTo: cw...@alumni.drew.edu ReportedBy: iarn...@gmail.com QAContact: extras...@fedoraproject.org CC: cw...@alumni.drew.edu, fedora-perl-devel-l...@redhat.com Classification: Fedora Chris, please respond to bug #555496 and bug #611014 perl-DBI-Dumper and perl-Data-Alias fail to build under perl 5.12. They should either be fixed or retired. According to rel-eng, perl-sig and perl maintainer can't initiate EOL for these packages[1]. I understand that ppisar has already contacted you about this[2]. There have also been automatic broken dependency mails for several weeks already. [1] https://fedorahosted.org/rel-eng/ticket/3882 [2] http://lists.fedoraproject.org/pipermail/perl-devel/2010-July/024190.html -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614982] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614982 Iain Arnell iarn...@gmail.com changed: What|Removed |Added Depends on||611015 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614982] New: non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: non-responsive maintainer https://bugzilla.redhat.com/show_bug.cgi?id=614982 Summary: non-responsive maintainer Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Pugs-Compiler-Rule AssignedTo: st...@silug.org ReportedBy: iarn...@gmail.com QAContact: extras...@fedoraproject.org CC: st...@silug.org, fedora-perl-devel-l...@redhat.com Classification: Fedora Steve, please respond to bug #611015. perl-Pugs-Compiler-Rule fails to build under perl 5.12. It should either be fixed or retired. According to rel-eng, perl-sig and perl maintainer can't initiate EOL for these packages[1]. There have also been automatic broken dependency mails for several weeks already. [1] https://fedorahosted.org/rel-eng/ticket/3882 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614981] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614981 Iain Arnell iarn...@gmail.com changed: What|Removed |Added CC||fedora-perl-devel-l...@redh ||at.com Depends on||539046 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614980] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614980 Iain Arnell iarn...@gmail.com changed: What|Removed |Added Depends on||611014, 555496 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614981] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614981 Bug 614981 depends on bug 539046, which changed state. Bug 539046 Summary: FTBFS perl-Test-AutoBuild-1.2.2-9.fc12 https://bugzilla.redhat.com/show_bug.cgi?id=539046 What|Old Value |New Value Status|ASSIGNED|CLOSED Resolution||RAWHIDE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 614981] non-responsive maintainer
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=614981 Daniel Berrange berra...@redhat.com changed: What|Removed |Added Status|NEW |CLOSED Resolution||NOTABUG --- Comment #1 from Daniel Berrange berra...@redhat.com 2010-07-15 13:26:31 EDT --- If anyone ever bothered to email me directly I would have responded. Automated emails are low priority easily missed when many thousand of them arrive every week. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Mon, Jul 5, 2010 at 7:05 PM, Orcan Ogetbil wrote: On Mon, Jul 5, 2010 at 6:17 PM, Michel Alexandre Salim wrote: Hi all, I'm initiating a fast track procedure for libsndfile -- a security bug has been reported for over a year, and there has been no response from maintainer We made many attempts to reach him last year. See: https://www.redhat.com/archives/fedora-devel-list/2009-November/msg00102.html I asked for comaintainership on Fedora branches about 10 months ago, and didn't hear back until now. My request is still open. I have got news. The other day, my ACL request (that I made last year!) for F-10 was approved by ixs. 1 minute later, it was set back to Awaiting Review. Anyone have any idea of what's going on? Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Wed, 07 Jul 2010 01:53:29 +0200, Kevin wrote: Kevin Fenzi wrote: If some provenpackager want's to maintain it, why don't they take ownership? Because I can fix the occasional broken dependency, [...] ... which hopefully will not be a problem anymore with a revised push process. You could not limit your activity to Rawhide, and you would not learn about broken deps and required rebuilds for released dists, if you're not willing to become one of the package's maintainers. [...] but I can't commit to actually maintain hundreds of packages. For example, the bugmail would flood me, I couldn't fix any of those bugs anyway, only the complete showstoppers (i.e. broken deps and MAYBE (!) FTBFS). So, you won't forward problem reports to upstream either (as by now everyone knows anyway that you'd like crash reports to flood upstream directly instead of Fedora's tracker), you won't keep an eye on upstream development (e.g. commit diffs and release monitoring), and you won't learn if your recent rebuild or upgrade causes segfaults. In other words, you request to become a package-monkey with no responsibilities, who may play with a pile of packages, which is free for everyone to either mess with or leave it aside. This might work with some software, which is rather maintenance-free and has upstream developers who make quality releases, but packages for such software often are easy to maintain and are low-hanging fruit even for RPM packging beginners. If the software is used at all by anyone within the Fedora community, it should not be a big problem to find _at least_ one packager for it. And if there are more than one, increase the freedom and encourage even additional people to become one of the package's maintainers. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Am Wed, 07 Jul 2010 01:46:44 +0200 schrieb Kevin Kofler kevin.kof...@chello.at: Thomas Spura wrote: For me it doesn't make much sense to be co-maintainer everywhere, but actually: 1. doing all the tasks alone. I don't see the big problem. I'm comaintaining a few packages in that way for a while (xchat and mingw32-nsis come to my mind) and that just works (though I do sometimes get angry about maintainers being registered there and rarely doing anything). It's simply annoying to fix *all* bugs of a particular package and always need to click e.g. on 'Take it' on the assign list. But that's not the best reason for this change... How to you see, that a maintainer is unresponsive? The bugs are getting fixed, all releases are getting updates, the program works, so there is nothing to complain about on the first sign. e.g. I *know* the package owner, I'm complaining about, doesn't even read the bugzilla mails, but he is also not 'unresponsive' with the criterias of the unresponsive maintainership rule, because he answers private mails... - I believe, he should give his packages completely away, and become co-maintainer of his former packages. This way he can still help out, when he finds time, or simply continue ignoring bugzilla mails without being bothered. To get such a button, to apply for becoming real maintainership makes this possible and is the easiest way, because it doesn't need e.g. a fast track procedure or anyone agreeing from fesco or anyone to change it manually in pkgdb. When you have another solution for this, let me hear. :) Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Tuesday, July 06, 2010 01:05:57 Orcan Ogetbil wrote: On Mon, Jul 5, 2010 at 6:17 PM, Michel Alexandre Salim wrote: Hi all, I'm initiating a fast track procedure for libsndfile -- a security bug has been reported for over a year, and there has been no response from maintainer I've added patch to that bugzilla. I have all changes ready, only commit acl required :) We made many attempts to reach him last year. See: https://www.redhat.com/archives/fedora-devel-list/2009-November/msg00102.ht ml I asked for comaintainership on Fedora branches about 10 months ago, and didn't hear back until now. My request is still open. me too but not 10 months ago If current maintainer is no longer interested in libsndfile I'm willing to become maintainer for this package. I already maintain it for rhel6 I ended up updating the Fedora packages, and hence closing the security bugs with my proven powers. I didn't touch the EPEL package since 1- I don't even know if the force is strong enough with my proven powers in the EPEL arena. 2- I am basically not much interested in EPEL. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 09:21:29AM +1000, Chris Jones wrote: This seems to be happening a lot lately regarding maintainers and/or co-maintainers losing interest in their projects somewhere along the line and just stopping development without any warning and notification to other members who may be interested. Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). That way packages with AWOL maintainers could grow co-maintainers without going through the complicated AWOL-process. -- sven === jabber/xmpp: s...@lankes.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
sorry for being offline. had some longer trouble in real life and am now wading through lots of mails which piled up since some weeks. pushed that package. what is the correct way for being unavailable? is a vacation message ok, or would we spam our mailinglists? as far as i remember vacation would leave mails from vacation-lists alone, though. josef On Mon, 2010-07-05 at 13:33 +0200, Pierre-Yves wrote: On Mon, 2010-07-05 at 12:30 +0100, Mark Chappell wrote: http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers It takes three weeks which can be frustrating, the initial can we push this update to testing might count as the initial ticket creation, dropping it down to 2 weeks from here... If we include the absence of reaction in this review: https://bugzilla.redhat.com/show_bug.cgi?id=585817 (last comment on Mai 08th) then we are over these 3 weeks. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 6, 2010 at 6:32 PM, Sven Lankes s...@lank.es wrote: Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). That way packages with AWOL maintainers could grow co-maintainers without going through the complicated AWOL-process. -- sven === jabber/xmpp: s...@lankes.net -- Sounds reasonable enough to me. Regards -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 Photo Resolutions - Photo Printing, Editing and Restorations Web: http://photoresolutions.freehostia.com Email: chrisjo...@comcen.com.au or ubuntu...@comcen.com.au Fedora Design Suite Developer and Co-Maintainer Email: foxmulder...@fedoraproject.org -- GnuPG v1.4.10 (GNU/Linux) Public Key Fingerprint: 6915 0761 5754 D091 99F4 5384 BA37 FD5D 34F9 F115 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On Tue, Jul 06, 2010 at 10:51:37AM +0200, josef radinger wrote: sorry for being offline. had some longer trouble in real life and am now wading through lots of mails which piled up since some weeks. Welcome back. what is the correct way for being unavailable? is a vacation message ok, or would we spam our mailinglists? as far as i remember vacation would leave mails from vacation-lists alone, though. If you are unavailable for a long time (e.g. longer than two weeks) it is imho best to announce it on the mailing list. Also if there are unhandled issues, it is better to ask for help here even on a shorter vacation. Also there is a wiki page to document absence: https://fedoraproject.org/wiki/Vacation Regards Till pgpzbEBQ03z1O.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 6, 2010 at 6:32 PM, Sven Lankes s...@lank.es wrote: Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). That way packages with AWOL maintainers could grow co-maintainers without going through the complicated AWOL-process. -- sven === jabber/xmpp: s...@lankes.net -- Sounds reasonable enough to me. Regards Big +1 from me too for such change. Alexander Kurtakov -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 Photo Resolutions - Photo Printing, Editing and Restorations Web: http://photoresolutions.freehostia.com Email: chrisjo...@comcen.com.au or ubuntu...@comcen.com.au Fedora Design Suite Developer and Co-Maintainer Email: foxmulder...@fedoraproject.org -- GnuPG v1.4.10 (GNU/Linux) Public Key Fingerprint: 6915 0761 5754 D091 99F4 5384 BA37 FD5D 34F9 F115 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non responsive maintainer: cheese ?
On Tue, 2010-07-06 at 10:51 +0200, josef radinger wrote: sorry for being offline. had some longer trouble in real life and am now wading through lots of mails which piled up since some weeks. Good to hear you are back :-) Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 10:32:06AM +0200, Sven Lankes wrote: On Tue, Jul 06, 2010 at 09:21:29AM +1000, Chris Jones wrote: This seems to be happening a lot lately regarding maintainers and/or co-maintainers losing interest in their projects somewhere along the line and just stopping development without any warning and notification to other members who may be interested. Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). +1, good idea. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Am Tue, 6 Jul 2010 10:57:06 +0100 schrieb Richard W.M. Jones rjo...@redhat.com: On Tue, Jul 06, 2010 at 10:32:06AM +0200, Sven Lankes wrote: On Tue, Jul 06, 2010 at 09:21:29AM +1000, Chris Jones wrote: This seems to be happening a lot lately regarding maintainers and/or co-maintainers losing interest in their projects somewhere along the line and just stopping development without any warning and notification to other members who may be interested. Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). +1, good idea. If this is implemented, the 'next' co-maintainer should become the real maintainer after another 8 weeks non-commiting by the former maintainer. For me it doesn't make much sense to be co-maintainer everywhere, but actually: 1. doing all the tasks alone. 2. when there is a problem with the package, other contact at first the maintainer, which should be the new one, too. Maybe a button with 'take the package, when maintainer doesn't want to keep it' and transfer, when the maintainer agrees or doesn't respond in the 8 weeks or so? Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 01:26:21PM +0200, Thomas Spura wrote: If this is implemented, the 'next' co-maintainer should become the real maintainer after another 8 weeks non-commiting by the former maintainer. I think this is another problem with pkgdb or Fedora. Why is there a maintainer (owner?) and co-maintainers, rather than just having all co-maintainers be equal? As people know, my default position is for inclusion: we should try to include as many packages in Fedora that we can, except where there is a legal or insuperable technical problem with that. So I think it's valid for packages to have 0, 1, 2, or more maintainers. If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 01:39:43PM +0100, Richard W.M. Jones wrote: I think this is another problem with pkgdb or Fedora. Why is there a maintainer (owner?) and co-maintainers, rather than just having all co-maintainers be equal? Because this ensures that there is a well defined person who is responsible for the package, and has the last word (with the usual procedure when people disagree with the maintainer). It doesn't prevent from having, in practice, equal maintainers when it comes to maintaining the package. This was the case for some packages I co-maintained, for example netcdf related packages, where all the co-maintainers were more or less equal in practice. -- Pat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, 6 Jul 2010 13:39:43 +0100, Richard wrote: So I think it's valid for packages to have 0, 1, 2, or more maintainers. Why 0? Who will be notified about bugzilla tickets? Who will receive mail sent to the PACKAGE-owner Fedora e-mail alias? For each package in the collection, there ought to be at least (!) one maintainer, who wants to be responsible for taking care of the package. If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. Sounds like the infamous dumping-ground for packages. Welcome back, contrib.redhat.com! Or what? Best-effort maintained ranging from no effort to over-ambitious upgrade hell. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 6, 2010 at 10:44 AM, Michael Schwendt wrote: On Tue, 6 Jul 2010 13:39:43 +0100, Richard wrote: So I think it's valid for packages to have 0, 1, 2, or more maintainers. Why 0? Who will be notified about bugzilla tickets? Who will receive mail sent to the PACKAGE-owner Fedora e-mail alias? Some mailing list like dumping-gro...@fedoraproject.org. I am sure someone can come up with a better name. For each package in the collection, there ought to be at least (!) one maintainer, who wants to be responsible for taking care of the package. Yes. And everyone who is subscribed to the above mailing list is a potential maintainer of those packages with 0 principal maintainers. Great idea. If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. Sounds like the infamous dumping-ground for packages. Welcome back, contrib.redhat.com! Or what? Best-effort maintained ranging from no effort to over-ambitious upgrade hell. +1. Exactly. Good thinking! Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 10:54:29AM -0400, Orcan Ogetbil wrote: On Tue, Jul 6, 2010 at 10:44 AM, Michael Schwendt wrote: On Tue, 6 Jul 2010 13:39:43 +0100, Richard wrote: So I think it's valid for packages to have 0, 1, 2, or more maintainers. Why 0? Who will be notified about bugzilla tickets? Who will receive mail sent to the PACKAGE-owner Fedora e-mail alias? Some mailing list like dumping-gro...@fedoraproject.org. I am sure someone can come up with a better name. We can use uberpackagers ;-) or maybe package-monkeys, make it a SIG and then it is afaik already covered by Fedora procedures, because a SIG or group of packagers can own a package, like e.g. the lvm-team. Orcan, Richard, who else is in? Regards Till pgp7BIxx7K7hK.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 12:31:32PM +0300, Alexander Kurtakov wrote: On Tue, Jul 6, 2010 at 6:32 PM, Sven Lankes s...@lank.es wrote: Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). That way packages with AWOL maintainers could grow co-maintainers without going through the complicated AWOL-process. -- sven === jabber/xmpp: s...@lankes.net -- Sounds reasonable enough to me. Regards Big +1 from me too for such change. If anyone wants to help code this, I think the way to do it is to implement an events queue in pkgdb. With the queue we can do two things -- first, have the pkgdb send nagmail when an acl request has not been answered. second have the pkgdb batch status messages when many requests are done at the same time. -Toshio pgpy8jGYp56mM.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, Jul 06, 2010 at 12:00:23PM -0400, Toshio Kuratomi wrote: If anyone wants to help code this, I think the way to do it is to implement an events queue in pkgdb. With the queue we can do two things -- first, have the pkgdb send nagmail when an acl request has not been answered. second have the pkgdb batch status messages when many requests are done at the same time. I guess for the nagmail a separate cron job that queries the db for old requests and send sends the mail might be enough and probably be straight forward to implement as long as there is a timestamp saved when a ACL request is made. Regards Till pgpFpOU8CES4w.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive maintainer fast track procedure for libsndfile
On Tue, 6 Jul 2010 09:21:29 +1000 Chris Jones chrisjo...@comcen.com.au wrote: This seems to be happening a lot lately regarding maintainers and/or co-maintainers losing interest in their projects somewhere along the line and just stopping development without any warning and notification to other members who may be interested. Yeah, the current process is not ideal, as it not only requires some maintainer to notice that they are gone, but be interested enough to start a process and follow through on it. I am wondering, is the process efficient enough for other willing developers to take over development of unplanned orphaned and unmaintained code from unresponsive developers/maintainers and co-maintainers? I think it could be better, and there are some good ideas later in this thread. ;) kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Tue, 6 Jul 2010 13:39:43 +0100 Richard W.M. Jones rjo...@redhat.com wrote: On Tue, Jul 06, 2010 at 01:26:21PM +0200, Thomas Spura wrote: If this is implemented, the 'next' co-maintainer should become the real maintainer after another 8 weeks non-commiting by the former maintainer. I think this is another problem with pkgdb or Fedora. Why is there a maintainer (owner?) and co-maintainers, rather than just having all co-maintainers be equal? If co-maintainers have all the same checkboxes as 'owner' then the only difference is that the 'owner' will show up in some queries as the primary contact for the package. Otherwise there's no difference. The co-maintainers can approve other people for acls, etc. As people know, my default position is for inclusion: we should try to include as many packages in Fedora that we can, except where there is a legal or insuperable technical problem with that. So I think it's valid for packages to have 0, 1, 2, or more maintainers. I disagree with the 0. If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. If some provenpackager want's to maintain it, why don't they take ownership? kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Sven Lankes wrote: Maybe we could tweak the pkgdb in a way that a co-maintainer request would automatically be granted if it isn't answered within a long enough timeframe (say 8 weeks). That way packages with AWOL maintainers could grow co-maintainers without going through the complicated AWOL-process. +1, good idea! And IMHO 8 weeks is too much, it should be somewhere between 2 and 4. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Thomas Spura wrote: For me it doesn't make much sense to be co-maintainer everywhere, but actually: 1. doing all the tasks alone. I don't see the big problem. I'm comaintaining a few packages in that way for a while (xchat and mingw32-nsis come to my mind) and that just works (though I do sometimes get angry about maintainers being registered there and rarely doing anything). (BTW, it's quite funny that the main GTK+-based IRC client is maintained almost exclusively by a KDE SIG member. ;-) ) 2. when there is a problem with the package, other contact at first the maintainer, which should be the new one, too. They should contact pkgname-ow...@fedoraproject.org, which also includes comaintainers. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Till Maas wrote: We can use uberpackagers ;-) or maybe package-monkeys, make it a SIG and then it is afaik already covered by Fedora procedures, because a SIG or group of packagers can own a package, like e.g. the lvm-team. Orcan, Richard, who else is in? As an inclusionist and someone who has often stepped in to fix broken dependencies in, uhm, very passively maintained packages, count me in! I think it's in almost all cases better to have a package than not to have it, even if it's not well maintained. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Kevin Fenzi wrote: On Tue, 6 Jul 2010 13:39:43 +0100 Richard W.M. Jones rjo...@redhat.com wrote: If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. If some provenpackager want's to maintain it, why don't they take ownership? Because I can fix the occasional broken dependency, but I can't commit to actually maintain hundreds of packages. For example, the bugmail would flood me, I couldn't fix any of those bugs anyway, only the complete showstoppers (i.e. broken deps and MAYBE (!) FTBFS). Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
On Wed, Jul 7, 2010 at 9:43 AM, Kevin Kofler kevin.kof...@chello.at wrote: And IMHO 8 weeks is too much, it should be somewhere between 2 and 4. Kevin Kofler I initially thought 8 weeks was too long also, but I guess people have busy lifestyles. 4 weeks is probably more realistic. If you can't access your email and reply within 4 weeks then there's definitely something going on there. worried Regards -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 Photo Resolutions - Photo Printing, Editing and Restorations Web: http://photoresolutions.freehostia.com Email: chrisjo...@comcen.com.au or ubuntu...@comcen.com.au Fedora Design Suite Developer and Co-Maintainer Email: foxmulder...@fedoraproject.org -- GnuPG v1.4.10 (GNU/Linux) Public Key Fingerprint: 6915 0761 5754 D091 99F4 5384 BA37 FD5D 34F9 F115 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Make pkgdb grant co-maintainer status automatically? (was Re: Non-responsive maintainer fast track procedure for libsndfile)
Richard W.M. Jones wrote: I think this is another problem with pkgdb or Fedora. Why is there a maintainer (owner?) and co-maintainers, rather than just having all co-maintainers be equal? Good point. I think, just like you, that there should be a list of owners rather than just 1 owner. As people know, my default position is for inclusion: we should try to include as many packages in Fedora that we can, except where there is a legal or insuperable technical problem with that. So I think it's valid for packages to have 0, 1, 2, or more maintainers. If #maintainers == 0 then the package is either just sitting there (as long as there are no serious bugs), or is being best-effort maintained by provenpackagers, at least until that becomes a burden and only then should the package be dropped. This is really a separate issue, but FWIW, I agree with you on this point as well. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
