GitHub should charge everyone $1 more per month to fund open source
81–90 of 352 posts
Re: GitHub should charge everyone $1 more per month to fund open source
#82Corporations who use and benefit from software should be made to pay for their use of that software, but they don't want to, which is why they'll happily spend money promoting the use of corporate-friendly and maximally exploitable open source licensing among the passionate individuals who maintain the lions share of their dependency tree.
Re: GitHub should charge everyone $1 more per month to fund open source
#83Maybe it's just me, but I don't think the solution to the open source funding problem is to force people to pay for it. I think that goes against the spirit of open source. If there is forced payment, or even the expectation of payment, then we're not really doing the whole original open source thing, we're just doing bad source available commercial-ish software. I think the solution is for people to understand that…
If they pay by popularity most of my $1 would go to javascript. I'd rather it went to libraries I actually use.
Re: GitHub should charge everyone $1 more per month to fund open source
#84Not a great take. Corporations who use and benefit from software should be made to pay for their use of that software, but they don't want to, which is why they'll happily spend money promoting the use of corporate-friendly and maximally exploitable open source licensing among the passionate individuals who maintain the lions share of their dependency tree. https://lgug2z.com/articles/on-evils-in-software-licensing/
Re: GitHub should charge everyone $1 more per month to fund open source
#85Re: GitHub should charge everyone $1 more per month to fund open source
#86> it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments. I am. I enjoy making things, and it's even better when others enjoy them. Just because you have expectations that you should be compensated for everything line of code you write; doesn't make it ubiquitous, nor should your expectations be considered the default. I…
My apologies - you’re correct. I didn’t mean that as “you should never expect anyone to have contributed code for free/the pleasure/for the puzzle solving aspect”. I do it all of the time. I meant - it’s unfair to consider that because this labor “fell from the sky”, you should just accept it - and as others have said, in the case of projects that become popular, that the burden should just automatically fall on the…
"Open Source" is hugely conflated in terms of the reasons people write open source software.
There are people who truly don't care to be compensated for their work. Some are even fine with corporations using it without receiving any benefit.
Some people prefer viral and infectious licenses the way that Stallman originally intended and that the FSF later lost sight of (the AGPL isn't strong enough, and the advocacy fell flat). They don't want to give corporations any wiggle room in using their craft and want anyone benefiting from it in any way to agree to the same terms for their own extensions.
Many corporations, some insidiously, use open source as a means of getting free labor. It's not just free code, but entire ecosystems of software and talent pools of engineers that appear, ready to take advantage of. These same companies often do not publish their code as open source. AWS and GCP are huge beneficiaries that come to mind, yet you don't have hyperscaler code to spin up. They get free karma for pushing the "ethos" of open source while not giving the important parts back. Linux having more users means more AWS and GCP customers, yet those customers will never get the AWS and GCP systems for themselves.
There are "impure" and "non-OSI" licenses such as Fair Source and Fair Code that enable companies to build in the open and give customers the keys to the kingdom. They just reserve the sole right to compete on offering the software. OSI purists attack this, yet these types of licenses enable consumers do to whatever they want with the code except for reselling it. If we care about sustainability, we wouldn't attack the gesture.
There are really multiple things going on in "open source" and we're calling it all by the same imprecise nomenclature.
The purists would argue not and that the OSI definition is all that matters. But look at how much of the conversation disappears when you adhere to that, and what behavior slips by.
Re: GitHub should charge everyone $1 more per month to fund open source
#87Not a great take. Corporations who use and benefit from software should be made to pay for their use of that software, but they don't want to, which is why they'll happily spend money promoting the use of corporate-friendly and maximally exploitable open source licensing among the passionate individuals who maintain the lions share of their dependency tree. https://lgug2z.com/articles/on-evils-in-software-licensing/
If you don't want to give your software away for free, don't give your software away for free. When they decide it is in their best interest to pay for it they will, i.e. support, bug fixes, changes. If you make open source software that just works they are unlikely to start writing checks nor should there be any expectation that they do that.
I don't, and I spend a lot of my time and efforts encouraging others not to, and doing the work to prove out alternative models :)
https://lgug2z.com/articles/normalize-identifying-corporate-...
https://lgug2z.com/articles/komorebi-financial-breakdown-for...
Re: GitHub should charge everyone $1 more per month to fund open source
#88> it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments. I am. I enjoy making things, and it's even better when others enjoy them. Just because you have expectations that you should be compensated for everything line of code you write; doesn't make it ubiquitous, nor should your expectations be considered the default. I…
I agree with you, but I do think we have a bit of a problem in which an open source creator makes something and then suddenly finds themselves accidentally having created a load-bearing component that is not only used by a lot of people and companies, but where people are demanding that bugs be fixed, etc., and we lack great models for helping transition it from "I do this for fun, might fix the bug if I ever feel li…