Source-available software

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Not to be confused with Open-source software.

Lua error in package.lua at line 80: module 'strict' not found.

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.[citation needed]

Distinction from free and open-source software

Any software is source-available software 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 (For example: Id Software 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).[2]

Free and open-source licenses

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Comparison of free and open-source software licenses

Free software licenses and open-source software licenses are also source-available software licenses, as they both require the source code of the software to be made available.

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.[3]

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

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

GitLab Enterprise Edition License (EE License)

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

GitLab Inc. openly discloses that the EE License makes their Enterprise Edition product "proprietary, closed source code."[11] 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.[12] 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

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: Mega (service) § History

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".[13] 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.[14][15]

Microsoft Shared Source Initiative

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: Shared Source Initiative § Restricted licenses

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),[16] the Microsoft Limited Reciprocal License (Ms-LRL),[17] and the Microsoft Reference Source License (Ms-RSL).[18]

Old Scilab License

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: Scilab § License

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

Server Side Public License

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: Server Side Public License

The Server Side Public License is a modification of the GNU General Public License version 3 created by the MongoDB project. It adds a clause stating that if SSPL-licensed software is incorporated into a "service" offered to other users, the source code for the entirety of the service must be released under the SSPL.[21] The license has been considered non-free by Debian and Red Hat (with software licensed under it therefore banned from their Linux distributions), as well as the Open Source Initiative, as it contains conditions that are unduly discriminatory towards commercial use of the software.[22][23]

SugarCRM Public License

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: SugarCRM § License

In 2007 Michael Tiemann, president of OSI, had criticized[24] 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"[25] 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,[26] and later the GNU Affero GPL version 3 in 2010.[27]

TrueCrypt License

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: TrueCrypt § License and source model

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

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

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.[32]

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

See also

<templatestyles src="Div col/styles.css"/>

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ The Commons Clause doesn't help the commons Matthew Garrett's blog
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Source-available_software&oldid=726488678"