#1477 Nonresponsive Package Maintainer
Closed None Opened 8 years ago by lfield.

= phenomenon =

Non-responsive Package Maintainer for the boinc-client

= reason =

The following ticket has been open for some time without any comment from the package maintainer.

https://bugzilla.redhat.com/show_bug.cgi?id=1140826

Various attempts have been made to contact the packager without success

= recommendation =

Suggest to orphan the package and assign ownership to Laurence Field


Frankly, I don't think this is a valid non-responsive maintainer report. The bug in question isn't a bug. It is a request to add the package to EPEL7. That is completely optional and not something a package maintainer is required to do. The package certainly shouldn't be orphaned entirely based solely on this single bug. EPEL maintainership can be granted to others outside of the normal Fedora package maintainership.

Also, the choice of assignment in the recommendation is odd. We don't normally specifically assign packages to people unless they are already co-maintainers.

Are there other bugs or issues that we should be aware of that are more illustrative of a non-responsive maintainer?

To add further to my invalid report statement, does anyone have links to devel list postings saying they have been unable to contact the maintainer and need help? I can't find any.

We have a process: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

and it certainly doesn't appear to have been followed here at all.

I am trying to follow the procedure the best I can. This morning I posted to the mailing list but received a message back that I was not allowed to post to the mailing list, hence moved on to the next step as we have not been able to contact the maintainers despite repeated attempts.

There was a delayed response with the EPEL6 request back in January of 2014. The backup maintainer stepped in, but has now resigned. At the time we were in email contact but now there is no response. Yesterday I requested to be a package administrator to help resolve this issue but this is still pending.

As we have not been able to contact the package maintainer, we are flagging this as non-responsive and are stepping forward to provide a solution to support a component that is useful for many scientific communities.

In the bug there is a specific comment on August 7th 2015 asking if there is an active maintainer to which there has been no response. Hence the state of the maintainer is non-responsive until someone gets a response.

You must be subscribed to the devel list to post... please make sure you are subscribed.

I have posted to the devel list but no responses from the maintainers so far.

https://lists.fedoraproject.org/pipermail/devel/2015-September/214792.html
https://lists.fedoraproject.org/pipermail/devel/2015-September/214878.html

Maintainers still in the status non-responsive.

Hello all,

I granted the permissions on the branches I had as a co-maintainer to Laurence.

+1 for granting it for other branches too.

Marek

Adding meeting keyword.

All of mjakubicek's packages have been orphaned. Please take those that you wish to become point of contact on.

Login to comment on this ticket.

Metadata