Files @ ae418023e0c5
Branch filter:

Location: website/www/conservancy/static/copyleft-compliance/glossary.html - annotation

Daniel Pono Takamori
add glossary and fixing Public Filings link
{% extends "base_compliance.html" %}
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
{% block submenuselection %}EnforcementStrategy{% endblock %}
{% block content %}

<h1 id="glossary">Glossary of terms</h1>

<h3 id="auditability">auditability</h3>
<p>Ability to inspect the exact software running on a device. This includes version information, modifications and licensing information. </p>

<h3 id="bash">Bash</h3>
A very common utility for Linux-based systems. Bash was originally released under the General Public License version 2 (GPLv2), but newer versions of Bash are under version 3 (GPLv3). Descendants of both versions are utilized in the industry.

<h3 id="ccs">Complete Corresponding Source (CCS)</h3>
<p>“Informally, <acronym title="Complete Corresponding Source">CCS</acronym> is all of the technical materials and source code required to modify, run, and/or reinstall the software. The <acronym title="General Public License">GPL</acronym> and <acronym title="Lesser General Public License">LGPL</acronym> have a formal definitions for <acronym title="Complete Corresponding Source">CCS</acronym>, which is sometimes called "Corresponding Source."</p>

<h3 id="copyleft">copyleft / copyleft licensing</h3>
<p>A kind of software licensing that leverages the restrictions of copyright, but with the intent to promote sharing (using copyright licensing to freely use and repair software). Software programs are copylefted when they utilize software with a copyleft license. These copyleft licenses are unique in that they seek to put large corporations, small companies, consumers, and hobbyists all on equal footing. The intention is for this to be achieved by granting everyone the exact same rights, permissions, and privileges to modify, improve, and/or include the software in their products.</p>

<h3 id="compliance">copyleft compliance</h3>
<p>When companies utilize copylefted software, they thereby agree to the terms associated with its use. By utilizing copylefted software when designing products, companies agreed to these terms, and so have both contractual and copyright obligations to take certain actions to ensure others have the same rights they did with regard to the software. When rights are respected, the sharing of software under copyleft licensing is a mutually beneficial approach, but many companies are not holding up their side of the bargain. A company is in compliance when it ensures that all of its customers have the same rights, permission, and ability that it has to improve that software and install their improvements onto a device. The best way a company can demonstrate its intent to be in full compliance is by creating a vibrant third-party marketplace for improved software.</p>

<h3 id="end-users">end user</h3>
<p>An end user is someone who winds up using the software. In the case of TVs, an end user is simply the person who uses the TV. (See also third-party beneficiaries of the <acronym title="General Public License">GPL</acronym>)</p>

<h3 id="ethical-technology">ethical technology</h3>
<p>Technology that serves its users, rather than the corporations who profit from it. Ethical technology preserves and promotes the rights of those impacted by it. </p>

<h3 id="foss">FOSS</h3>
<p>Acronym for free and open source software (FOSS). See software freedom.</p>

<h3 id="foss-commons">FOSS commons</h3>
<p>The Digital Library of the Commons defines “commons” as “a general term for shared resources in which each stakeholder has an equal interest”. The FOSS commons refers to a commons for free and open source software (FOSS). See also software freedom.</p>

<h3 id="firmware">firmware</h3>
<p>Software on embedded devices that is written for the purpose of operating the specific hardware of that device.</p>

<h3 id="tar">GNU tar</h3>
<p>A copylefted program for storing large groups of files inside another file. Incredibly common and used ubiquitously. </p>

<h3 id="gpl">General Public License (GPL) </h3>
<p>A copyleft license that ensures end users the freedom to run, study, share, and modify the software. Often referred to as “the GPL.” Also known as GNU General Public License (GPL).</p>

<h3 id="gpl-software">GPL’d software</h3>
<p>Software that has been released under the terms of the <acronym title="General Public License">GPL</acronym>.</p>

<h3 id="right-to-repair">right-to-repair software</h3>
<p>The ability to repair the software on your device in the same way you can repair the physical aspects of your tools. Software Freedom Conservancy asserts that this right is overlooked and needs additional legal protections (as the <acronym title="Federal Trade Commission">FTC</acronym> has agreed with) to protect consumers. Software Freedom Conservancy focuses specifically on the right to software repair; other great organizations like the Repair Association focus on the right to hardware repair. The two rights go hand-in-hand in our modern world where nearly all electronic devices also have small computers inside them.</p>

<h3 id="samygo">SamyGo project</h3>
<p>A software project designed to improve the functionality of the software on Samsung TVs. </p>

<h3 id="software">software (vs hardware)</h3>
<p>An analogy is that ingredients and tools for cooking are hardware and the recipe is software. Both the physical components (computers, phones, TVs) and the ideas (software, programs, algorithms) are necessary.</p>

<h3 id="devices">software-based electronics devices</h3>
<p>Devices like pacemakers have all the necessary hardware to beat your heart, but need the software to do it safely in a way that makes it useful. More and more devices are defined by their software, rather than the hardware (sensors, motors, radio, etc). </p>

<h3 id="software-freedom">software freedom</h3>
<p>The freedom of a user to run, study, (re)distribute, and (re)install (modified) versions of a piece of software. More generally, it is the idea that we are entitled to rights when using software and there should be equal protections for privacy and redistribution. The rights should treat everyone equally—big businesses and individual consumers and users alike.</p>

<h3 id="source-code">source code</h3>
<p>The human readable code written by people that gets turned into binary code that only a computer can understand. </p>

<h3 id="specific-performance">specific performance</h3>
<p>Fulfilling the requirements of a contract in exactly the way the contract specifies. When most contracts are disputed in court, the plaintiff expects to receive money, that they can use to remedy the harm that the other party caused them in not holding up their side of the deal. When a plaintiff seeks specific performance, they want something that money can’t replace.</p>

<h3 id="third-party-beneficiary">third-party beneficiaries of the GPL</h3>
<p>People who aren’t a party to a <acronym title="General Public License">GPL</acronym> agreement, but who would benefit from the contract if the parties to the <acronym title="General Public License">GPL</acronym> do as they promise under the agreement. An example of such a benefit might be the receipt of the source code of the GPL’d software. See also General Public License (GPL).</p>

{% endblock %}