#2171 Unresponsive Maintainer: dchen
Closed: Accepted 2 years ago by zbyszek. Opened 2 years ago by decathorpe.

Looking at bodhi, koji and bugzilla, it looks like he suddenly stopped contributing to fedora in August 2018. There were no koji builds, bodhi updates, bodhi comments, or comments on bugzilla since then.

Looking at the open bugs, it seems like he stopped working at Red Hat at the beginning of August 2018, coinciding with the end of contributions towards fedora packages. He has not responded to multiple nagging / needinfo FTBFS bugs and even security issues since August 2018.

I posted to the devel mailing list 10 days ago, asking for more information, but got no responses.

Since his broken Java packages hinder some of the cleanup work and fixing we're doing for the Stewardship SIG, I request that all his packages are orphaned, so they can get cleaned up properly (either with a new maintainer or retired).


To clarify, this a short-circuit request for the nonrseponsive policy, correct?

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

2 years ago

Yes and no. I did not take one of his bugs, created a needinfo request, and added more comments for three more weeks - because an equivalent thing already happened for all his FTBFS bugs, for example, here: https://bugzilla.redhat.com/show_bug.cgi?id=1674627

If you consider this a short-circuit in the literal reading of the non-responsive maintainer policy, I can continue adding comments to those bug reports :wink:

In the general case, I'd be against counting automated releng bugzillas and bugzilla comments as nonresponsive reminders. The policy clearly says you should open a bugzilla and you should ask the maintainer to response.

OTOH if you explicitly play the "If there is no known way of contacting the former maintainer ... one can short-circuit the normal 3 week interval required in the Outline steps 1 to 3, and make the formal request to orphan mentioned in step 4." card, I would gladly sanction that.

Alright, I'll follow up on this issue when it's time.

For the record, I've picked this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1675164

Metadata Update from @zbyszek:
- Issue tagged with: stalled

2 years ago

Metadata Update from @churchyard:
- Issue untagged with: stalled

2 years ago

Since this was filed according to the old/current https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ - it is now approved (+3, 0, -0).

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

2 years ago

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

2 years ago

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement

2 years ago

Login to comment on this ticket.

Metadata