Supported Source is a licensing model in which software is publicly viewable but commercial use requires a paid license, while individual hobbyists and short-term evaluators can use it for free.
Everything an open source maintainer might need to know about open source licensing | Ben Balter
There's lots of internet lore around open source licensing. An attorney and open source developer answers the most common questions.
Supporting open source with 3% of our revenue | Hacker News
> SPI acts as a fiscal sponsor to many free and open source projects ... we encourage programmers to use the GNU General Public License or other licenses that allow free redistribution and use of software and hardware developers to distribute documentation that will allow device drivers to be written for their product ... all donations made to SPI and its supported projects are tax deductible for donors in the United States.
Licenses – Open Source Initiative
The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License.Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy
Sorting out the Ethical Licensing Mess
Software developers who give the world, for free, usage rights to the code they write often use open source licenses to make this gift legally explicit. These free usage rights (and then some) are …
Introducing the Functional Source License: Freedom without Free-riding
Sentry started life in 2008 as an unlicensed, 71-line Django plugin. The next year we began publishing it under BSD-3, and ten years later we switched to the Business Source License (BSL or BUSL). Last year we purchased Codecov, and a few months ago we published it under BSL/BUSL as well. That led to some vigorous debate because of our use of the term “Open Source” to describe Codecov, from which emerged this helpful suggestion from Adam Jacob, co-founder of Chef:
Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing | TechCrunch
New alternative category to 'closed source' could help companies monetize software in the open -- without going all-in on open source.
Open Source is a cost-allocation system
Because the right to use the software is not tied to payment, the license does not connect the people who benefit, the people who decide, and the people who bear the costs. Projects have to build those connections deliberately through governance.
Time for Net Giants to Pay Fairly for the Open Source on Which They Depend | Linux Journal
Licensing lies at the heart of open source. Arguably, free software began with the publication of the GNU GPL in 1989. And since then, open-source projects are defined as such by virtue of the licenses they adopt and whether the latter meet the Open Source Definition. The continuing importance of licensing is shown by the periodic flame wars that erupt in this area. Recently, there have been two such flarings of strong feelings, both of which raise important issues.
Open source is a restaurant
[[Chad Whitacre]] makes a great analogy around when/how software gets paid for, vs food. Open Source is a restaurant. At a restaurant, you eat your meal fir...
The Money In Open-Source Software | TechCrunch
It’s no secret that open-source technology -- once the province of radicals, hippies and granola eaters -- has gone mainstream. According to industry estimates, more than 180 young companies that give away their software raised roughly $3.2 billion in financing from 2011 to 2014. Despite the growing popularity of open-source software, though, many open-source companies are not financially healthy.
Nobody pays for open source. We can force them to. | Seldo.com
Thirty years of voluntary funding schemes haven't paid open source maintainers because asking doesn't scale. The real money already flows — to JFrog, Docker, Sonatype — at the registry layer. The fix: registries charge companies for supply (they already do), then route a slice automatically to the maintainers who make that supply worth having.
