fas username: @duriantang package: bumpversion issues to fix: https://src.fedoraproject.org/rpms/bumpversion/pull-request/3 nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=2115356 fedora-devel mail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VAZT5UBSTJTV77QGXOYFEGPBCAAW4XKT/ comainainers: @jdornak I am interested in comaintaining the package: yes additional notes: I am not a packager yet, although have submitted a bunch of PR to packages that were as well merged (https://src.fedoraproject.org/dashboard/activity). I would be interested to become one (have also a new package waiting for a sponsor (https://bugzilla.redhat.com/show_bug.cgi?id=2087143) and a bunch of others I'd like to propose (some specs here: https://github.com/fedepell/rpms-specs)) and maybe take over also some of the dormant/orphaned ones.
This is a ticket for the Fedora's Policy for nonresponsive package maintainers.
+1 for the nonresponsive maintainer thing.
For sponsors, please read https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#how_to_find_a_sponsor
Metadata Update from @churchyard: - Issue tagged with: nonresponsive maintainer
duriantang is main admin of rpms/bumpversion co-maintained by @jdornak duriantang has a bugzilla override on rpms/bumpversion
I'd like to add a side note to this request. I was looking into the list of tickets filed by the new find-inactive-packagers policy and I was surprised this user wasn't listed. So I did some investigation and I found that user duriantang is not even in the packager group anymore! I suppose either they removed themselves from the group or they were removed, but they still maintained their status of primary admin of bumpversion.
I think we need to get in place some check to prevent this situation to happen.
@duriantang Are you still interested in maintaining Fedora packages?
@duriantang maintains nothing. Closing.
Metadata Update from @churchyard: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open) - Issue tagged with: pending announcement
Log in to comment on this ticket.