On Thursday, June 12, 2025 1:36:50 PM Mountain Standard Time Andrey Rakhmatullin wrote: > On Thu, Jun 12, 2025 at 02:31:02PM -0500, Aaron Rainbolt wrote: > >However, since I haven't > >gotten any response (no explicit "this would be good, send a patch and > >let's see what you have", no criticism or discussion, etc.), I don't > >know how to proceed. I don't want to submit a patch and have it ignored > >similar to the research and feature requests up to now. I also don't > >want to just wait indefinitely before implementing patches. > > > >I know that for bugfixes, the NMU process can be used to work around an > >unresponsive maintainer, while still giving the maintainer time to take > >a look and fix things if they'd like to. But for this kind of a feature > >addition, I don't know if this is the right approach. As the Debian > >Developer's Reference [5] says, "Using NMUs to make changes that are > >likely to be non-consensual is discouraged." > > > >What's a good way forward here? Am I trying to do something that > >fundamentally shouldn't be done, or is there a good way for me to > >contribute this feature? > > Salvage or hijack, basically.
I would recommend you first create a bug and an associated MR. Then, if you get no response (which is obviously different than a NACK), you can choose if you would like to salvage the package or if you would like to leave the MR there for someone else who to to come along and salvage the package. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
