Hello,

In most recent Ubuntu cycles, I've taken on the "archive bootstrapping" 
responsibility of adding the new Ubuntu codename to Lintian. I remember 
having some deeper conversations with the former Lintian maintainer 
regarding further contributions and maintenance, but I also recall some 
politics, and quite frankly, *I don't care*. Regardless, Lintian is 
something I look at every cycle.

I'm writing today to express my concern about the current state of 
Lintian maintenance. I already understand that there is an RFH filed 
against Lintian, but that has not received any sort of followup since 
2022. The most recent Lintian upload is from March 2023, and as of the 
time of writing, there are 26 open merge requests[1].

I also understand that this is a volunteer team. My goal here is not to 
diminish the work of the current maintainers in any way, quite the 
opposite. I would simply like to ask, "do you need help?"

I'm not volunteering to take over Lintian entirely, nor do I want to. 
That being said, I would be motivated to sort through the current MR 
list and at least shave off some technical debt. If this is something 
you are open to, or if anyone else would be open to this as well, I 
think it is a worthwhile effort.

Lintian is crucially important for Debian development as it stands 
today. Before sponsoring a package, before uploading our own packages, 
and even once in the archive, we run Lintian all the time. I do not 
believe it is too late to put some additional minds behind this, to 
ensure Lintian survives for years to come. I simply feel as if *someone* 
should bump this thread, so we do not lose sight of it.

Thank you for your time. Please do let me know if you have any 
questions, or if I can do anything else to help.

[1] https://salsa.debian.org/lintian/lintian/-/merge_requests

Warm regards,

--
Simon Quigley
si...@tsimonq2.net
tsimonq2 on LiberaChat and OFTC
@tsimonq2:ubuntu.com on Matrix
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4

Attachment: smime.p7m
Description: smime.p7m

Reply via email to