Bug 2171184

Summary:	Non-responsive maintainer check for Fab
Product:	[Fedora] Fedora	Reporter:	Christopher Klooz <py0xc3>
Component:	asciidoc	Assignee:	Fabian Affolter <mail>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	37	CC:	chrisw, jridky, mail, nphilipp
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:	2023-02-18 20:44:44 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 Christopher Klooz 2023-02-18 20:30:35 UTC

This bug is part of the non-responsive maintainer procedure for Fab, 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 asciiDoc.

-------- Forwarded Message from 2/11/23, 01:49 to Fab --------
Hi Fab,

I saw in src.fp.org that you are the asciiDoc maintainer.

It seems asciiDoc has not been updated since Feb 2021. There have been 10 new releases since then, although there is nothing urgent contained I think.

I wrote an email with details to asciidoc-maintainers but have not received an answer (see the attached email below).

Although there have been several bug fixes and some new features since then, a rough skim over the release notes on GitHub [1] does not indicate security-critical issues at the moment, and I have no stability issues either on F37. Nevertheless, I think it makes sense to take a look at the package in the medium term?

[1] https://github.com/asciidoc-py/asciidoc-py/releases

All the best & stay safe.
Regards,
Chris 

-------- Forwarded Message from 1/29/23, 17:25 to asciidoc-maintainers --------

Hi all,

It seems our repository contains still an outdated release from asciiDoc (9.1 from Feb 2021). Current is 10.2. There have been several releases in the last two years that also contain some bug fixes.

The fixes do not look security relevant, but they look reasonable. Maybe it could be checked if updating the package makes sense?

See https://github.com/asciidoc-py/asciidoc-py/releases

All the best & stay safe.

Regards,
Chris

Comment 1 Fabian Affolter 2023-02-18 20:44:44 UTC

I don't see a pull request for the update by the reporter. Also, I don't see any communication with the Fedora Docs teams included here as those guys are the primary consumers for this package.

Comment 2 Christopher Klooz 2023-02-18 21:03:42 UTC

There is no pull request, only the two emails and a topic in the devel mailing list (https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KR62QMEPFICFY2EWLUAUUIRB2IWZQX5R/). I have not said to have opened a pull request. The package is available and distributed in Fedora, not limited to the Docs team. Being a member of the Docs, I can say that the package still works in generating our adocs as far as I experience it, but keeping it updated seems to make sense anyway, doesn't it?

Comment 3 Christopher Klooz 2023-02-19 13:19:57 UTC

I have talked to the team and it seems there is a misunderstanding. We did not know that there are packages that are only updated when this is triggered by us. Maybe you have a collusion with someone who is not in the Docs team or something like that. In any case, there is the opinion that activities from our side should not be part of the maintenance; it seems that I am the only Docs member who uses this package anyway; in either way, we do not consider the use of the asciiDoc package as something officially related to the Docs team. With this in mind, it should be avoided in future to encourage users to contact the Docs team when they want to have the package updated or such. Sorry if there was a misunderstanding somehow. I hope that makes sense.
Thanks for maintaining!
Chris