An overview on why we changed the license model of EPPlus.
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.
Introducing BOSL, a radically new type of open-source license
Note: This post has been updated to reflect renaming of the Transitive Grace Period Public License (TGPPL) to the Bootstrap Open Source License (BOSL). Electric Coin Co. is spearheading a new type of…
Open source licensing and why we’re changing Plausible to the AGPL license
We’re changing our license as we’ve become aware that there are risks associated with permissive open source licenses that corporations that don’t care about open source are happy to take advantage of.
The Single-Vendor Commercial Open Source Business Model
Dirk Riehle Research, SAP Labs LLC Updated 2010-11-09: Renamed “commercial open source” to “single-vendor (commercial) open source” to be clear about the difference to distr…
Toward Copyleft Equality for All
I would not have imagined even two years ago that expansion of copyleft would become such an issue of interest in software freedom licensing. Historically and for good reason, addition of new forms of copyleft clauses has moved at a steady pace. The early 2000s brought network services clauses (such as that in the Affero GPL), which hinged primarily on requiring provision of source to network-remote users. Affero GPL implemented this via copyright-controlled permission of modification. These licenses began as experiments, and were not approved by some license certification authorities until many years later.
Licensing needs for Truly P2P Software
This article is preserved for historical purposes but HAS BEEN SUPERSEDED BY THE CRYPTOGRAPHIC AUTONOMY LICENSE.
RFC 0015 · Pi Licensing
Mario Zechner is joining us at Earendil and we just acquired Pi. An Open Source project. Earendil is a venture-backed for-profit, public benefit corporation. How do those things go together?
On Long Term Software Development - Bert Hubert's writings
Recently the Dutch Electoral Board (where I am also a very part time advisor) invited me to do a talk reflecting on their open source Abacus vote tabulation software. Much software is now provided as a service, and is typically deployed continuously (CD, continuous deployment), surrounded by enough automated testing (CI, continuous integration) that we can be reasonably sure that a new revision is likely to at least work to some extent.
The Free-Libre / Open Source Software (FLOSS) License Slide
There are a large number of Free-Libre / Open Source Software (FLOSS) licenses, but only a few are widely used. The widely-used licenses tend to be compatible, i.e., the software can be combined to produce a larger work. The following “license slide” figure makes it easy to see when common licenses can be combined:
HUD — Build RL environments
The platform for building RL environments. Train specialized agents, evaluate models, and ship RL datasets backed by HUD infrastructure.
