3 ms·

> There isn't any "victims" here? What do you call the state that indie open source maintainers are in right now? Lack of business mindset? Skill issue? > You

by shprd 2y ago

> There isn't any "victims" here? What do you call the state that indie open source maintainers are in right now? Lack of business mindset? Skill issue? > You and others seem to constantly misrepresent what FOSS explicitly means, and start involving some implicit rules about what FOSS means and should be I thought "the vision" and a major corner of open source is others contributing and building on top of each other? Which of the following is more FOSS: - Putting your code online and saying no to requests - Collaborating together and contributing back? Why do you refuse to promote the second option? How does it go against FOSS? To me, it sounds much healthier for the ecosystem and more along the spirit of FOSS. I'm not sure what definition of FOSS make you blame those frustrated with the lack of contribution and trying to promote it.

diggan 2y ago
> What do you call the state that "indie" open source maintainers are in right now? Lack of business mindset? Skill issue? If I had to call it something, I guess it would be something along the lines of "Not realizing the control they have over their projects". If you're writing FOSS not to earn money or build a business, and AWS employees approaches you asking for features, you as a maintainer has the power and control to say "Nope", and no one would bat an eye, because that's the contract they implicitly signed by using your software in the first place. > Which of the following is more FOSS Neither, as neither are actually related to FOSS at all. The first is a process you can apply in order to remain sane if there is pressure to implement features you don't care about and don't want to implement. The second is something you can do on top of FOSS if you want, or not. Choosing one over the other isn't more/less FOSS. > Why do you refuse to promote the second one? I don't refuse that, I promote plenty of communities around FOSS projects, and probably wouldn't had a career in software at all if it wasn't for FOSS, and most of my time daily is spent doing FOSS. > How does it go against FOSS? It doesn't go against, but people need to appreciate there is a difference between "Building a community" and "Publishing FOSS". One does not mean the other is required, either way.

by shprd 2y ago

diggan 2y ago

> What do you call the state that "indie" open source maintainers are in right now? Lack of business mindset? Skill issue? If I had to call it something, I guess it would be something along the lines of "Not realizing the control they have over their projects". If you're writing FOSS not to earn money or build a business, and AWS employees approaches you asking for features, you as a maintainer has the power and control to say "Nope", and no one would bat an eye, because that's the contract they implicitly signed by using your software in the first place. > Which of the following is more FOSS Neither, as neither are actually related to FOSS at all. The first is a process you can apply in order to remain sane if there is pressure to implement features you don't care about and don't want to implement. The second is something you can do on top of FOSS if you want, or not. Choosing one over the other isn't more/less FOSS. > Why do you refuse to promote the second one? I don't refuse that, I promote plenty of communities around FOSS projects, and probably wouldn't had a career in software at all if it wasn't for FOSS, and most of my time daily is spent doing FOSS. > How does it go against FOSS? It doesn't go against, but people need to appreciate there is a difference between "Building a community" and "Publishing FOSS". One does not mean the other is required, either way.