#2307 Nonresponsive maintainer: Chris Grau (cgrau)
Closed: Accepted 2 years ago by decathorpe. Opened 2 years ago by ferdnyc.

fas username: @cgrau
package: frotz
issues to fix: https://bugzilla.redhat.com/show_bug.cgi?id=1510108 "update 2.44" (originally opened by @mastaiza on 2017-11-06, autoclosed by F29 EOL)
nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=1779063
fedora-devel mail: https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/thread/Z52MDJ7NOF3KFSSWLQST3VEG25BRI6FD/ (sent 2019-12-29)
comainainers: none
additional notes:

Other packages maintained by @cgrau:

  • ifm
  • perl-Time-Piece (orphaned)
  • perl-Time-Piece-MySQL

As I noted in the fedora-devel email, my primary interest is in frotz, as the version currently packaged for F31 / rawhide is 2.43, which was released in October 2002. Version 2.44 was released in 2015 (that's what the autoclosed bug was for), and now version 2.50 is out last month. I already have a working frotz-2.50 RPM built locally, based on the spec in Pagure.

I'd like to take over frotz so I can push out an update , if there are no objections. I'd be willing to pick up ifm as well, at least long enough to determine whether it's still useful for anything. I have absolutely no interest in maintaining the Perl modules.

My FAS username: ferdnyc

This is a ticket for the Fedora's Policy for nonresponsive package maintainers.

Not sure why @-tagging @cgrau doesn't work.

Nothing comes up in the typeahead list for that username here, but https://admin.fedoraproject.org/accounts/user/view/cgrau shows an accout. ¯\_(ツ)_/¯

Not sure why @-tagging @cgrau doesn't work.

No account on this pagure instance.

Metadata Update from @churchyard:
- Issue tagged with: nonresponsive maintainer

2 years ago

Was there an e-mail to them? Other than bugzilla automatic email that is?

Sorry for the delay in responding.

Was there an e-mail to them? Other than bugzilla automatic email that is?

Other than that (and multiple bugzilla emails over the past 2 years from the 1510108 ticket), I guess there wasn't, no. I was hoping the @-tag here would generate an additional notification, but obviously that didn't happen.

I suppose I can send one now, though I feel a bit weird emailing a perfect stranger out of the blue, right from my personal GMail account. It's like, "Who the heck is this?"

Not sure why @-tagging @cgrau doesn't work.

No account on this pagure instance.

Huh. I didn't realize they could be separate, thanks.

Anyway, I'll figure out what I'm going to say and send that email now.

The idea is that the e-mail to devel is CC'ed to the maintainer. In case their bugzilla e-mail is filtered, they need to know this is happening anyway.

@churchyard No, no, understood... it's just unfortunate that HyperKitty doesn't offer a way to do that. I generally avoid posting to mailing lists from webmail, because it's not often well-received.

Anyway, I just sent a new mail to the devel list, and CC'd Chris's registered email address. As expected the formatting is awful, but oh well.


(I'll update the initial request as well.)

Should I close this and open a new request when a week has passed, or can we just put this on hold until then?

we just put this on hold until then

ok. a week has passed.


And another, nearly. Anything else I need to do on this?

@ferdnyc No, sorry. After 3+ days with at least one FESCo member approval, you become an additional admin of frotz and ifm (drop yourself there if you don't like that). Doing it now.

@ferdnyc Done. Sorry for the delay, it is not processed automatically.

@cgrau Do you still want to maintain your packages in Fedora? (Also sent via e-mail, since there will be no notification here.)

Made @ferdnyc main admin of frotz and ifm.

Orphaned perl-Time-Piece-MySQL.

Metadata Update from @churchyard:
- Issue tagged with: pending announcement

2 years ago

👍 frotz-2.50-1.fc30 is currently in the testing→stable queue, in fact. (frotz-2.50-1.fc31 has another day to go, due to a delay getting into testing.)

Still figuring out what to do about ifm. There is a new version — but even that's from 2009. Unclear whether it's actually useful for anything. But I'll figure something out.

Metadata Update from @decathorpe:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.