Hi,
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
I asked for an updated in june, the 1st, for the 3.5.11 version, released on 2007-04-11 :-( https://bugzilla.redhat.com/show_bug.cgi?id=242112 http://lftp.yar.ru/events.html
There is now a 3.5.14 release since 2 weeks. All these releases fix bugs.
Regards, An angry lftp user
Alain PORTAL wrote:
Hi,
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
I asked for an updated in june, the 1st, for the 3.5.11 version, released on 2007-04-11 :-( https://bugzilla.redhat.com/show_bug.cgi?id=242112 http://lftp.yar.ru/events.html
There is now a 3.5.14 release since 2 weeks. All these releases fix bugs.
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
Rahul
Le vendredi 14 septembre 2007, Rahul Sundaram a écrit :
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
Thanks for the pointer!
Do I have to follow the full policy or can I short some steps? I opened the bug https://bugzilla.redhat.com/show_bug.cgi?id=242112 on 2007-06-01 for a 3.5.11 release, updated that bug on 2007-08-19 for a 3.5.12 release without any answer from maintainer who commited an updated spec file to answer to the mass rebuild request.
Unfortunately, I'm not sure to be able to maintain this package (I didn't try), but if nobody take it, I'll try.
Regards, Alain
Alain PORTAL wrote:
Le vendredi 14 septembre 2007, Rahul Sundaram a écrit :
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
Thanks for the pointer!
Do I have to follow the full policy or can I short some steps? I opened the bug https://bugzilla.redhat.com/show_bug.cgi?id=242112 on 2007-06-01 for a 3.5.11 release, updated that bug on 2007-08-19 for a 3.5.12 release without any answer from maintainer who commited an updated spec file to answer to the mass rebuild request.
Unfortunately, I'm not sure to be able to maintain this package (I didn't try), but if nobody take it, I'll try.
Please,
Adopt it, as anyone should know, if a package is written in C and a bug can be reproduced by someone other then the reporter, I'm always willing to help out and fix it.
I wonder if we need to have a wiki entry for package maintainers which says: "I have a bug I cannot fix even though I'm an excellent packager as I'm unfortunately not a programming guru"
With as answers: 1) Ask for help on fedora-devel-list 2) If the app is written in C ask Hans.
And I'm _not_ joking, various packagers already know to find me, and I don't mind if others find out about this too. Ofcourse there will be a point when we need a Hans version 2 / a backup Hans, volunteers?
Regards,
Hans
Alain PORTAL wrote:
Le vendredi 14 septembre 2007, Rahul Sundaram a écrit :
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
Thanks for the pointer!
Do I have to follow the full policy or can I short some steps? I opened the bug https://bugzilla.redhat.com/show_bug.cgi?id=242112 on 2007-06-01 for a 3.5.11 release, updated that bug on 2007-08-19 for a 3.5.12 release without any answer from maintainer who commited an updated spec file to answer to the mass rebuild request.
Unfortunately, I'm not sure to be able to maintain this package (I didn't try), but if nobody take it, I'll try.
Please,
Adopt it, as anyone should know, if a package is written in C and a bug can be reproduced by someone other then the reporter, I'm always willing to help out and fix it.
I wonder if we need to have a wiki entry for package maintainers which says: "I have a bug I cannot fix even though I'm an excellent packager as I'm unfortunately not a programming guru"
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
And I'm _not_ joking, various packagers already know to find me, and I don't mind if others find out about this too. Ofcourse there will be a point when we need a Hans version 2 / a backup Hans, volunteers?
No, but I could be the PHP Hans. For C, I'm jsut a Hans user. :)
Regards,
Hans
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
On 9/14/07, Hans de Goede j.w.r.degoede@hhs.nl wrote:
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
I think a broken code response group is a good idea.
Generalize it a bit so we can gather a group of people who have skillz in a number of different programming subareas.. not just C.
-jef"Such a group would need a kickass acronym and t-shirts"spaleta
On 9/14/07, Hans de Goede j.w.r.degoede@hhs.nl wrote:
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
I think a broken code response group is a good idea.
Generalize it a bit so we can gather a group of people who have skillz in a number of different programming subareas.. not just C.
Fedora Repeatably Irregular Code Killers?
I like the t-shirts idea. Then, if someone has a problem, they just look around, and find someone wearing. . .never mind.
-jef"Such a group would need a kickass acronym and t-shirts"spaleta
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Jeff Spaleta wrote:
On 9/14/07, Hans de Goede j.w.r.degoede@hhs.nl wrote:
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
I think a broken code response group is a good idea.
Generalize it a bit so we can gather a group of people who have skillz in a number of different programming subareas.. not just C.
-jef"Such a group would need a kickass acronym and t-shirts"spaleta
I've also helped out a C/C++ related stuff on a few occasions. So there is a Bug Squad reponse team :-)
Denis Leroy wrote:
Jeff Spaleta wrote:
On 9/14/07, Hans de Goede j.w.r.degoede@hhs.nl wrote:
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
I think a broken code response group is a good idea.
Generalize it a bit so we can gather a group of people who have skillz in a number of different programming subareas.. not just C.
-jef"Such a group would need a kickass acronym and t-shirts"spaleta
I've also helped out a C/C++ related stuff on a few occasions. So there is a Bug Squad reponse team :-)
Okay, so we have 2 c / c++ people for routing help request too (my C is better then my C++ though), what about other languages?
I think that just using the list for help requests probably is best, last time there was an issue I was planning on fixing it and Dennis beat me to it (before I even started looking) so just sending things to the list seems to work well, otherwise we will need some complicated dispatch mechanism for help requests to reach the proper persons.
I think that we just need to stimulate sending out help requests more. Every now and then I go on a bug hunt in bugzilla and find many bugs which are usually fixable within the hour for someone with the necessary skills and willing to do the job.
If this encouraging of asking for help leads to too much noise on this list then we can start a fedora-devel-help list where people prepared to help others like me and Dennis can subscribe too.
Regards,
Hans
On Fri, 14 Sep 2007 19:41:26 +0200 Hans de Goede j.w.r.degoede@hhs.nl wrote:
Okay, so we have 2 c / c++ people for routing help request too (my C is better then my C++ though), what about other languages?
We definitely need a Python Squad. I can't offer a whole lot to it, but I'd love to watch the traffic and learn a thing or to along the way.
On Fri, 2007-09-14 at 13:55 -0400, Jesse Keating wrote:
On Fri, 14 Sep 2007 19:41:26 +0200 Hans de Goede j.w.r.degoede@hhs.nl wrote:
Okay, so we have 2 c / c++ people for routing help request too (my C is better then my C++ though), what about other languages?
We definitely need a Python Squad. I can't offer a whole lot to it, but I'd love to watch the traffic and learn a thing or to along the way.
+1 that. I can help a little with C stuff, but probably not at the level of someone like Hans or other full-time developers, at least not if you want it fast. :-)
Paul W. Frields wrote:
On Fri, 2007-09-14 at 13:55 -0400, Jesse Keating wrote:
On Fri, 14 Sep 2007 19:41:26 +0200 Hans de Goede j.w.r.degoede@hhs.nl wrote:
Okay, so we have 2 c / c++ people for routing help request too (my C is better then my C++ though), what about other languages?
We definitely need a Python Squad. I can't offer a whole lot to it, but I'd love to watch the traffic and learn a thing or to along the way.
+1 that. I can help a little with C stuff, but probably not at the level of someone like Hans or other full-time developers, at least not if you want it fast. :-)
Hey, I'm _not_ a fulltime developer.
Regards,
Hans
On Fri, 2007-09-14 at 13:55 -0400, Jesse Keating wrote:
On Fri, 14 Sep 2007 19:41:26 +0200 Hans de Goede j.w.r.degoede@hhs.nl wrote:
Okay, so we have 2 c / c++ people for routing help request too (my C is better then my C++ though), what about other languages?
We definitely need a Python Squad. I can't offer a whole lot to it, but I'd love to watch the traffic and learn a thing or to along the way.
Count me in on C/C++, python, php and perl, I guess. If there's going to be a list, that is. And java, if anyone needs help. --
Richi Plana
Dnia 2007-09-14, o godz. 23:50:01 Richi Plana myfedora@richip.dhs.org napisał(a):
Count me in on C/C++, python, php and perl, I guess. If there's going to be a list, that is.
Yeah, please create a list and when you do so, don't forget to post to f-d-announce, so I don't miss it here, thanks :)
Lam
Le vendredi 14 septembre 2007 à 19:41 +0200, Hans de Goede a écrit :
I think that just using the list for help requests probably is best, last time there was an issue I was planning on fixing it and Dennis beat me to it (before I even started looking) so just sending things to the list seems to work well, otherwise we will need some complicated dispatch mechanism for help requests to reach the proper persons.
IMHO fedora-devel traffic is big enough without this, but there's no need for a complicated dispatch mechanism : just create a fedora-coderescue-list with no language differentiation, and have would-be helpers subscribe to it.
Le vendredi 14 septembre 2007 à 19:41 +0200, Hans de Goede a écrit :
I think that just using the list for help requests probably is best, last time there was an issue I was planning on fixing it and Dennis beat me to it (before I even started looking) so just sending things to the list seems to work well, otherwise we will need some complicated dispatch mechanism for help requests to reach the proper persons.
IMHO fedora-devel traffic is big enough without this, but there's no need for a complicated dispatch mechanism : just create a fedora-coderescue-list with no language differentiation, and have would-be helpers subscribe to it.
+1
-- Nicolas Mailhot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
On 9/14/07, Jon Ciesla limb@jcomserv.net wrote:
+1
Is there a potential bugzilla enhancement idea here as well? Like a settable flag that the bug owner can use to send the bat signal up into the air for the code squad to see?
-jef
On 9/14/07, Jon Ciesla limb@jcomserv.net wrote:
+1
Is there a potential bugzilla enhancement idea here as well? Like a settable flag that the bug owner can use to send the bat signal up into the air for the code squad to see?
+1
Can we have cars, like a certain other Squad? Maybe something a bit cooler though, like a Prius, or the Tumbler(?) from Batman Begins.
Or maybe just open the bugzilla report in a new tab, instead of via a crosstown chase leaving a wake of devastation. Yeah, that makes more sense.
-jef
On Fri, 2007-09-14 at 10:06 -0800, Jeff Spaleta wrote:
On 9/14/07, Jon Ciesla limb@jcomserv.net wrote:
+1
Is there a potential bugzilla enhancement idea here as well? Like a settable flag that the bug owner can use to send the bat signal up into the air for the code squad to see?
Good idea. Maybe just change Bugzilla status to "NEEDSHELP" and bugzilla can send an email with the proper link back to the bugzilla page to the proper mailing list. --
Richi Plana
"Jeff Spaleta" jspaleta@gmail.com writes:
On 9/14/07, Jon Ciesla limb@jcomserv.net wrote:
+1
Is there a potential bugzilla enhancement idea here as well? Like a settable flag that the bug owner can use to send the bat signal up into the air for the code squad to see?
Very nice ideas.
Le vendredi 14 septembre 2007, Hans de Goede a écrit :
Alain PORTAL wrote:
Le vendredi 14 septembre 2007, Rahul Sundaram a écrit :
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
Thanks for the pointer!
Do I have to follow the full policy or can I short some steps? I opened the bug https://bugzilla.redhat.com/show_bug.cgi?id=242112 on 2007-06-01 for a 3.5.11 release, updated that bug on 2007-08-19 for a 3.5.12 release without any answer from maintainer who commited an updated spec file to answer to the mass rebuild request.
Unfortunately, I'm not sure to be able to maintain this package (I didn't try), but if nobody take it, I'll try.
Please,
Adopt it, as anyone should know, if a package is written in C and a bug can be reproduced by someone other then the reporter, I'm always willing to help out and fix it.
I wonder if we need to have a wiki entry for package maintainers which says: "I have a bug I cannot fix even though I'm an excellent packager as I'm unfortunately not a programming guru"
With as answers:
- Ask for help on fedora-devel-list
- If the app is written in C ask Hans.
And I'm _not_ joking, various packagers already know to find me, and I don't mind if others find out about this too. Ofcourse there will be a point when we need a Hans version 2 / a backup Hans, volunteers?
OK, if noboby ask for maintaining this package during the next 72h, I'll take it.
Regards, Alain
On Fri, 2007-09-14 at 19:49 +0200, Alain PORTAL wrote:
OK, if noboby ask for maintaining this package during the next 72h, I'll take it.
FWIW, 72 hours on a Friday afternoon is somewhat short as far as time is concerned. I've done a side channel ping to try to get the maintainer's attention
Jeremy
Le vendredi 14 septembre 2007, Jeremy Katz a écrit :
On Fri, 2007-09-14 at 19:49 +0200, Alain PORTAL wrote:
OK, if noboby ask for maintaining this package during the next 72h, I'll take it.
FWIW, 72 hours on a Friday afternoon is somewhat short as far as time is concerned. I've done a side channel ping to try to get the maintainer's attention
I said 72H because I didn't want to try to package in the weekend ;-) I agree to wait some days more if you're able to find someboby to take it, but you have to know that I need a FC-6 branch, a branch that I'll request if I take it because I'm still on this release on two boxes.
Regards, Alain
On Fri, Sep 14, 2007 at 02:37:42PM -0400, Jeremy Katz wrote:
OK, if noboby ask for maintaining this package during the next 72h, I'll take it.
FWIW, 72 hours on a Friday afternoon is somewhat short as far as time is
Yeah, seriously. And here's the changes we're talking about, from the web site:
2007-08-31: lftp-3.5.14 released. A bug fixed. 2007-08-23: lftp-3.5.13 released. Some bugs fixed. 2007-07-26: lftp-3.5.12 released. Minor improvements. 2007-04-11: lftp-3.5.11 released. Some minor bugs fixed.
None of that really looks earth-shattering -- and with sometimes only a few weeks between updates, seems like waiting for an important release is a reasonably maintenance strategy.
On 14/09/2007, Matthew Miller mattdm@mattdm.org wrote:
On Fri, Sep 14, 2007 at 02:37:42PM -0400, Jeremy Katz wrote:
OK, if noboby ask for maintaining this package during the next 72h,
I'll take
it.
FWIW, 72 hours on a Friday afternoon is somewhat short as far as time is
Yeah, seriously. And here's the changes we're talking about, from the web site:
2007-08-31: lftp-3.5.14 released. A bug fixed. 2007-08-23: lftp-3.5.13 released. Some bugs fixed. 2007-07-26: lftp-3.5.12 released. Minor improvements. 2007-04-11: lftp-3.5.11 released. Some minor bugs fixed.
None of that really looks earth-shattering -- and with sometimes only a few weeks between updates, seems like waiting for an important release is a reasonably maintenance strategy.
I agree but bugs are bugs and this hasn't been updated for Fedora 7 or following the update request. Not great. Plus the maintainer's email address is waving a red flag in my head somewhere - I think someone was chasing another of his packages for an update on IRC recently...
Chris
Rahul Sundaram wrote:
Follow the AWOL policy
http://fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers
I updated the page to change a few more references to the maintainers list to this list. I also changed references to owners.list to the CVSAdminprocedure. The latter change may well already be outdated as well, now that the PackageDB is open. Anyone that knows the current procedures well may want to double check that the page is accurate.
On Fri, 2007-09-14 at 18:29 +0200, Alain PORTAL wrote:
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
How are packages orphaned? And where does one go to adopt orphan packages? I'd love to get my hands dirty by maintaining a package. Might be better than adding a new package (though I'd love to include add gnome-hearts for which I already have a package of 0.2 for). --
Richi Plana
Richi Plana wrote:
On Fri, 2007-09-14 at 18:29 +0200, Alain PORTAL wrote:
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
How are packages orphaned?
Package maintainers themselves announce that they are orphaning a package and use the package database to abandon it or a package becomes orphaned after someone else uses the AWOL policy.
And where does one go to adopt orphan
packages?
http://fedoraproject.org/wiki/PackageMaintainers/OrphanedPackages
Rahul
So let's say I wanted to grab some experiencing managing a package on Fedora and I wanted to start with an orphaned package (say brightside, though its upstream appears dead), what do I do first? How do I get an account for Fedora PackageDB?
On Fri, 2007-09-14 at 22:08 +0530, Rahul Sundaram wrote:
Richi Plana wrote:
On Fri, 2007-09-14 at 18:29 +0200, Alain PORTAL wrote:
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
How are packages orphaned?
Package maintainers themselves announce that they are orphaning a package and use the package database to abandon it or a package becomes orphaned after someone else uses the AWOL policy.
And where does one go to adopt orphan
packages?
http://fedoraproject.org/wiki/PackageMaintainers/OrphanedPackages
Rahul
On 9/14/07, Richi Plana myfedora@richip.dhs.org wrote:
So let's say I wanted to grab some experiencing managing a package on Fedora and I wanted to start with an orphaned package (say brightside, though its upstream appears dead), what do I do first? How do I get an account for Fedora PackageDB?
Read: http://fedoraproject.org/wiki/PackageMaintainers/Join Read: http://fedoraproject.org/wiki/PackageMaintainers/HowToGetSponsored
As linked from: http://fedoraproject.org/wiki/PackageMaintainers
As linked from: http://fedoraproject.org/wiki/
Or as link from: http://fedoraproject.org/wiki/Join
-jef
On Fri, Sep 14, 2007 at 06:29:06PM +0200, Alain PORTAL wrote:
Hi,
I ask for orphaning lftp because package maintainer doesn't maintain this package since a long time.
I asked for an updated in june, the 1st, for the 3.5.11 version, released on 2007-04-11 :-( https://bugzilla.redhat.com/show_bug.cgi?id=242112 http://lftp.yar.ru/events.html
There is also
https://bugzilla.redhat.com/show_bug.cgi?id=203574
and the merge review isn't ini better shape.
I could maintain lftp. Hans already takes care of my bugs ;-).
-- Pat
On Fri, 14 Sep 2007 21:51:35 +0200 Patrice Dumas pertusus@free.fr wrote:
I contacted the maintainer, as per the AWOL procedure. We'll see.
Has there been progress on this? We'd like to see the package orphaned so that somebody could pick it up.
On Fri, Nov 30, 2007 at 11:22:35AM -0500, Jesse Keating wrote:
On Fri, 14 Sep 2007 21:51:35 +0200 Patrice Dumas pertusus@free.fr wrote:
I contacted the maintainer, as per the AWOL procedure. We'll see.
Has there been progress on this? We'd like to see the package orphaned so that somebody could pick it up.
The maintainer finally responded and did the most urgent stuff. So he isn't AWOL. If I recall well, however there is another maintainer now.
-- Pat
On 30 nov 2007, at 20:33, Patrice Dumas wrote:
On Fri, Nov 30, 2007 at 11:22:35AM -0500, Jesse Keating wrote:
On Fri, 14 Sep 2007 21:51:35 +0200 Patrice Dumas pertusus@free.fr wrote:
I contacted the maintainer, as per the AWOL procedure. We'll see.
Has there been progress on this? We'd like to see the package orphaned so that somebody could pick it up.
The maintainer finally responded and did the most urgent stuff. So he isn't AWOL. If I recall well, however there is another maintainer now.
-- Pat
See https://bugzilla.redhat.com/225984
Ruben
devel@lists.stg.fedoraproject.org
-
Alain PORTAL -
Christopher Brown -
Denis Leroy -
Frank Schmitt -
Hans de Goede -
Jef Spaleta -
Jeremy Katz -
Jesse Keating -
Jon Ciesla -
Leszek Matok -
Matthew Miller -
Nicolas Mailhot -
Patrice Dumas -
Paul W. Frields -
Rahul Sundaram -
Richi Plana -
Ruben Kerkhof -
Todd Zullinger