#2242 Nonresponsive maintainer: Benjamin Pereto bpereto
Closed: Accepted 7 months ago by ignatenkobrain. Opened 7 months ago by heffer.

fas username: @bpereto
package: borgmatic
issues to fix: https://bugzilla.redhat.com/buglist.cgi?component=borgmatic&product=Fedora
nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=1755559
fedora-devel mail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CTSIVZ3NSIMLHJWMJ7MYBJTB77C2YZYV/
comainainers: none
additional notes: Email to @fedoraproject.org address bounced, possibly due to SPF fail. Sent an email to his email @sandchaschte.ch on August 10, 2019 and have received no reply.

I am a Fedora packager and actively using borgmatic and maintain a working version here: https://copr.fedorainfracloud.org/coprs/heffer/borgmatic/

I would like to take over maintaining this package.

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

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

7 months ago

If at least one FESCo member votes +1 and no one votes differently, the ticket is approved after three days.


If approved, and the reporter is a current Fedora packager in good standing, interested in comaintaining the package, FESCo will default to adding the reporter as the package admin.

I've added heffer as an admin to borgmatic.

Keeping this open, so we can remind @bpereto in 4 days.

@bpereto is the main admin of borgbackup and borgmatic.

@fschwarz seem to be the active maintainer of borgbackup. In case we'd orphan all @bpereto's packages, I suspect the following is the best course of action:

  • make @heffer the main admin of borgmatic
  • make @fschwarz the main admin of borgbackup

Felixes, how does that sound?

  • make @heffer the main admin of borgmatic
  • make @fschwarz the main admin of borgbackup

Felixes, how does that sound?

This Felix thinks that sounds splendid!

Metadata Update from @churchyard:
- Issue assigned to churchyard

7 months ago

Great, +1 from me.

Felix: are you interested in co-maintaining borgbackup? Right now I think I can handle borgbackup well enough (as I dug into both for my F30 unbundling) but my availability may change so having a co-maintainer would be nice.

(I'm on vacation with spotty connectivity - answers might take a bit longer than usual)

@bpereto This is the FESCo bump after a week. Are you still interested in maintaining your packages?

With no further reply for the original owner, FESCo closes its ticket and the bugzilla ticket.

Tagged with pending announcement, closed the buzgilla.

If maintainership was requested in 4., the reporter will be assigned as the main maintainer of the package...

Gave borgmatic to @heffer.

All other packages are orphaned too, and may be picked up by co-maintainers or other packagers.

Gave borgbackup to @fschwarz. There are no other packages of @bpereto.

Once the final reassignment happens, the new owner must also reassign all open bugs for this package to themselves.

I've reassigned 1 remaining borgmatic bugzilla to @heffer, the other one was already done; borgbackup has no open bugzillas.


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

7 months ago

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

7 months ago

Login to comment on this ticket.