3 ms·
I fail to see the "problem with being an unpaid volunteer" angle in this story, I wonder why ffmpeg staff worded it that way. Open source always had this "dange
by poisonborz 3y ago
I fail to see the "problem with being an unpaid volunteer" angle in this story, I wonder why ffmpeg staff worded it that way. Open source always had this "danger", yet the massive benefits made corps never question their use day by day. And with "massive benefits" I actually mean "it holds everything else on its shoulders".
- orev 3y agoIt explains right in the tweet. Big companies take unpaid work and start to rely on it without giving anything back, then demand fixes as high priority. Also, being unpaid implies that one has to do other things to get money, so that leaves limited time and energy to put towards the free project. So when pressure starts coming in from outside, the maintainer(s) don’t have time for real reviews and accept code without fully vetting it. If maintaining this code was part of a paid day job, there would be more time, energy, and incentive to review it more completely.
- sys_64738 3y agoOpen source code is generally supplied as-is without any liability acceptance or warranty. If your business relies on it and it has bugs then that is the business's problem to deal with.