Bug 2087212

Summary: Non-responsive maintainer check for adeza
Product: [Fedora] Fedora Reporter: Mikel Olasagasti Uranga <mikel>
Component: python-repoze-lruAssignee: Fedora Infrastructure SIG <infra-sig>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: adeza, infra-sig, jcaratza, kevin, ktdreyer, lewk, mhroncok, ondrejj, rbean, thomas.moschny
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-25 11:14:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mikel Olasagasti Uranga 2022-05-17 15:17:09 UTC
This bug is part of the non-responsive maintainer procedure for adeza, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

Please respond if you are still active in Fedora and want to maintain python-execnet.

Comment 1 Thomas Moschny 2022-05-17 21:50:06 UTC
Huh? One of the requirements went stable only yesterday.

Will look into this now.

Comment 2 Mikel Olasagasti Uranga 2022-05-17 21:57:45 UTC
I'm following the non-repsonsive maintainer procedure for Alfredo.

As reported in devel-list, Alfredo was using a @redhat email but he is not an employee anymore, so the account is unreachable. As the procedure requires a BZ to be opened and the ticket requires a component, I opened against python-execnet as it is the package I realized with that he was not active anymore.

Comment 3 Thomas Moschny 2022-05-17 22:04:21 UTC
But adeza is not the main maintainer of this package ... Maybe another package would be more appropriate.

Comment 4 Thomas Moschny 2022-05-24 11:14:09 UTC
See also bug 2033140.

Closing here.

Comment 5 Mikel Olasagasti Uranga 2022-05-24 12:21:51 UTC
Switching component and reopening.

The BZ was not for non-responsive maintainers of python-execnet, but a non-responsive check for Alfredo that happens to be one of the admins.

Comment 6 Kevin Fenzi 2022-05-25 01:01:10 UTC
So, what action do you need from adeza here?

Is there an update needed? a bug? I don't see any bugs open... (aside this one)

Comment 7 Mikel Olasagasti Uranga 2022-05-25 11:13:24 UTC
Nothing, I'm just following the non-responsive maintainer procedure for Alfredo, not the package, that requires a BZ to be opened. We need this open until FESCO completes the procedure.

Comment 8 Miro HronĨok 2022-05-25 11:14:05 UTC
https://pagure.io/fesco/issue/2798

Comment 9 Jan ONDREJ 2022-05-30 10:13:15 UTC
I am a bit confused. Is someone planning to take repoze-lru package?

Justin Caratzas, you are currently admin. Are you planning to maintain this package?
If yes, I need an EPEL9 build.

If nobody takes it, I will. It's needed for TurboGears package, even if it should be simply to remove it's dependency, but lru looks to be simple package, so it's better to leave it in Fedora/EPEL.

Comment 10 Mikel Olasagasti Uranga 2022-05-30 11:56:42 UTC
I'm not planning to take repoze-lru package.

Comment 11 Jan ONDREJ 2022-05-31 07:19:53 UTC
aekoroglu has already taken this package. Thanks.