On Wednesday, May 7, 2025 10:56:43 AM Mountain Standard Time Jonas Smedegaard 
wrote:
> Quoting Holger Levsen (2025-05-07 18:59:27)
> 
> > On Wed, May 07, 2025 at 05:42:39PM +0200, Jonas Smedegaard wrote:
> > > Since you asked: I respectfully find ITN a very bad idea.
> > 
> > +1

I personally think this is a good idea, because it meets a need that isn’t 
currently well met, which is that some packages have problems with them that 
extend beyond what we currently handle in an NMU.

I have recently dealt with a few packages like this.  I handled it using the 
Salvaging process.  But having some sort of expanded NMU process would have 
been preferable to me.

We need some step that is in-between a standard NMU and a full orphaning to QA 
or salvaging of the package.  What filing an ITN does is give a heads up to 
the maintainer and uploaders that there is a desire to do an NMU that that 
addresses these bigger problems with the package.  It provides a notification 
period during which they can object.  If they do object, then the expanded NMU 
doesn’t happen.  If they don’t object, then the package is brought up-to-date 
with current best practices.

I don’t see this as offensive or rude to the maintainer and uploaders at all.  
If this ever happened to me I would respond in one of the following ways, 
depending on circumstances:

1.  Go right ahead.  The package could use some love I can’t give it right 
now.

2.  Please don’t touch the package.  I will get to it soon.

3.  Would you like help me co-maintain the package?

4.  Would you like to adopt the package?

In any of the cases, there are no hard feelings.

Note that I don’t have a strong opinion about what this should be called (NMU, 
ITN, expanded NMU, something else).  What I do think is important is that we 
have some common mechanism to ask, “Would you mind if I did an big update to 
your package?”  As long as the maintainer has sufficient time to say no, and 
as long as that no is respected, then I think this is a wonderful idea.

-- 
Soren Stoutner
so...@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to