Free/open

From Things and Stuff Wiki
Revision as of 16:26, 10 August 2023 by Milk (talk | contribs)
Jump to navigation Jump to search


General

a mess. to resort



  • https://en.wikipedia.org/wiki/Copyright_abolition - a movement to abolish copyright, for example by repealing the Statute of Anne and all subsequent law made in its support. The notion of anti-copyright combines a group of ideas and ideologies that advocate changing the current copyright law. It often focuses on the negative philosophical, economic, or social consequences of copyright, and that it has never been a benefit to society, but instead serves to enrich a few at the expense of creativity. Some groups may question the logic of copyright on economic and cultural grounds. The members of this movement are in favor of a full or partial change or repeal of the current copyright law. Copyright and patents are widely rejected among anarchists, communists, socialists, free market libertarians, crypto-anarchists, info-anarchists, and the former Situationist International.

Michele Boldrin and David K. Levine, economists at Washington University in St. Louis, have suggested that copyrights and patents are a net loss for the economy because of the way they reduce competition in the free market. They refer to copyrights and patents as intellectual monopolies, akin to industrial monopolies, and they advocate phasing out and eventually abolishing them. The classic argument in defense of copyright is the view that giving the developers a temporary monopoly over their works encourages further development and creativity, giving the developer a source of income, and thus encourages them to continue their creative work; usually copyright is secured under the Berne Convention, established by Victor Hugo and first adopted in 1886. Every country in the world has copyright laws and private information ownership has not been repealed anywhere officially. Numerous international agreements on copyright have been concluded since then, but copyright law still varies from country to country.


  • https://en.wikipedia.org/wiki/Criticism_of_copyright - or anti-copyright sentiment, is a dissenting view of the current state of copyright law or copyright as a concept. Critics often discuss philosophical, economical, or social rationales of such laws and the laws' implementations, the benefits of which they claim do not justify the policy's costs to society. They advocate for changing the current system, though different groups have different ideas of what that change should be. Some call for remission of the policies to a previous state—copyright once covered few categories of things and had shorter term limits—or they may seek to expand concepts like fair use that allow permissionless copying. Others seek the abolition of copyright itself.

Opposition to copyright is often a portion of platforms advocating for broader social reform. For example, Lawrence Lessig, a free-culture movement speaker, advocates for loosening copyright law as a means of making sharing information easier or addressing the orphan works issue and the Swedish Pirate Party has advocated for limiting copyright to five year terms.




"i don't find these graphical interfaces very clear"


  • https://en.wikipedia.org/wiki/Implied_license - an unwritten license which permits a party (the licensee) to do something that would normally require the express permission of another party (the licensor). Implied licenses may arise by operation of law from actions by the licensor which lead the licensee to believe that it has the necessary permission. Implied licenses often arise where the licensee has purchased a physical embodiment of some intellectual property belonging to the licensor, or has paid for its creation, but has not obtained permission to use the intellectual property.


  • https://en.wikipedia.org/wiki/Public_domain - consists of all the creative work to which no exclusive intellectual property rights apply. Those rights may have expired, been forfeited, expressly waived, or may be inapplicable. Because no one holds the exclusive rights, anyone can legally use or reference those works without permission.


  • https://en.wikipedia.org/wiki/Public-domain-equivalent_license - are licenses that grant public-domain-like rights and/or act as waivers. They are used to make copyrighted works usable by anyone without conditions, while avoiding the complexities of attribution or license compatibility that occur with other licenses.
  • https://en.wikipedia.org/wiki/Public_Domain_Mark - a symbol used to indicate that a work is free of known copyright restrictions and therefore in the public domain. It is analogous to the copyright symbol, which is commonly used to indicate that a work is copyrighted, often as part of a copyright notice. The Public Domain Mark was developed by Creative Commons and is only an indicator of the public domain status of a work – it itself does not release a copyrighted work into the public domain like CC0.



  • https://en.wikipedia.org/wiki/Anti-copyright_notice - a specific statement that is added to a work in order to encourage wide distribution. Such notices are legally required to host such specific media; under the Berne Convention in international copyright law, works are protected even if no copyright statement is attached to them. However, "anti-copyright" statements typically do not take the form of either sophisticated public copyright licenses or a simple dedication to the public domain; instead, they usually just encourage wide distribution. Depending on jurisdiction, it is possible to denounce all claims to copyright in a work including moral rights in a written disclaimer. An example of an anti-copyright notice is the following: "Anti-Copyright! Reprint freely, in any manner desired, even without naming the source." Where such notices are attached depends highly on the type of work. They are often found in anarcho-socialist magazines and books. A copyright waiver might[clarification needed] state the following: The author of this work hereby waives all claim of copyright (economic and moral) in this work and immediately places it in the public domain; it may be used, distorted or destroyed in any manner whatsoever without further attribution or notice to the creator.




  • https://en.wikipedia.org/wiki/Public_copyright_license - or public copyright licenses is a license by which a copyright holder as licensor can grant additional copyright permissions to any and all persons in the general public as licensees. By applying a public license to a work, provided that the licensees obey the terms and conditions of the license, copyright holders give permission for others to copy or change their work in ways that would otherwise infringe copyright law.



  • https://en.wikipedia.org/wiki/Free_software_movement - a social movement with the goal of obtaining and guaranteeing certain freedoms for software users, namely the freedoms to run, study, modify, and share copies of software. Software which meets these requirements, The Four Essential Freedoms of Free Software, is termed free software.

Although drawing on traditions and philosophies among members of the 1970s hacker culture and academia, Richard Stallman formally founded the movement in 1983 by launching the GNU Project. Stallman later established the Free Software Foundation in 1985 to support the movement.


  • https://en.wikipedia.org/wiki/Free_Software_Foundation - a 501(c)(3) non-profit organization founded by Richard Stallman on October 4, 1985, to support the free software movement, with the organization's preference for software being distributed under copyleft ("share alike") terms, such as with its own GNU General Public License. The FSF was incorporated in Boston, Massachusetts, US, where it is also based. From its founding until the mid-1990s, FSF's funds were mostly used to employ software developers to write free software for the GNU Project. Since the mid-1990s, the FSF's employees and volunteers have mostly worked on legal and structural issues for the free software movement and the free software community.

Consistent with its goals, the FSF aims to use only free software on its own computers.


  • https://en.wikipedia.org/wiki/The_Free_Software_Definition - written by Richard Stallman and published by the Free Software Foundation (FSF), defines free software as being software that ensures that the end users have freedom in using, studying, sharing and modifying that software. The term "free" is used in the sense of "free speech," not of "free of charge." The earliest-known publication of the definition was in the February 1986 edition of the now-discontinued GNU's Bulletin publication by the FSF. The canonical source for the document is in the philosophy section of the GNU Project website. As of April 2008, it is published in 39 languages. The FSF publishes a list of licences which meet this definition.


  • https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses - This comparison only covers software licenses which have a linked Wikipedia article for details and which are approved by at least one of the following expert groups: the Free Software Foundation, the Open Source Initiative, the Debian Project and the Fedora Project. For a list of licenses not specifically intended for software, see List of free-content licences.






  • https://en.wikipedia.org/wiki/Open_Publication_License - was published by the Open Content Project in 1999 as a public copyright license for documents. It superseded the Open Content License, which was published by the Open Content Project in 1998. Starting around 2002-2003, it began to be superseded, in turn, by the Creative Commons licenses.
  • https://en.wikipedia.org/wiki/Open_Content_Project - was a project dedicated to free culture and Creative Commons. One goal was to evangelize the concept of open content. The project's Open Publication License, primarily designed and offered for academics, could easily be adapted to the needs of the artist or other content provider. The Open Content Project has closed in 2003 and has been succeeded by Creative Commons.


  • https://en.wikipedia.org/wiki/The_Open_Definition - a document published by the Open Knowledge Foundation (OKF) (previously Open Knowledge International) to define openness in relation to data and content. It specifies what licences for such material may and may not stipulate, in order to be considered open licences. The definition itself was derived from the Open Source Definition for software. OKI summarise the document as: Open means anyone can freely access, use, modify, and share for any purpose (subject, at most, to requirements that preserve provenance and openness).

The latest form of the document, published in November 2015, is version 2.1. The use of language in the document is conformant with RFC 2119.



  • https://en.wikipedia.org/wiki/Free_content - libre content, libre information, or free information, is any kind of functional work, work of art, or other creative content that meets the definition of a free cultural work.








The organization was founded in late February 1998 by Bruce Perens and Eric S. Raymond, part of a group inspired by the Netscape Communications Corporation publishing the source code for its flagship Netscape Communicator product. Later, in August 1998, the organization added a board of directors.



  • https://en.wikipedia.org/wiki/Participatory_culture - an opposing concept to consumer culture — in other words a culture in which private individuals (the public) do not act as consumers only, but also as contributors or producers (prosumers). The term is most often applied to the production or creation of some type of published media. Recent advances in technologies (mostly personal computers and the Internet) have enabled private persons to create and publish such media, usually through the Internet. Since the technology now enables new forms of expression and engagement in public discourse, participatory culture not only supports individual creation but also informal relationships that pair novices with experts. This new culture as it relates to the Internet has been described as Web 2.0. In participatory culture "young people creatively respond to a plethora of electronic signals and cultural commodities in ways that surprise their makers, finding meanings and identities never meant to be there and defying simple nostrums that bewail the manipulation or passivity of "consumers."



  • https://en.wikipedia.org/wiki/Open-source_model - a decentralized software development model that encourages open collaboration. A main principle of open-source software development is peer production, with products such as source code, blueprints, and documentation freely available to the public. The open-source movement in software began as a response to the limitations of proprietary code. The model is used for projects such as in open-source appropriate technology, and open-source drug discovery. Open source promotes universal access via an open-source or free license to a product's design or blueprint, and universal redistribution of that design or blueprint. Before the phrase open source became widely adopted, developers and producers used a variety of other terms. Open source gained hold with the rise of the Internet. The open-source software movement arose to clarify copyright, licensing, domain, and consumer issues.Generally, open source refers to a computer program in which the source code is available to the general public for use or modification from its original design. Open-source code is meant to be a collaborative effort, where programmers improve upon the source code and share the changes within the community. Code is released under the terms of a software license. Depending on the license terms, others may then download, modify, and publish their version (fork) back to the community.



Fields


Standards



  • Open Standards principles - GOV.UK - Open Standards are one of the most powerful tools we have to open up government. They make it possible for the smallest supplier to compete with the largest. They make data open for any citizen to audit. They unlock the transformative power of open source software. This version of the Open Standards Principles builds on the version originally published in 2012 and revised in 2015. They underscore our commitment to digital modernisation and increased accessibility. With these principles in place, we are on-course to recognise the massive efficiency gains of web-scale technologies. We have accomplished so much with open standards. Huge transformational programmes such as Verify, Pay, and the GOV.UK website are all backed by mature and scalable open standards. We are improving the way documents are generated, edited, and stored by adopting the Open Document Format (ODF). We continue to drive the development of open standards by working with industry and academia and becoming members of standards development organisations like the World Wide Web Consortium (W3C).


Software


  • Software Freedom Conservancy - Software Freedom Conservancy is a not-for-profit charity that helps promote, improve, develop, and defend Free, Libre, and Open Source Software (FLOSS) projects. Conservancy provides a non-profit home and infrastructure for FLOSS projects. This allows FLOSS developers to focus on what they do best — writing and improving FLOSS for the general public — while Conservancy takes care of the projects' needs that do not relate directly to software development and documentation.


  • switching.software - Ethical, easy-to-use and privacy-conscious alternatives to well-known software
  • Open Source Guides - Open source software is made by people just like you. Learn how to launch and grow your project.





  • https://github.com/fossology/fossology - FOSSology is an open source license compliance software system and toolkit. As a toolkit you can run license, copyright and export control scans from the command line. As a system, a database and web ui are provided to give you a compliance workflow. License, copyright and export scanners are tools used in the workflow.


  • https://en.wikipedia.org/wiki/License_proliferation - the phenomenon of an abundance of already existing and the continued creation of new software licenses for software and software packages in the FOSS ecosystem. License proliferation affects the whole FOSS ecosystem negatively by the burden of increasingly complex license selection, license interaction, and license compatibility considerations.









  • OpenHatch - a non-profit dedicated to matching prospective free software contributors with communities, tools, and education.



  • https://en.wikipedia.org/wiki/Multi-licensing - the practice of distributing software under two or more different sets of terms and conditions. This may mean multiple different software licenses or sets of licenses. Prefixes may be used to indicate the number of licenses used, e.g. dual-licensed for software licensed under two different licenses. Multi-licensing is commonly done to support free software business models in a commercial environment. In this scenario, one option is a proprietary software license, which allows the possibility of creating proprietary applications derived from it, while the other license is a copyleft free software/open-source license, thus requiring any derived work to be released under the same license. The copyright holder of the software then typically provides the free version of the software at little or no cost, and profits by selling proprietary licenses to commercial operations looking to incorporate the software into their own business. This model can be compared to shareware.


  • Dual Licensing - Dual licensing is a business model for creative work covered by copyright. In software, dual licensing means giving everyone free permission to use the software in some ways while selling permission to use it in others. For example, a developer might allow noncommercial use of their software for free while charging for commercial use. Or they may allow use of their work in free, open projects while charing for use in closed, proprietary ones. Dual licensing is sometimes called “selling exceptions”. The license terms for free use are “the rule”. Paid permissions to break that rule are the “exceptions”.


Guides


Articles





Agreements



  • https://en.wikipedia.org/wiki/Project_Harmony_(FOSS_group) - an initiative by Canonical Ltd. about contributor agreements for Open Source software. The aim of the Harmony project is to develop templates of Contributor License Agreements for use by Free and open source software (FOSS) projects. The Canonical initiative was announced in June 2010 by Amanda Brock, General Counsel at Canonical. In July 2011, the project released version 1.0 of its agreements templates. Following this release, the project was seen by some as an important step for intellectual property and copyright management for open Source software, and by some others as "Making an exception (ie copyright aggregation) the norm". The project proposes two types of options for the Contributor License Agreements: Copyright License: The contributors retain the copyright to their contribution. Copyright Assignment: The contributors transfer the copyright of their contribution to the project.



  • Contributor Agreements - The Next Generation - The goal of contributoragreements.org is to develop the legal and technical infrastructure that will enable open source collaborative projects to receive, use, and share in-kind contributions from participants while eliminating or minimizing the legal risk therefrom to the projects and those who depend on them. Easy to use template agreements mean less friction (transaction cost) and more time to create. In order to achieve this goal, contributoragreements.org was established as a platform to deepen the discussion around the practices and legal questions for contributor agreements, and to provide additional generic information relevant for any legal strategy considered by open collaborative projects. A summary of our thoughts and suggestions can be found at SCRIPTed 2013 Volume 10 Issue 2. We realize that contributor agreements are one available tool out of many in an overall legal strategy for open collaborative projects, and we don’t intend to suggest that contributor agreements are necessary for all successful legal strategies. Rather, we hope to assist projects and organizations that have decided to use contributor agreements by providing a new generation of standardized terms, adaptable and easy to use for established and emerging projects in order to avoid friction and transaction costs. Through this platform we propose to explore in more detail how to make such contributor agreements suitable for multiple jurisdictions and how to offer an efficient system to mediate and move rights between contributors (developers and creators), projects, and end-users.


  • Don't sign a CLA - So to you, the contributor: if you are contributing to open source and you want it to stay that way, you should not sign a CLA. When you send a patch to a project, you are affording them the same rights they afforded you. The relationship is one of equals. This is a healthy balance. When you sign a CLA, you give them unequal power over you. If you’re scratching an itch and just want to submit the patch in good faith, it’s easy enough to fork the project and put up your changes in a separate place. This is a right afforded to you by every open source license, and it’s easy to do. Anyone who wants to use your work can apply your patches on top of the upstream software. Don’t sign away your rights!




  • https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin - DCO) is a statement that a software developer agrees to, saying that "the contributor is allowed to make the contribution and that the project has the right to distribute it under its license." It was introduced in 2004 by the Linux Foundation, to enhance the submission process for software used in the Linux kernel, shortly after the SCO–Linux disputes. DCOs are often used as an alternative to a Contributor License Agreement (CLA). Instead of a signed legal contract, a DCO is an affirmation that the source code being submitted originated from the developer, or that the developer has permission to submit the code. Proponents of the DCO contend that it reduces the barriers of entry introduced by a CLA.



Hardware



  • https://en.wikipedia.org/wiki/Free_and_Open_Source_Silicon_Foundation - a non-profit foundation with the mission to promote and assist free and open digital hardware designs and their related ecosystems. It was set up by the core OpenRISC development team in response to decreasing support from the commercial owners of the opencores.org website. The main sponsor of the FOSSi Foundation is Google and past sponsors included Cadence Design Systems and Embecosm. The FOSSi Foundation should not be confused with the Free Silicon Foundation.





Content


Licenses

  • https://en.wikipedia.org/wiki/License_compatibility - a legal framework that allows for pieces of software with different software licenses to be distributed together. The need for such a framework arises because the different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program.[failed verification] Proprietary licenses are generally program-specific and incompatible; authors must negotiate to combine code. Copyleft licenses are commonly deliberately incompatible with proprietary licenses, in order to prevent copyleft software from being re-licensed under a proprietary license, turning it into proprietary software. Many copyleft licenses explicitly allow relicensing under some other copyleft licenses. Permissive licenses are (with minor exceptions) compatible with everything, including proprietary licenses; there is thus no guarantee that all derived works will remain under a permissive license.


  • TLDRLegal - Lookup popular software licenses summarized at-a-glance.


  • SPDX License List | Software Package Data Exchange (SPDX) - a list of commonly found licenses and exceptions used in free and open source and other collaborative software or documentation. The purpose of the SPDX License List is to enable easy and efficient identification of such licenses and exceptions in an SPDX document, in source files or elsewhere. The SPDX License List includes a standardized short identifier, full name, vetted license text including matching guidelines markup as appropriate, and a canonical permanent URL for each license and exception.


  • https://en.wikipedia.org/wiki/Rights_Expression_Language - or REL is a machine-processable language used to express intellectual property rights (such as copyright) and other terms and conditions for use over content. RELs can be used as standalone expressions (i.e. metadata usable for search, compatibility tracking) or within a DRM system.

RELs are expressible in a machine-language (such as XML, RDF , RDF Schema, and JSON). Although RELs may be processed directly, they can also be encountered when embedded as metadata within other documents, such as eBooks, image, audio or video files.



  • LibrePlanet - an organizing space for everyone in the free software and free culture movements to collaborate around their own needs and concerns. LibrePlanet will work to provide the necessary infrastructure, tools, and resources to help free software proponents amplify their advocacy.




  • Fast Path - Complete this form create a ZIP archive with an order form template and legal terms for a commercial software license agreement.





  • The CRAPL - An academic-strength open source license. An open source license for academics has additional needs: (1) it should require that source and modifications used to validate scientific claims be released with those claims; and (2) more importantly, it should absolve authors of shame, embarrassment and ridicule for ugly code.






Artistic License



Mixed

Creative Commons





Permissive

BSD

  • https://en.wikipedia.org/wiki/BSD_licenses - are a family of permissive free software licenses, imposing minimal restrictions on the use and distribution of covered software. This is in contrast to copyleft licenses, which have share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. The original version has since been revised, and its descendants are referred to as modified BSD licenses.

BSD is both a license and a class of license (generally referred to as BSD-like). The modified BSD license (in wide use today) is very similar to the license originally used for the BSD version of Unix. The BSD license is a simple license that merely requires that all code retain the BSD license notice if redistributed in source code format, or reproduce the notice if redistributed in binary format. The BSD license (unlike some other licenses e.g. GPL) does not require that source code be distributed at all.



FDL

License The license is very similar to the 2-clause Simplified BSD License used by the support of FreeBSD, however, it makes the applications of "source code" and "compile" less obscure in the context of documentation. It also includes an obligatory disclaimer about IEEE and Open Group manuscript in some old-fashioned sheets.


MIT





University of Illinois/NCSA Open Source License / UIUC


ISC

  • https://en.wikipedia.org/wiki/ISC_license - a permissive free software license published by the Internet Software Consortium, now called Internet Systems Consortium (ISC). It is functionally equivalent to the simplified BSD and MIT licenses, but without language deemed unnecessary following the Berne Convention.[nb 1][nb 2]



zlib


Apache Software Foundation

  • Apache Software Foundation Licenses - various licenses to distribute software and documentation, and to accept regular contributions from individuals and corporations and larger grants of existing software products. These licenses help us achieve our goal of providing reliable and long-lived software products through collaborative, open-source software development. In all cases, contributors retain full rights to use their original contributions for any other purpose outside of Apache while providing the ASF and its projects the right to distribute and build upon their work within Apache.


  • https://en.wikipedia.org/wiki/Apache_License - a permissive free software license written by the Apache Software Foundation (ASF). It allows users to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software under the terms of the license, without concern for royalties. The ASF and its projects release their software products under the Apache License. The license is also used by many non-ASF projects.

Educational Community License

  • https://en.wikipedia.org/wiki/Educational_Community_License - ECL version 2.0 was approved by the Open Source Initiative in the Summer of 2007, and the Free Software Foundation lists it as being a "GPL-Compatible Free Software License" that is compatible with version 3 of the GNU General Public License but not compatible with GPLv2. This means that a software developer can mix code from an ECLv2 licensed project and a GPLv3 licensed project but, due to license terms incompatibility, they are not allowed to mix code from an ECLv2 project and a GPLv2 project. EDUCAUSE (Ref 2 below) says of the ECL, "It is essentially the Apache 2.0 license with a modification of the patent language to make it workable for many colleges and universities."


Copyleft

  • https://en.wikipedia.org/wiki/Copyleft - the legal technique of granting certain freedoms over copies of copyrighted works with the requirement that the same rights be preserved in derivative works. In this sense, freedoms refers to the use of the work for any purpose, and the ability to modify, copy, share, and redistribute the work, with or without a fee. Licenses which implement copyleft can be used to maintain copyright conditions for works ranging from computer software, to documents, art, scientific discoveries and even certain patents. Copyleft software licenses are considered protective or reciprocal in contrast with permissive free software licenses, and require that information necessary for reproducing and modifying the work must be made available to recipients of the software program, which are often distributed as executables. This information is most commonly in the form of source code files, which usually contain a copy of the license terms and acknowledge the authors of the code. Notable copyleft licenses include the GNU General Public License (GPL), originally written by Richard Stallman, which was the first software copyleft license to see extensive use, the Mozilla Public License, the Free Art License, and the Creative Commons share-alike license condition, with the last two being intended for other types of works, such as documents and pictures, both academic or artistic in nature.


  • https://en.wikipedia.org/wiki/Share-alike - a copyright licensing term, originally used by the Creative Commons project, to describe works or licenses that require copies or adaptations of the work to be released under the same or similar license as the original. Copyleft licenses are free content or free software licenses with a share-alike condition.



  • Essays and Articles - GNU Project - Free Software Foundation - Free software is a matter of freedom: people should be free to use software in all the ways that are socially useful. Software differs from material objects—such as chairs, sandwiches, and gasoline—in that it can be copied and changed much more easily. These possibilities make software as useful as it is; we believe software users should be able to make use of them.


  • Copyleft Compliance Projects - Software Freedom Conservancy - As existing donors and sustainers know, the Software Freedom Conservancy is a 501(c)(3) non-profit charity registered in New York, and Conservancy helps people take control of their computing by growing the software freedom movement, supporting community-driven alternatives to proprietary software, and defending free software with practical initiatives. Conservancy accomplishes these goals with various initiatives, including defending and upholding the rights of software users and consumers under copyleft licenses, such as the GPL.




https://wiki.debian.org/DFSGLicenses




GPL





AGPL


  • Why the GNU Affero GPL - GNU Project - Free Software Foundation - The GNU Affero General Public License is a modified version of the ordinary GNU GPL version 3. It has one added requirement: if you run a modified program on a server and let other users communicate with it there, your server must also allow them to download the source code corresponding to the modified version running there.



Sleepycat

Free Art License

Mozilla Public License / MPL

  • About MPL 2.0: Revision Process and Changes FAQ — Mozilla - MPL 2.0 was drafted over a period of 21 months in a public process that included extensive feedback from a variety of people, including MPL users, lawyers, and open source community groups like the Free Software Foundation and Open Source Initiative.

Common Public License / CPL

  • https://en.wikipedia.org/wiki/Common_Public_License - a free software / open-source software license published by IBM. The Free Software Foundation and Open Source Initiative have approved the license terms of the CPL. The CPL has the stated aims of supporting and encouraging collaborative open-source development while still retaining the ability to use the CPL'd content with software licensed under other licenses, including many proprietary licenses. The Eclipse Public License (EPL) consists of a slightly modified version of the CPL.

The CPL has some terms that resemble those of the GNU General Public License (GPL), but some key differences exist. A similarity relates to distribution of a modified computer program: under either license (CPL or GPL), one must make the source code of a modified program available to others. CPL, like the GNU Lesser General Public License, allows non-CPL-licensed software to link to a library under CPL without requiring the linked source code to be made available to the licensee. CPL lacks compatibility with both versions of the GPL because it has a "choice of law" section in section 7, which restricts legal disputes to a certain court. Another source of incompatibility is the differing copyleft requirements.

Eclipse Public License / EPL

  • https://en.wikipedia.org/wiki/Eclipse_Public_License - a free and open source software license most notably used for the Eclipse IDE and other projects by the Eclipse Foundation. It replaces the Common Public License (CPL) and removes certain terms relating to litigations related to patents. The Eclipse Public License is designed to be a business-friendly free software license, and features weaker copyleft provisions than licenses such as the GNU General Public License (GPL). The receiver of EPL-licensed programs can use, modify, copy and distribute the work and modified versions, in some cases being obligated to release their own changes.


Common Development and Distribution License / CDDA

  • https://en.wikipedia.org/wiki/Common_Development_and_Distribution_License - a free and open-source software license, produced by Sun Microsystems, based on the Mozilla Public License (MPL). Files licensed under the CDDL can be combined with files licensed under other licenses, whether open source or proprietary. In 2005 the Open Source Initiative approved the license. The Free Software Foundation (FSF) considers it a free software license, but one which is incompatible with the GNU General Public License (GPL).

Terms

Derived from the Mozilla Public License 1.1, the CDDL tries to address some of the problems of the MPL. Like the MPL, the CDDL is a weak copyleft license in-between GPL license and BSD/MIT permissive licenses, requiring only source code files under CDDL to remain under CDDL. Unlike strong copyleft licenses like the GPL, mixing of CDDL licensed source code files with source code files under other licenses is permitted without relicensing. The resulting compiled software product ("binary") can be licensed and sold under a different license, as long as the source code is still available under CDDL, which should enable more commercial business cases, according to Sun. Like the MPL the CDDL includes a patent grant to the licensee from all contributors ("patent peace"). However, in section 2.1(d), the patent grant is lost if the code implementing a patented feature is modified.


GNU Free Documentation License / GFDL

  • https://en.wikipedia.org/wiki/GNU_Free_Documentation_License - GNU FDL or simply GFDL) is a copyleft license for free documentation, designed by the Free Software Foundation (FSF) for the GNU Project. It is similar to the GNU General Public License, giving readers the rights to copy, redistribute, and modify (except for "invariant sections") a work and requires all copies and derivatives to be available under the same license. Copies may also be sold commercially, but, if produced in larger quantities (greater than 100), the original document or source code must be made available to the work's recipient. The GFDL was designed for manuals, textbooks, other reference and instructional materials, and documentation which often accompanies GNU software. However, it can be used for any text-based work, regardless of subject matter. For example, the free online encyclopedia Wikipedia uses the GFDL (coupled with the Creative Commons Attribution Share-Alike License) for much of its text, excluding text that was imported from other sources after the 2009 licensing update that is only available under the Creative Commons license.


GNU Simpler Free Documentation License / GSFDL


Extreme copyleft

  • The Copyleft Bust Up — /dev/lawyer - "The two great camps of copyleft developers—software freedom activists and competitive upstarts—have split apart again. Upstarts can no longer achieve their goals with activist copyleft licenses. Activists don’t inhabit the same computing universe, or feel the same pain. So upstart copyleft developers are writing new licenses for themselves, on their own." [10]




  • Cooperative Technology - "We believe a significant reason for the failures of both "free software" and "open source" to prevent this cooptation is that the men who coined and initially promoted these terms did not and do not critique capitalism. Richard Stallman has generally dodged the question of whether free software is opposed to capitalism. In the historical context of the United States in the 1980s, that may have been a wise decision. But that was then, and now it is 2021. The promoters of "open source" emphasize its compatibility with capitalism and go out of their way to distance "open source" from critiques of capitalism. To effectively resist cooptation and expand our movement, we believe we need to build on the FOSS movement with an explicitly anticapitalist political movement which proactively collaborates with other movements for justice.

"We believe the focus of the cooperative technology movement should be on the practical impacts that the use of technology has on humans and the universe we inhabit. The scope of this extends beyond humans and must consider the environment around us. Moreover, we believe it is counterproductive to have a small self-appointed group of privileged men determine what our movement's terminology, goals, and tactics are. We encourage anyone interested in building a better world through technology to engage in discussions with your own communities about what you want "cooperative technology" to mean.

"While we agree with the Ethical Software Movement that we must resist when our efforts are coopted for unjust purposes, we reject putting restrictions on the ways people may use software through copyright licenses as a wise tactic for achieving our goals. The history of the Free and Open Source Software movement has shown that the proliferation of incompatible copyright licenses which prohibit software from being legally combined creates more obstacles than opportunities for our movement. Any new copyright licenses for use with cooperative software must be written with this consideration in mind to intentionally avoid fracturing the software ecosystem. Adopting incompatible copyright licenses for different software would make it easy for our adversaries to divide and suppress the movement."



SSPL

  • https://en.wikipedia.org/wiki/Server_Side_Public_License - a source-available software license introduced by MongoDB Inc. in 2018. It includes most of the text and provisions of the GNU Affero General Public License version 3 (AGPL v3), and primarily replaces section 13 "Remote Network Interaction; Use with the GNU General Public License." with a new section that requires that anyone who offers the functionality of SSPL-licensed software to third-parties as a service must release the entirety of their source code, including all software, APIs, and other software that would be required for a user to run an instance of the service themselves, under the SSPL. In contrast, the AGPL v3's section 13 covers only the program itself (the copyrightable work licensed under AGPL v3).

The SSPL is not recognized as free software by multiple parties, including the Open Source Initiative (OSI) and multiple major Linux vendors, as the aforementioned provision is discriminatory towards specific fields of use.



  • Cooperative Technology - We believe a significant reason for the failures of both "free software" and "open source" to prevent this cooptation is that the men who coined and initially promoted these terms did not and do not critique capitalism. Richard Stallman has generally dodged the question of whether free software is opposed to capitalism. In the historical context of the United States in the 1980s, that may have been a wise decision. But that was then, and now it is 2021. The promoters of "open source" emphasize its compatibility with capitalism and go out of their way to distance "open source" from critiques of capitalism. To effectively resist cooptation and expand our movement, we believe we need to build on the FOSS movement with an explicitly anticapitalist political movement which proactively collaborates with other movements for justice. We propose the term "cooperative technology" for this movement. By "cooperative technology", we mean technology that is constructed by and for the people whose lives are affected by its use. While this builds on the Free and Open Source Software movement, we aim to apply the same principles to hardware as well, although the criteria by which we evaluate hardware and software will of course not be identical. It is not sufficient to narrowly focus on the people who directly interact with computers. Cooperative software which is run on a server should not be controlled solely by the administrator of the server, but also by the people who interact with the server over a network. Similarly, the data generated by the technology and the data which it requires to function should be in the control of the people who are affected by the technology. Cooperative software that uses cameras should not be controlled solely by the people who own the cameras, but also the people who are observed by the cameras. Cooperative electronic medical record systems should not be designed for the interests of insurance companies or hospital administrators, but for the interests of patients and the clinicians who directly use it.


Cross License Collaborative Agreement

  • Cross License Collaborative - These terms enable contributors working together on a project covered by copyrights or patents to make collective decisions about licensing their project as a whole.


Cooperative Source License


Parity Public License

Prosperity Public License

CC4r

Cooperative Non-Violent Public License / CNPL

Nonviolent Public License / NPL

  • NVPL - Nonviolent Public License
  • CNPL - Cooperative Nonviolent Public License
  • NVPL-NA - Nonviolent Public License No Attributions
  • CNPL-NA - Cooperative Nonviolent Public License No Attributions



Peace Public License / PPL


Anti-Capitalist Software License / ACSL

  • The Anti-Capitalist Software License - a software license towards a world beyond capitalism. This license exists to release software that empowers individuals, collectives, worker-owned cooperatives, and nonprofits, while denying usage to those that exploit labor for profit. How is the Anti-Capitalist Software License different from other licenses? Most existing licenses, including free and open source licenses, consider qualities like source code availability, ease of use, commercialization, and attribution, none of which speak directly to the conditions under which the software is written. Instead, the ACSL considers the organization licensing the software, how they operate in the world, and how the people involved relate to one another. [11]


to sort









  • Open Standards for Data Guidebook - Open standards for data are reusable agreements that make it easier for people and organisations to publish, access, share and use better quality data.This guidebook helps people and organisations create, develop and adopt open standards for data.It supports a variety of users, including policy leads, domain experts and technologists.




  • Blue Oak Model License 1.0.0 - demonstrates all the techniques that licenses can use to make software free and simple for everyone to use and build on, in everyday language that everyone can understand.



  • https://wiki.p2pfoundation.net/Copyfarleft - based on a critique of the approach by Creative Commons and other Copyleft approaches.A more recent development along similar lines is Copyfair. Copyfarleft is specifically limited to worker-owned entities and cooperatives, which some may find restrictive. So Copyfair addresses more generically the relations between commons communities and the market entities working with them, expecting reciprocity in exchange for commercial rights (note from Michel Bauwens)"The main argument advanced in the essay is that artists can not earn a living from exclusivity of "intellectual property" and that that neither copyleft licenses like the GPL, nor "copyjustright" frameworks such as the creative commons, can help."


  • Copyfair - P2P Foundation - an evolution of the Copyfarleft concept. Michel Bauwens: "The Copyfair is a principle which aims to re-introduce reciprocity requirements in market activities it aims to preserve the right of sharing knowledge without conditions but aims to subject commercialization of any such knowledge commons to some form of contribution to that commons. So the aim is to create 'ethical' entrepreneurial coalitions, consisting in preference in 'generative' entities such as cooperatives, solidarity economy entities, social entrepreneurship or any not-for-profit mission-oriented or purpose driven entity, which constitutes itself around a knowledge commons (mutualization of productive knowledge), and contribute to this commons to which they are all co-dependent."


  • https://wiki.p2pfoundation.net/Peer_Production_License - The peer production license is an example of the Copyfair type of license, in which only other commoners, cooperatives and nonprofits can share and re-use the material, but not commercial entities intent on making profit through the commons without explicit reciprocity. This fork on the original text of the Creative Commons non-commercial variant makes the PPL an explicitly anti-capitalist version of the CC-NC. It only allows commercial exploitation by collectives in which the ownership of the means of production is in the hands of the value creators, and where any surplus is distributed equally among them (and not only into the hands of owners, shareholders or absentee speculators). According to Dmytri Kleiner, co-author of the license with the barrister John Magyar, it’s not a copyleft license, but instead copyFARleft, and is intended for consumer goods or commodities rather than capital or producers’ goods.


Open Data Commons


Free

  • https://github.com/44bits/awesome-opensource-documents - This is not a list of free programming books. This is a curated list of open source or open source licensed documents, guides, and books which can be read, used, modified, translated, redistributed and even rewritten under their same license.


=== to sort ---

  • https://en.wikipedia.org/wiki/Piratbyr%C3%A5n#Kopimi - was a Swedish think tank established to support the free sharing of information, culture, and intellectual property. Piratbyrån provided a counterpoint to lobby groups such as the Swedish Anti-Piracy Bureau.

In 2005 Piratbyrån released an anthology entitled Copy Me, containing selected texts previously available from its website. Members of Piratbyrån participated in debates on Swedish Radio and Swedish Television and also gave several lectures in other European countries, such as at the 2005 22nd Chaos Communication Congress in Berlin. Piratbyrån's activities might have changed over the years, partly as a result of the addition of the Pirate Party to the Swedish political scene. During Walpurgis Night 2007, Piratbyrån burned all of their remaining copies of Copy Me in a ritual-like performance, declaring: The file-sharing debate is hereby buried. When we talk about file-sharing from now on it's as one of many ways to copy. We talk about better and worse ways of indexing, archiving and copying—not whether copying is right or wrong. Winter is pouring down the hillside. Make way for spring!

Unlicense

WTFPL


to sort

Commons Clause License

  • Commons Clause License - Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software.


DRM

Retrieved from "https://wiki.thingsandstuff.org/index.php?title=Free/open&oldid=61723"