#1931 Nonresponsive maintainer: thomasvs (python-twisted)
Closed: Fixed 5 years ago Opened 5 years ago by churchyard.

@thomasvs is not responsive.

Bugzilla: #1589079
E-mail: Nonresponsive maintainer: thomasvs
Package: python-twisted

Last commit from @thomasvs (in python-twisted) is from 2008-05-21.

I'd like to get the package to @python-sig and @eclipseo who seem to care: https://src.fedoraproject.org/rpms/python-twisted/pull-request/4

There are also comaintainers: @jsteffan @thias @tomprince - none of them ever replied to a bug or a Pagure PR.


+1 to orphaning / reassigning.

+1 to orphaning / reassigning.

+1 to orphaning / reassigning.

@thias has responded to the bug:

I know for a fact that Thomas hasn't been using Twisted for a long time now.
Also, if changes are made to the ownership, feel free to remove me as
co-maintainer, as I'm nearly as unresponsive as Thomas (sorry!).

+1 to orphan/reassign.

I removed @thias as requested, As far as I understand the original comment, the co-maintainers are also unresponsive. Are you voting to remove them from the package, too?

+1 to remove all non-responsive maintainers and just add @eclipseo

Note that as long as @eclipseo is main admin and python-sig is admin, I don't care if there are dead comaintainers as well or not.

Also note that @eclipseo haven't agreed to this yet... (feel free to make it just the sig if he doesn't).

I don't use it but I can take care of it for now. My interest was to update kajongg which needs a recent python-twisted.

Thank you! Let's make @eclipseo the main admin, me and python-sig admins?

Can we do this soonish? I'd like to have this solved before the F29 mass rebuild.

(I will help you ship it as a provenpackager, see my comment in the PR.)

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

6. If at least one FESCo member approves the takeover, and no one objects within 3 days, the reporter may take over the package.
7. Once approval has been given, follow PackageDB admin requests to request ownership of the package. In addition to this, the new owner must also reassign all open bugs for this package to themselves.

How do we proceed now? PackageDB is no more.

A releng ticket to reassign the package would be the best way forward normally. However, I have just done this for this ticket.

Do we only want to reassign the one package? Or do we want to find maintainers for all their other packages as well?

AFAIK there is only this one. Others are retired. Thanks

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

5 years ago

Login to comment on this ticket.

Metadata