3 ms·

I maintain an OSS that is 10x smaller than the author of the post and I have experienced the same absurd community behavior. I feel bad for the state of open s

I maintain an OSS that is 10x smaller than the author of the post and I have experienced the same absurd community behavior. I feel bad for the state of open source [0] - even when Microsoft literally a couple of weeks ago pulled the "FIX THIS NOW" card on ffmpeg https://trac.ffmpeg.org/ticket/10341#comment:4 https://trac.ffmpeg.org/ticket/10341#comment:4 [0] https://blog.tidelift.com/maintainer-burnout-is-real https://blog.tidelift.com/maintainer-burnout-is-real

xtracto 2y ago
We need a FUCK OFF OSS license: like the do-whatever-tf-you-want but with extra clauses telling people to FO. if they want bugfixes, improvements or features. All the free software I had put out there is kind of like that. I don't care about the fame, glory or user count. I release something I built to scratch an itch just because someone else might find it useful. If you didn't like my code, tough luck, go write yours. Edit: call it the FOOSS license, ha!
- orliesaurus 2y ago
  the idea is good in principle but it's not good in practice - we're all grown ups at the end of the day and personally, I don't ask for money, I just ask for a little gratitude and help!
- jraph 2y ago
  I don't think this has any place in a license. That would be a CoC, or a README section. Also just post your project somewhere people can't open issues and ask for improvements. Though I don't think that's what most projects want. You still want feedback usually. You just want to skip the entitled users.
- sevagh 2y ago
  The MIT license already bakes "fuck off" into its core. The license does not put any maintenance burden on the creator. So, choose a regular license, and comport yourself as a maintainer in a manner that tells people to fuck off. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
  - eu_rope 2y ago
    That's going to change with the Cyber Resilience Act (at least in this context, where open source is tied with a commercial activity).
everybodyknows 2y ago
It says something about the state of Microsoft that such a naive coder would be responsible for a critical bug in a "highly visible product". > Hi, This is a high priority ticket and the FFmpeg version is currently used in a highly visible product in Microsoft. We have customers experience issues with Caption during Teams Live Event. Please help,
eviks 2y ago
How did you manage to translate "Please help," into a "FIX THIS NOW"?

xtracto 2y ago

We need a FUCK OFF OSS license: like the do-whatever-tf-you-want but with extra clauses telling people to FO. if they want bugfixes, improvements or features. All the free software I had put out there is kind of like that. I don't care about the fame, glory or user count. I release something I built to scratch an itch just because someone else might find it useful. If you didn't like my code, tough luck, go write yours. Edit: call it the FOOSS license, ha!

orliesaurus 2y ago
the idea is good in principle but it's not good in practice - we're all grown ups at the end of the day and personally, I don't ask for money, I just ask for a little gratitude and help!
jraph 2y ago
I don't think this has any place in a license. That would be a CoC, or a README section. Also just post your project somewhere people can't open issues and ask for improvements. Though I don't think that's what most projects want. You still want feedback usually. You just want to skip the entitled users.
sevagh 2y ago
The MIT license already bakes "fuck off" into its core. The license does not put any maintenance burden on the creator. So, choose a regular license, and comport yourself as a maintainer in a manner that tells people to fuck off. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
- eu_rope 2y ago
  That's going to change with the Cyber Resilience Act (at least in this context, where open source is tied with a commercial activity).

everybodyknows 2y ago

It says something about the state of Microsoft that such a naive coder would be responsible for a critical bug in a "highly visible product". > Hi, This is a high priority ticket and the FFmpeg version is currently used in a highly visible product in Microsoft. We have customers experience issues with Caption during Teams Live Event. Please help,

eviks 2y ago

How did you manage to translate "Please help," into a "FIX THIS NOW"?