FOSS doesn’t mean “we think people that make software should work for free because we like free shit”. It means:
When you want to modify something someone else made to your benefit you should recognize the work they did for you and pay it back in the form of contributing those changes back to the project. Beyond that, it also benefits you directly because someone else might build on your improvements (well, that, but also its easier to stop your changes from breaking in new versions of the software if other people are aware of them). Like the other commenter said, its communal development, sure lots of people do it at least partly because they want to make the world a better place, but the primary reason it works is because the various parties mutually benefit from mutual cooperation.
The belief that you should have complete control over your own computer, which you can’t do in practice without being able to view the source code of the software you run.
There’s a difference between helping out people who are interested in, and capable of learning, improving, contributing to something…
… and people who just want thing work, and are also almost always unwilling to put literally any thought into this process.
‘User Support’ and ‘Collaborative Development’ are not the same thing.
There’s also ‘the computer guy’ syndrome, where a group of people just expect a seemingly infinite amount of uncomoensated time and mental effort from ‘the computer guy’ to solve all their problems, who then take this for granted, and become hostile and offended when you tell them ‘sorry, don’t have the time’, when ‘the computer guy’ has the audacity to… want to do something else at that moment.
It’s so funny to see this on a sub dedicated to FOSS. Trying to imagine how many Pull Requests come with a bill attached.
FOSS doesn’t mean “we think people that make software should work for free because we like free shit”. It means:
When you want to modify something someone else made to your benefit you should recognize the work they did for you and pay it back in the form of contributing those changes back to the project. Beyond that, it also benefits you directly because someone else might build on your improvements (well, that, but also its easier to stop your changes from breaking in new versions of the software if other people are aware of them). Like the other commenter said, its communal development, sure lots of people do it at least partly because they want to make the world a better place, but the primary reason it works is because the various parties mutually benefit from mutual cooperation.
The belief that you should have complete control over your own computer, which you can’t do in practice without being able to view the source code of the software you run.
There’s a difference between helping out people who are interested in, and capable of learning, improving, contributing to something…
… and people who just want thing work, and are also almost always unwilling to put literally any thought into this process.
‘User Support’ and ‘Collaborative Development’ are not the same thing.
There’s also ‘the computer guy’ syndrome, where a group of people just expect a seemingly infinite amount of uncomoensated time and mental effort from ‘the computer guy’ to solve all their problems, who then take this for granted, and become hostile and offended when you tell them ‘sorry, don’t have the time’, when ‘the computer guy’ has the audacity to… want to do something else at that moment.
So much this