From: vv221@debian.org 
  
 Disclaimer: I don€€€t like the overhead of the merge request workflow, but 
 I€€€m OK with following it if some contributor really wants to use it. 
  
  
 Le Thu, Aug 14, 2025 at 10:07:02AM -0700, Otto Kek€€l€€inen a €€crit : 
 > It is demotivating to new 
 > aspiring Debian contributors to put in significant effort to learn the 
 > complexities of Debian packaging and submit an improvement, only to 
 > see that the maintainer two months later didn't look at the MR at all, 
 > (€€€) 
  
 I see a discrepancy here between "to put in significant effort to learn 
 the complexities of Debian packaging" and the fact they did not get in 
 touch with the package maintainer. Silently opening a merge request on 
 Salsa is *not* getting in touch. 
  
 I for one only take into consideration contributions by people who 
 actually talk to me about said contributions. Code dump through Salsa do 
 not interest me in the slightest, and no amount of automatic 
 notifications is going to change that for me (I would actually block 
 such notifications). 
  
 To avoid confusion: I€€€m perfectly happy with Salsa being used as a way 
 to send patches, even as a merge request if it is what the contributor 
 would use (I would have been OK with a repo URL + branch name). But the 
 patches are only part of a contribution, and patches without 
 communication are not going to be included in any of the packages I 
 maintain. 
  
 -----BEGIN PGP SIGNATURE----- 
  
 iHUEABYKAB0WIQSUsdxM90hewW6X7Jhja3j5HOuA2AUCaJ4z9AAKCRBja3j5HOuA 
 2IV8AQDXNRom3MYQhE1BZTLkCTFUfO44TWeuPFypc9KnHJSHgAD8Cv4uvOJIpWaF 
 F44O6hGIe6B7MQWi/7D51BelaIFOYww= 
 =dhQ7 
 -----END PGP SIGNATURE----- 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)