Open-source license

An open-source license is a type of license for computer software and other products that allows the source code, blueprint or design to be used, modified and/or shared under defined terms and conditions.[1][2] This allows end users and commercial companies to review and modify the source code, blueprint or design for their own customization, curiosity or troubleshooting needs. Open-source licensed software is mostly available free of charge, though this does not necessarily have to be the case[3].

Licenses which only permit non-commercial redistribution or modification of the source code for personal use only are generally not considered as open-source licenses[3]. However, open-source licenses may have some restrictions, particularly regarding the expression of respect to the origin of software, such as a requirement to preserve the name of the authors and a copyright statement within the code, or a requirement to redistribute the licensed software only under the same license (as in a copyleft license). One popular set of open-source software licenses are those approved by the Open Source Initiative (OSI) based on their Open Source Definition (OSD).

Comparisons

The Free Software Foundation has related but distinct criteria for evaluating whether or not a license qualifies software as free software. Most free software licenses are also considered open-source software licenses.[4] In the same way, the Debian project has its own criteria, the Debian Free Software Guidelines, on which the Open Source Definition is based. In the interpretation of the FSF, open-source license criteria focus on the availability of the source code and the ability to modify and share it, while free software licenses focuses on the user's freedom to use the program, to modify it, and to share it.[5]

Source-available licenses ensure source code availability, but do not necessarily meet the user freedom criteria to be classified as free software or open-source software.

Public domain
Main article: Public-domain software
See also: Public-domain-equivalent license

Around 2004, lawyer Lawrence Rosen argued in the essay "Why the public domain isn't a license" software could not truly be waived into the public domain and can't therefore be interpreted as very permissive open-source license,[6] a position which faced opposition by Daniel J. Bernstein and others.[7] In 2012, the dispute was finally resolved when Rosen accepted the CC0 as an open-source license, while admitting that contrary to his previous claims, copyright can be waived away, backed by Ninth Circuit decisions.[8]

gollark: Not stored unencrypted on some web service with password protection only.
gollark: No, I mean, generally the actual passwords will be stored locally, encrypted.
gollark: I doubt that would help.
gollark: If you use password autofill stuff in your browser, without a master password of some sort, those are compromised now.
gollark: Just have some fancy onboard robots controlled by you for repair.

See also

References
  1. "Brief Definition of Open Source Licenses". Open Source Initiative. Retrieved April 25, 2013.
  2. Popp, Dr. Karl Michael (2015). Best Practices for commercial use of open source software. Norderstedt, Germany: Books on Demand. ISBN 978-3738619096.
  3. Haumba, Eric Nelson (2018). Open Licensing Models for Strengthening Access to Information: Opportunities for Authors. YMCA Library: Uganda Textbook-Academic and Non-Fiction Authors Association- UTANA. ISBN 9789970428052.
  4. Stallman, Richard (18 November 2016). "Why Open Source misses the point of Free Software". The GNU Project. Retrieved 1 October 2018.
  5. "Relationship between the Free Software movement and Open Source movement", Free Software Foundation, Inc
  6. Lawrence Rosen (2004-05-25). "Why the public domain isn't a license". rosenlaw.com. Retrieved 2016-02-22.
  7. Placing documents into the public domain by Daniel J. Bernstein on cr.yp.to "Most rights can be voluntarily abandoned ("waived") by the owner of the rights. Legislators can go to extra effort to create rights that can't be abandoned, but usually they don't do this. In particular, you can voluntarily abandon your United States copyrights: "It is well settled that rights gained under the Copyright Act may be abandoned. But abandonment of a right must be manifested by some overt act indicating an intention to abandon that right. See Hampton v. Paramount Pictures Corp., 279 F.2d 100, 104 (9th Cir. 1960)."" (2004)
  8. Lawrence Rosen (2012-03-08). "(License-review) (License-discuss) CC0 incompliant with OSD on patents, (was: MXM compared to CC0)". opensource.org. Archived from the original on 2016-03-12. Retrieved 2016-02-22. The case you referenced in your email, Hampton v. Paramount Pictures, 279 F.2d 100 (9th Cir. Cal. 1960), stands for the proposition that, at least in the Ninth Circuit, a person can indeed abandon his copyrights (counter to what I wrote in my article) -- but it takes the equivalent of a manifest license to do so. :-)[...] For the record, I have already voted +1 to approve the CC0 public domain dedication and fallback license as OSD compliant. I admit that I have argued for years against the "public domain" as an open-source license, but in retrospect, considering the minimal risk to developers and users relying on such software and the evident popularity of that "license", I changed my mind. One can't stand in the way of a fire hose of free public domain software, even if it doesn't come with a better FOSS license that I trust more.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.