Bug 2007971

Summary:	Non-responsive maintainer check for "java-maint-sig@lists.fedoraproject.org"
Product:	[Fedora] Fedora	Reporter:	Stefan Bluhm <fedoraproject.org>
Component:	snakeyaml	Assignee:	Java Package Maintainers <java-maint-sig>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	decathorpe, jaromir.capik, java-maint-sig, java-sig-commits, jerboaa, mizdebsk, mo
Target Milestone:	---
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:	2021-09-26 17:54:59 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 Stefan Bluhm 2021-09-26 16:23:58 UTC

This bug is part of the non-responsive maintainer procedure for java-maint-sig.org, 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 snakeyaml.

Comment 1 Fabio Valentini 2021-09-26 17:28:20 UTC

Groups cannot be primary maintainer of a package, so they can't really be unresponsive, either.
The person you should be asking if they are unresponsive is the "main admin", jerboaa, as they are the person primarily responsible for snakeyaml.

(It seems you have been confused by the "Bugzilla assignee" entry that lists @java-maint-sig,java-maint-sig, but the primary maintainer is still the one listed under "Memmbers" as "main admin") here: https://src.fedoraproject.org/rpms/snakeyaml

Comment 2 Stefan Bluhm 2021-09-26 17:54:59 UTC

Thank you Fabio.
you are right that I confused the "Bugzilla assignee" as the main maintainer. Let me get in touch with the main admin whom I left out of this completely.

Best wishes,

Stefan