add base_learn and fix menus for glossary
This commit is contained in:
parent
e370250897
commit
2123cf0047
4 changed files with 138 additions and 13 deletions
|
@ -1,6 +1,6 @@
|
|||
{% extends "base_compliance.html" %}
|
||||
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
|
||||
{% block submenuselection %}EnforcementStrategy{% endblock %}
|
||||
{% extends "base_learn.html" %}
|
||||
{% block subtitle %}Glossary of terms - {% endblock %}
|
||||
{% block submenuselection %}Glossary{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<h1 id="glossary">Glossary of terms</h1>
|
||||
|
|
|
@ -1,15 +1,106 @@
|
|||
{% extends "base_press.html" %}
|
||||
{% extends "base_learn.html" %}
|
||||
{% block subtitle %}Press - {% endblock %}
|
||||
{% block submenuselection %}Press{% endblock %}
|
||||
{% block content %}
|
||||
<h1 id="QandA">Q&A</h1>
|
||||
<h1 id="QandA">Q & A</h1>
|
||||
|
||||
<p>"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
|
||||
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
|
||||
quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
|
||||
consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
|
||||
cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat
|
||||
non proident, sunt in culpa qui officia deserunt mollit anim id est
|
||||
laborum."</p>
|
||||
|
||||
<h3 id="">Q: Who is the defendant in this lawsuit?</h3>
|
||||
|
||||
<p>The defendant is Vizio, Inc., a U.S.-based TV maker and media company that has been publicly traded on the New York Stock Exchange since March 2021.</p>
|
||||
|
||||
<h3 id="">Q: What did Vizio do wrong?</h3>
|
||||
|
||||
<p>The lawsuit alleges that Vizio’s TV products, built on its SmartCast system, contain software that Vizio unfairly appropriated from a community of developers who intended consumers to have very specific rights to modify, improve, share, and reinstall modified versions of the software.</p>
|
||||
|
||||
<h3 id="">Q: So, Vizio didn’t create SmartCast?</h3>
|
||||
|
||||
<p>It appears from extensive research that the core components of SmartCast were not created by Vizio, but rather, are based on various components licensed to the public under free and open-source software (FOSS) licenses. Most notably, many of the programs that are part of the SmartCast system are licensed under the GPL.</p>
|
||||
|
||||
<h3 id="">Q: What is copyleft?</h3>
|
||||
|
||||
<p>Copyleft is a term used to describe a license that uses the rights granted under copyright—not to restrict usage, but instead to ensure that the software is always shared freely.</p>
|
||||
|
||||
<h3 id="">Q: What is FOSS? </h3>
|
||||
|
||||
<p>“FOSS” stands for free and open-source software that allows for software freedom. “Software freedom” means 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="">Q: I thought FOSS allowed companies to simply take software from the commons and put it into their products whenever they wanted? Isn’t that the whole point of FOSS—for companies to get components for their products and lower their cost of production?</h3>
|
||||
|
||||
<p>While that is the main advantage that big corporations get from FOSS, it was never the primary impetus behind FOSS. Particularly through special licensing terms like the GPL, this licensing approach creates an egalitarian community of users, developers, and consumers. When functioning correctly, each individual and organization that participates in FOSS stands on equal footing with everyone else. Licenses like the GPL have rules to assure everyone's rights in that ecosystem are treated with equal respect and reverence. This is why compliance with these rules is important and we must stand up against companies who refuse to comply. </p>
|
||||
|
||||
<h3 id="">Q: But, I'm not a software developer. Why should I care at all that Vizio won’t let me modify and reinstall GPL’d components in its SmartCast system?</h3>
|
||||
|
||||
<p>Right-to-repair software is essential for everyone, even if you don't know how to make the repairs yourself. Once upon a time, we had lots of local vendors that could repair and fix TVs when they broke. That’s because TVs were once analog hardware devices that could be taken apart and understood merely by inspection from someone with the sufficient knowledge. TVs today are simply a little computer attached to a large display. As such, the most important part that needs repairs is usually when the software malfunctions, has bugs, or otherwise needs upgrades and changes. The GPL was specifically designed to assure such fixes could be done, and that consumers (or agents those consumers hire on the open market) can make such repairs and changes. </p>
|
||||
|
||||
<h3 id="">Q: Alright, that makes sense, but I’m happy with Vizio’s SmartCast right now. What difference does it make to me if Vizio won’t give me the rights under the GPL?</h3>
|
||||
|
||||
<p>Time and time again, companies stop supporting the software build for the device long before the computer inside the device fails. In other words, these devices are built for planned premature obsolescence. </p>
|
||||
|
||||
<p>By refusing to comply with the pro-consumer terms of the GPL, Vizio has the power to disable your TV at any time it wants, over your internet connection, without your knowledge or consent. If Vizio complied with the GPL, all would not be lost in this scenario: volunteers and third-party entities could take GPL’d software as a basis for a replacement for SmartCast. Without these rights, consumers are essentially forced to purchase new devices when they could be repaired.</p>
|
||||
|
||||
<h3 id="">Q: Creation of a replacement for SmartCast seems far-fetched to me. After all, most of the software in SmartCast is not actually GPL’d, only a portion of the components and programs are GPL’d. How will Vizio's compliance with the GPL actually lead to an alternative firmware?</h3>
|
||||
|
||||
<p>Years ago, people said the very same thing about wireless routers, which had only partially GPL'd firmwares. However, thanks to actions to enforce the GPL in the wireless router market, the OpenWrt project was born! That project is now the premiere replacement software for wireless routers from almost every major manufacturer on the market. There is now healthy competition and even occasional cooperation between a hobbyist and community-led firmware project and the wireless router manufacturers. We believe the same can happen for TVs, but the first step is assuring the entire TV market complies with the GPL.</p>
|
||||
|
||||
<h3 id="">Q: What indications do you have that compliance with the GPL will be a catalyst for alternative firmwares?</h3>
|
||||
|
||||
<p>Beyond the OpenWrt example, Software Freedom Conservancy sued 14 defendants for GPL violations in 2009, including Samsung for its 2009-era TV models. Thanks to the source release that was achieved through the settlement of that lawsuit, a community-led SamyGo project was created for that era of TVs. (source)</p>
|
||||
|
||||
<h3 id="">Q: Who is the plaintiff in the lawsuit?</h3>
|
||||
|
||||
<p>Software Freedom Conservancy is the plaintiff in this case. The organization is filing as a third-party beneficiary, as the purchaser of a product which has copylefted code on it. A consumer of a product such as this has the right to access the source code so that it can be modified, studied, and redistributed (under the appropriate license conditions).</p>
|
||||
|
||||
<h3 id="">Q: What makes this different than other GPL compliance lawsuits?</h3>
|
||||
|
||||
<p>In the past, the plaintiffs have always been copyright holders of the specific GPL code. In this case Software Freedom Conservancy is demonstrating that it's not just the copyright holders, but also the receivers of the licensed code which are entitled to their rights.</p>
|
||||
|
||||
<h3 id="">Q: What type of case is this? How does it compare to previous litigation by Software Freedom Conservancy regarding the GPL?</h3>
|
||||
|
||||
<p>Previously, Software Freedom Conservancy filed as a copyright holder in federal court, or coordinated or funded litigation by other copyright holders in copyright cases in the U.S. and Germany. This is an example of how, historically, GPL litigation has focused on the rights of the developers. However, the rights assured by the GPL are actually not intended primarily for the original developers, but rather for people who purchase products that contain GPL’d software. That is what makes this litigation unique and historic in terms of defending consumer rights. It is the first case that focuses on the rights of individual consumers as third-party beneficiaries of the GPL.</p>
|
||||
|
||||
<h3 id="">Q: Why are you filing a third-party beneficiary claim instead of a copyright claim?</h3>
|
||||
|
||||
<p>For too long, GPL enforcement has focused only on the rights of developers, who are often not the ones impacted by the technology in question. Some of those same developers even have lucrative jobs working for the various companies that violate the GPL. The GPL was designed to put the rights of hobbyists, individual developers, consumers, small companies, and nonprofit organizations on equal footing with big companies. With the advent of more contributions to GPL’d software coming from for-profit multinational corporations and fewer from individuals, the rights of these other parties are often given second-class billing. The third-party beneficiary claim prioritizes the consumers, who are the users and the most important beneficiaries of the rights under GPL.</p>
|
||||
|
||||
<h3 id="">Q: Are you saying the rights of developers under the GPL are not important?</h3>
|
||||
|
||||
<p>Not at all! Most would agree that individual developers care deeply about the software freedom of users. They are the artists who create the amazing FOSS on which all of us rely. However, as Francis Ford Coppola once said (paraphrased), “to understand who holds the power in any culture, look not to the artists but who employs the artists”—a quote which suits this situation well. Large multinational corporations have co-opted FOSS for their own bottom lines. While many developers privately cheer Software Freedom Conservancy’s efforts and donate money to this cause, they fear the power that their employers exert and have asked Software Freedom Conservancy to fight for the software freedom of users.</p>
|
||||
|
||||
<h3 id="">Q: Why is this important for the future of developers?</h3>
|
||||
|
||||
<p>The next generation of developers comes from the users of today. The golden age of FOSS that the industry now enjoys came to fruition from the counterculture created by FOSS activists in the 1990s and early 2000s. During this time, Linux and other GPL’d software was considered just a curiosity (and was even accused of being anti-American). Nevertheless, the rights assured by the GPL ultimately led to a new generation of software developers learning how to build Linux and all the amazingly useful FOSS around it. To recruit a diverse group of the next generation of enthusiastic developers, we must ensure that the rights under GPL are available to every single individual, consumer and hobbyist around the globe. That is what this lawsuit is about.</p>
|
||||
|
||||
<h3 id="">Q: If the goal is to fight for all consumer rights, why not file this lawsuit as a class action? </h3>
|
||||
|
||||
<p>Forcing consumers to fight for their individual rights is one way that for-profit corporations exert their inappropriate power. Actions such as this lawsuit seek to disrupt this power dynamic by asserting that all consumers of copylefted code deserve the opportunity to know, access and modify the code on their devices. However, expecting all consumers to have to personally participate in that process not only puts an undue burden on them, it simply is not realistic. It is not how change happens. Furthermore, pursuant to “The Principles of Community Oriented GPL Enforcement,” the lawsuit does not prioritize financial remedy over compliance. This lawsuit seeks the most important remedy for the public good: release of the Complete, Corresponding Source (CCS) for all GPL’d components on Vizio TVs. Once that is achieved, the benefit is immediately available to not only all who purchased a Vizio TV, but also to the entire FOSS community. </p>
|
||||
|
||||
<h3 id="">Q: What are “The Principles of Community Oriented GPL Enforcement”?</h3>
|
||||
|
||||
<p>In 2016, Software Freedom Conservancy published “The Principles of Community-Oriented GPL Enforcement” in response to those who might use copyleft licenses for their own financial gain. Software Freedom Conservancy is part of a long tradition of using copyleft enforcement as intended: to further the rights and freedoms of individual users, consumers, and developers. Pursuant to those principles, Software Freedom Conservancy never prioritizes financial gain over assuring the rights guaranteed by the GPL are upheld.</p>
|
||||
|
||||
<h3 id="">Q: Are the court documents released? Does that relate to why the litigation was brought in the U.S.?</h3>
|
||||
|
||||
<p>Software Freedom Conservancy brought this litigation within the U.S. specifically because litigation in this country is completely public. Historically, Germany has been one of the most popular venues for GPL litigation but it also has a huge downside: the German legal system keeps all details of the cases private and there is little transparency. </p>
|
||||
|
||||
<h3 id="">Q: Who is funding this lawsuit? </h3>
|
||||
|
||||
<p>This lawsuit is central to the mission of Software Freedom Conservancy. The organization has received grants from Amateur Radio Digital Communications (ARDC) to support GPL compliance work. As a nonprofit, charitable donations are also an important source of funding to carry out the work. This combined financial support allowed for this litigation to begin. However, continued donor support will be vital since litigation like this is quite expensive.</p>
|
||||
|
||||
<h3 id="">Q: How can someone make a donation?</h3>
|
||||
|
||||
<p>To make a tax-deductible donation to Software Freedom Conservancy, go to sfconservancy.org/donate. The best way to support this important work is to join as an official Sustainer. Details on that program are available at sfconservancy.org/sustainer. </p>
|
||||
|
||||
<h3 id="">Q: Why must you file a lawsuit? Isn’t there any other way to convince Vizio to comply with the GPL? </h3>
|
||||
|
||||
<p>Vizio has a long history of violating copyleft. The company has also stopped replying to inquiries from Software Freedom Conservancy. Vizio has been benefiting from the use of an abundance of existing copylefted software, but completely ignores the responsibilities that come with using the licenses. Furthermore, Vizio has already been subject to a large class-action suit that alleged that Vizio was misusing its customers’ private information (Vizio settled that class action for $17 million).</p>
|
||||
|
||||
<h3 id="">Q: What GPL code has been discovered in Vizio’s SmartCast? </h3>
|
||||
|
||||
<p>SmartCast is a Linux-based operating system. That means that not only do multiple copies of the Linux kernel appear in the firmware, other GPL'd and LGPL'd programs were found, including U-Boot, bash, gawk, tar, glibc, and ffmpeg.</p>
|
||||
|
||||
<h3 id="">Q: How can I verify Software Freedom Conservancy’s technical findings above? </h3>
|
||||
|
||||
<p>Object code can be found on the TVs and source code/binaries on the filesystem. There are multiple models in which we can confirm the findings. Go to sfconservancy.org/vizio for details.</p>
|
||||
|
||||
{% endblock %}
|
||||
|
|
|
@ -31,7 +31,6 @@
|
|||
<h2>Our Copyleft {% block category %}Compliance{% endblock %} Projects</h2>
|
||||
<ul>
|
||||
<li class="AboutCompliance"><a href="/copyleft-compliance/about.html">About</a></li>
|
||||
<li class="Glossary"><a href="/copyleft-compliance/glossary.html">Glossary</a></li>
|
||||
<li class="EnforcementStrategy"><a href="/copyleft-compliance/enforcement-strategy.html">Strategic GPL Enforcement Initiative</a></li>
|
||||
<li class="CopyleftPrinciples"><a href="/copyleft-compliance/principles.html">Principles of Community-Oriented GPL Enforcement</a></li>
|
||||
<li class="LiberateFirmware"><a href="/copyleft-compliance/firmware-liberation.html">Liberate IoT Firmware via GPL Enforcement</a></li>
|
||||
|
|
35
www/conservancy/templates/base_learn.html
Normal file
35
www/conservancy/templates/base_learn.html
Normal file
|
@ -0,0 +1,35 @@
|
|||
{% extends "base_conservancy.html" %}
|
||||
{% load cache %}
|
||||
{% load humanize %}
|
||||
{% block head %}
|
||||
<link href="/jquery-ui.css" rel="stylesheet" type="text/css"/>
|
||||
<link href="/forms.css" rel="stylesheet" type="text/css"/>
|
||||
|
||||
{% endblock %}
|
||||
|
||||
{% block outercontent %}
|
||||
<div class="donate-sidebar">
|
||||
<table style="background-color:#afe478;width:100%;">
|
||||
<tr><td style="text-align:center;padding:10px;padding-bottom:10px;">
|
||||
<div id="donate-box" class="toggle-unit"><h1 class="toggle-content">Support
|
||||
Now!</h1></div>
|
||||
|
||||
<h3>Support Copyleft Enforcement Now!</h3>
|
||||
|
||||
<p>
|
||||
To support our copyleft compliance & enforcement work,
|
||||
please <a href="/sustainer/#annual"><span class="donate-box-highlight">become a Conservancy
|
||||
Sustainer <strong>right now</strong></span></a>. We can't sustain
|
||||
this work without ongoing support from donors like you!</p>
|
||||
</td></tr></table>
|
||||
</div>
|
||||
<div class="content-with-donate-sidebar">
|
||||
<div id="container">
|
||||
<div id="sidebar" class="{% block submenuselection %}other{% endblock %}">
|
||||
<h2>Learn</h2>
|
||||
{% include 'submenus/learn_partial.html' %}
|
||||
</div>
|
||||
<div id="mainContent">{% block content %}{% endblock %}
|
||||
</div>
|
||||
</div></div>
|
||||
{% endblock %}
|
Loading…
Reference in a new issue