Generating Income from Open Source
vadimdemedes.com
Generating Income from Open Source
1–10 of 126 posts
Re: Generating Income from Open Source
#2Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs).
I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essentially the same business model, but you use the threat of legal action rather than API keys to enforce your rights. “Open Source” is in the name only.
Re: Generating Income from Open Source
#3Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs). I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essenti…
Open source licenses are commercial licenses, full stop. It doesn't prevent for profit uses.
Re: Generating Income from Open Source
#4I've always looked at charging for open source as a support service. What is the developer's time worth? If one wants new features pay a fee/salary/bounty for the development.
Re: Generating Income from Open Source
#5> Isotope is open source
But it hasn't been updated in years: https://github.com/metafizzy/isotope
Does the commercial license use a different repo?
Re: Generating Income from Open Source
#6Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs). I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essenti…
Free as in free speech, not as in free beer. This has been a slogan of free software for decades. Charging money for your software is not in any way incompatible with open source.
Re: Generating Income from Open Source
#7Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs). I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essenti…
I really think these kinds of comments are counter productive to people seeing source available software (SAS, OSS, FOSS, or all three). Free to the public but not corporate is clearly not "try before you buy" and is a gross misinterpretation of this. I don't care what Citizens United ruling said, corporations are not the same as people and we should distinguish them as such. This model is in no way functionally similar to closed-source software and the comparison is laughable. The source is right there!
__Stop gatekeeping__
Source available software with commercial licensing still helps the main intended target: hackers, builders, inventors, creators, learners, researchers, pen testers, and so on. Opened source code makes programs safer and encourages creativity. The article is right that you can't just live on donations and pure good will, as much as we'd love to see this you gotta pay the bills. Accountability is low in large societies and social pressure means little. SAS still helps the people, but it also puts restrictions on those that would profit off of your work and leave you high and dry. Comments like these only encourage closed source hardware as well as the lack of free software.
The fucking name OSS confuses people and this has been an utter disaster. Your name should clearly indicate what is being advocated and should not conflict with a reasonable but distinctly different definition (there's a lot of this for some fucking reason). Especially when the reasonable interpretation makes more sense! Even you say that it is in the name only and we see these fights almost weekly here. Words mean what people use them as. I don't care what OSI says, OSS and SAS are the same thing. Corporations lose trademarks as words/phrases enter the lexicon, I don't know why we should defend OSI's inane definition. They have not won the culture war on what the term means.
Re: Generating Income from Open Source
#8Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs). I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essenti…
> Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs).
You really do not understand what rights Open Source licenses give you. The GPL in particular really only affects you if you distribute it (a js library vs nginx). There is no 'non-profit' exception in the GPL.
> but you use the threat of legal action rather than API keys to enforce your rights. “Open Source” is in the name only.
Every software company has a license that governs it's use. I am pretty certain your company will use legal threats if it's source code got out or it's frontend code was being abused. There are likely legal clauses in your employment contract over the source code that you have signed.
Re: Generating Income from Open Source
#9Charging for a commercial license is virtual closed-source. You have reinvented selling software, except with a “try before you buy” model that enables engineers to vet its utility first before paying, with free usage for non-profits (i.e. other non-profit devs). I’m not making any comment about the merits of this model. I strictly make and sell closed-source software (SaaS). But it’s funny to me that this is essenti…
I really think these kinds of comments are counter productive to people seeing source available software (SAS, OSS, FOSS, or all three). Free to the public but not corporate is clearly not "try before you buy" and is a gross misinterpretation of this. I don't care what Citizens United ruling said, corporations are not the same as people and we should distinguish them as such. This model is in no way functionally simi…
> Words mean what people use them as. I don't care what OSI says, OSS and SAS are the same thing.
I completely agree. I’ve avoided using the term “open source” where possible for my SAS, instead opting for word-play like “open, source-available”, but it was frustrating that I felt I even needed to do that to avoid backlash from the zealots. And I’ve loosened my reigns there a bit as well as time has gone by. I think it’s silly. I want to use “open source” because that’s what it is.
As an example, there’s no reason Elastic should have had to cave to OSI and start using “free & open” everywhere in place of “open source.” The reality is SAS licenses like ELv2 may not be “Open Source (tm)” but they sure as hell are “open source” to most people in our industry.
FOSS !== OSS.
Re: Generating Income from Open Source
#10The question of whether source code is accessible (open vs. closed) and whether you need to pay someone to do something with that source code (free vs. paid) are two different questions.