Conversation

Notices

1. Embed this notice
   Thorsten Leemhuis (acct. 1/4) (kernellogger@fosstodon.org)'s status on Monday, 10-Feb-2025 18:52:56 JST Thorsten Leemhuis (acct. 1/4)

   Linus on the social media shaming in the context of the #Rust on #Linux DMA drama[1]:

   https://lore.kernel.org/all/CAHk-%3Dwi%3DZmP2%3DTmHsFSUGq8vUZAOWWSK1vrJarMaOhReDRQRYQ@mail.gmail.com/

   "'[…] the current process works.

   It has problems, but problems are a fact of life. There is no perfect.

   However, I will say that the social media brigading just makes me not want to have anything at all to do with your approach.

   […] Technical patches and discussions matter. Social media brigading - no than\k you.

   Linus"'

   [1] https://fosstodon.org/@kernellogger/113955147394109633

   #kernel #LinuxKernel #Rustlang

   • Embed this notice
     Thorsten Leemhuis (acct. 1/4) (kernellogger@fosstodon.org)'s status on Monday, 10-Feb-2025 18:52:53 JST Thorsten Leemhuis (acct. 1/4)

     in reply to

     • Ike

     @ike there are many aspects at play here, but let me pick one that stuck out:

     In a professional setting you work in the interest of the company for the money you get in return.

     In FLOSS projects like Linux (the kernel) everyone is a volunteer with a different motivation. As project leader you don't want to step on people toes without strong needs too often (especially not those of core people), as that can quickly ruin a project. It's similar in sports clubs, rabbit breeders association, …

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 10-Feb-2025 18:52:53 JST 翠星石

     in reply to

     • Ike
     @kernellogger @ike >In FLOSS projects like Linux (the kernel)
     Linux is not even a source-available project - it contains proprietary software without source code, making it proprietary software.
   • Embed this notice
     Ike (ike@pkm.social)'s status on Monday, 10-Feb-2025 18:52:55 JST Ike

     in reply to

     @kernellogger In professional work and more, blockers need to say "here is what I need in order to say `yes`" instead of just offering a blanket "no". Then, they are part of the solution rather than impeding it.

     The maintainer failed this, and therefore demonstrated that this was personal to them rather than about whats best for the codebase that they maintain.

     Maybe thats viable for open source projects, but it hasn't worked for me in professional settings.

   • Embed this notice
     Ike (ike@pkm.social)'s status on Monday, 10-Feb-2025 18:52:56 JST Ike

     in reply to

     @kernellogger I'm really disappointed with that response, tbh.

     Yeah partly because I want to see Rust expand its footprint everywhere, but partly because I do think that the maintainer could have just left it at "I'm unable to maintain non-C code in the codebase at this time" without calling Rust or other programming languages "cancers".

     I'm actually glad that this was raised on social media so I can learn what contributing in open source is like in projects like this.