Post #2453069

I’m starting to think that FOSS projects should explicitly explain which problems are the user’s responsibility and which problems are the project’s responsibility - in a prominent place because often I’ll start using some FOSS but it turns out that I’m expected to put in a lot more work than I have the energy to, and when I complain about it people tell me that it’s my responsibility to make sure that that problem doesn’t happen. if I had known that that was going to be my responsibility, I wouldn’t have used that software. but at that point I’m in an awkward position where I unexpectedly have to either put in effort to fix the problem, or put in effort to find and configure different software some great examples are treesitter-nvim expecting users to figure out neovim version compatibility on their own, and Arch expecting users to keep up with Arch news so that they know which updates might bork something IMO it’s totally fine to shift responsibility onto your users like that - just make sure that every user knows about this from the outset. that way nobody is stuck doing work that they don’t have the energy for, because their software unexpectedly stopped working and it’s their responsibility to fix it