Source-available software

From HandWiki
Short description: Software licensed to ensure access to source code


Source-available software is software released through a source code distribution model that includes arrangements where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source.[1] The licenses associated with the offerings range from allowing code to be viewed for reference to allowing code to be modified and redistributed for both commercial and non-commercial purposes.[2]

Distinction from free and open-source software

Any software is source-available in the broad sense as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify or even compile it. It is possible for a software to be both source-available software and proprietary software (e.g. id Software's Doom).

In contrast, the definitions of free software and open-source software are much narrower. Free software and/or open-source software is also always source-available software, but not all source-available software is also free software and/or open-source software. This is because the official definitions of those terms require considerable additional rights as to what the user can do with the available source (including, typically, the right to use said software, with attribution, in derived commercial products).[3]

In the broad sense, any FOSS license is a source-available license. In the narrow sense,[1] the term source-available specifically excludes FOSS software.

Non-free licenses

The following source-available software licenses are considered non-free licenses because they have limitations that prevent them from being open-source according to the Open Source Initiative and free to the Free Software Foundation.

Commons Clause

The Commons Clause, created by Fossa, Inc., is an addendum to an open-source software license that restricts users from selling the software. Under the combined license, the software is source-available, but not open-source.[4]

On August 22, 2018, Redis Labs shifted some Redis Modules from the Affero General Public License[5][6] to a combination of the Apache License 2.0 and the Commons Clause.[7][8]

In September 2018, Matthew Garrett criticized Commons Clause calling it an "older way of doing things" and said it "doesn't help the commons".[9]

GitLab Enterprise Edition License (EE License)

The GitLab Enterprise Edition License is used exclusively by GitLab's commercial offering.[10] GitLab also releases a Community Edition under the MIT License.[11]

GitLab Inc. openly discloses that the EE License makes their Enterprise Edition product "proprietary, closed source code."[12] However, the company makes the source code of the Community Edition public, as well as the repository's issue tracker, and allows users to modify the source code.[13] The dual release of the closed-source Enterprise Edition and the open-source Community Edition makes GitLab an open core company.

Mega Limited Code Review Licence

In 2016, Mega Ltd. released the source code of their Mega clients under the Mega Limited Code Review Licence, which only permits usage of the code "for the purposes of review and commentary".[14] The source code was released after former director Kim Dotcom stated that he would "create a Mega competitor that is completely open source and non-profit" following his departure from Mega Ltd.[15][16]

Microsoft Shared Source Initiative

Microsoft's Shared Source Initiative, launched in May 2001, comprises 5 licenses, 2 of which are open-source and 3 of which are restricted. The restricted licenses under this scheme are the Microsoft Limited Public License (Ms-LPL),[17] the Microsoft Limited Reciprocal License (Ms-LRL),[18] and the Microsoft Reference Source License (Ms-RSL).[19]

Old Scilab License

Prior to version 5, Scilab described itself as "the open source platform for numerical computation"[20] but had a license[21] that forbade commercial redistribution of modified versions. Versions 5 and later are distributed under the GPL-compatible CeCILL license.

Server Side Public License

Further information: Software:Server Side Public License

The Server Side Public License is a modification of the GNU Affero General Public License created by the MongoDB project. It modifies a clause relating to usage of the licensed work over a network, stating that if SSPL-licensed software is incorporated into a "service" offered to other users, the source code for the entirety of the service (including without limitation all software and APIs that would be required for a user to run an instance of the service themselves) must be released under the SSPL.[22] The license is considered non-free by the Open Source Initiative, Debian and Red Hat, as it contains conditions that are unduly discriminatory towards commercial use of the software.[23][24]

SugarCRM Public License

In 2007 Michael Tiemann, president of OSI, had criticized[25] companies such as SugarCRM for promoting their software as "open source" when in fact it did not have an OSI-approved license. In SugarCRM's case, it was because the software is so-called "badgeware"[26] since it specified a "badge" that must be displayed in the user interface. SugarCRM's open source version was re-licensed under the GPL version 3 in 2007,[27] and later the GNU Affero GPL version 3 in 2010.[28]

TrueCrypt License

The TrueCrypt License was used by the TrueCrypt disk encryption utility.[29] When TrueCrypt was discontinued, the VeraCrypt fork switched to the Apache License, but retained the TrueCrypt License for code inherited from TrueCrypt.[30]

The Open Source Initiative rejects the TrueCrypt License, as "it has elements incompatible with the OSD."[31] The Free Software Foundation criticizes the license for restricting who can execute the program, and for enforcing a trademark condition.[32]

BeeGFS End User License Agreement

BeeGFS EULA is the license of the distributed parallel file system BeeGFS, except the client for Linux, which is licensed under GPLv2.[33]

BeeGFS source code is publicly available from their website,[34] and because of this they claiming BeeGFS as "Open-Source" software;[35] it is in fact not because this license prohibits distributing modified versions of the software, or using certain features of the software without authorization.[36]

See also

References

  1. ↑ 1.0 1.1 "DoD Open Source Software (OSS) FAQ: Is there a name for software whose source code is publicly available, but does not meet the definition of open source software?". U.S. Department of Defense. https://dodcio.defense.gov/Open-Source-Software-FAQ/. 
  2. ↑ Fortunato, Laura; Galassi, Mark (17 May 2021). "The case for free and open source software in research and scholarship". Philosophical Transactions of the Royal Society A 379 (2197). doi:10.1098/rsta.2020.0079. PMID 33775148. 
  3. ↑ "The Open Source Definition | Open Source Initiative". https://opensource.org/osd. 
  4. ↑ "Commons Clause License". https://commonsclause.com/. 
  5. ↑ Shoolman, Yiftach (5 July 2016). "Why Redis Labs' Modules are AGPL". https://redislabs.com/blog/why-redis-labs-modules-are-agpl/. 
  6. ↑ Claburn, Thomas. "Redis has a license to kill: Open-source database maker takes some code proprietary". https://www.theregister.co.uk/2018/08/23/redis_database_license_change/. 
  7. ↑ "Commons Clause License". https://commonsclause.com/. 
  8. ↑ Asay, Matt. "Why Redis Labs made a huge mistake when it changed its open source licensing strategy". TechRepublic. https://www.techrepublic.com/article/why-redis-labs-made-a-huge-mistake-when-it-changed-its-open-source-licensing-strategy/. 
  9. ↑ The Commons Clause doesn't help the commons Matthew Garrett's blog
  10. ↑ "The GitLab Enterprise Edition (EE) license (the "EE License")". GitLab Inc.. 16 May 2018. https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE. 
  11. ↑ "GitLab Community Edition LICENSE file". GitLab Inc.. 15 May 2018. https://gitlab.com/gitlab-org/gitlab-ce/blob/master/LICENSE. 
  12. ↑ Sijbrandij, Sid (20 Jul 2016). "GitLab is open core, GitHub is closed source". GitLab Inc.. https://about.gitlab.com/2016/07/20/gitlab-is-open-core-github-is-closed-source/. 
  13. ↑ "GitLab Community Edition". GitLab Inc.. https://gitlab.com/gitlab-org/gitlab-ce. 
  14. ↑ "meganz/MEGAsync". 2017-09-07. https://github.com/meganz/MEGAsync/blob/master/LICENCE.md. 
  15. ↑ "Interviews: Kim Dotcom Answers Your Questions - Slashdot". 2015-07-30. https://yro.slashdot.org/story/15/07/27/200204/interviews-kim-dotcom-answers-your-questions. 
  16. ↑ "Kim Dotcom promises to launch an open-source competitor to Mega (updated)". Engadget. 2015-07-31. https://www.engadget.com/2015/07/31/kim-dotcom-new-site-mega/. 
  17. ↑ "Microsoft Limited Public License (Ms-LPL)". http://www.microsoft.com/resources/sharedsource/licensingbasics/limitedpubliclicense.mspx. 
  18. ↑ "Microsoft Limited Reciprocal License (Ms-LRL)". http://www.microsoft.com/resources/sharedsource/licensingbasics/limitedreciprocallicense.mspx. 
  19. ↑ "Microsoft Reference Source License". Microsoft. 2016-07-06. http://referencesource.microsoft.com/license.html. ""Reference use" means use of the software within your company as a reference, in read-only form, for the sole purposes of debugging your products, maintaining your products, or enhancing the interoperability of your products with the software, and specifically excludes the right to distribute the software outside of your company." 
  20. ↑ "The open source platform for numerical computation". INRIA. http://www.scilab.org. 
  21. ↑ "SCILAB License". INRIA. http://www.scilab.org/legal/license.html. 
  22. ↑ Staff, Ars (October 16, 2019). "In 2019, multiple open source companies changed course—is it the right move?". https://arstechnica.com/information-technology/2019/10/is-the-software-world-taking-too-much-from-the-open-source-community/. 
  23. ↑ Vaughan-Nichols, Steven J.. "MongoDB "open-source" Server Side Public License rejected" (in en). https://www.zdnet.com/article/mongodb-open-source-server-side-public-license-rejected/. 
  24. ↑ "MongoDB's licensing changes led Red Hat to drop the database from the latest version of its server OS" (in en-US). January 16, 2019. https://www.geekwire.com/2019/mongodbs-licensing-changes-led-red-hat-drop-database-latest-version-server-os/. 
  25. ↑ Tiemann, Michael (2007-06-21). "Will The Real Open Source CRM Please Stand Up?". Open Source Initiative. http://www.opensource.org/node/163. 
  26. ↑ Berlind, David (2006-11-21). "Are SugarCRM, Socialtext, Zimbra, Scalix and others abusing the term "open source?"". ZDNet. http://blogs.zdnet.com/BTL/index.php?p=3430. 
  27. ↑ Vance, Ashlee (2007-07-25). "SugarCRM trades badgeware for GPL 3". The Register. http://www.regdeveloper.co.uk/2007/07/25/sugarcrm_gpl3/. 
  28. ↑ "The SSPL is Not an Open Source License". Open Source Initiative. 19 January 2021. https://opensource.org/node/1099. 
  29. ↑ "truecrypt-archive/License-v3.1.txt at master · DrWhax/truecrypt-archive". 28 Mar 2014. https://github.com/DrWhax/truecrypt-archive/blob/master/doc/License-v3.1.txt. 
  30. ↑ "root/License.txt". TrueCrypt Foundation. 17 Oct 2016. https://www.veracrypt.fr/code/VeraCrypt/tree/License.txt?h=VeraCrypt_1.19. 
  31. ↑ Phipps, Simon (15 November 2013), TrueCrypt or false? Would-be open source project must clean up its act, InfoWorld, http://www.infoworld.com/d/open-source-software/truecrypt-or-false-would-be-open-source-project-must-clean-its-act-230862, retrieved 20 May 2014 
  32. ↑ "Various Licenses and Comments about Them". Free Software Foundation. https://www.gnu.org/licenses/license-list.html. 
  33. ↑ "BeeGFS End User License Agreement - Documentation - BeeGFS". https://www.beegfs.io/content/documentation/#eula. 
  34. ↑ "GitLab". https://www.beegfs.io/source. 
  35. ↑ "Frequently Asked Questions (FAQ)". https://www.beegfs.io/wiki/FAQ#open_source. 
  36. ↑ "End-User License Agreement" (plain text). 2019-09-10. https://www.beegfs.io/docs/BeeGFS_EULA.txt. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Source-available_software&oldid=3363477"