From abe226a6f4ccda45a3aff3f8f558849bf1fa5b46 2015-11-29 20:13:39 From: Bradley M. Kuhn Date: 2015-11-29 20:13:39 Subject: [PATCH] Rewrite page; fully discuss all compliance effort This about page now talks about all of Conservancy's compliance efforts. --- diff --git a/www/conservancy/static/copyleft-compliance/about.html b/www/conservancy/static/copyleft-compliance/about.html index 7a4c254cb6f8ee57fad59d15224d9839d22ab458..0fdc7ca3c59e01d9b02cb60a648a792372f1bb74 100644 --- a/www/conservancy/static/copyleft-compliance/about.html +++ b/www/conservancy/static/copyleft-compliance/about.html @@ -4,35 +4,77 @@ {% block content %}

Conservancy's Copyleft Compliance Projects

-

The GPL Compliance Project for Linux Developers is comprised of copyright -holders in the kernel, Linux, who have contributed to Linux under its -license, the -GPLv2. These copyright holders have formally asked Conservancy to engage -in compliance efforts for their copyrights in the Linux kernel.

+

Free and open source software is + everywhere and in everything; yet our software freedom is constantly + eroded. With the help of its volunteers, member projects, and staff, + Conservancy stands up for users' software freedom via its copyleft compliance work.

+ +

Conservancy engages in copyleft compliance work in two different ways: by acting directly +on behalf of Conservancy's Member Projects who request +Free and Open Source License compliance efforts, and for +specific, targeted member projects for communities of developers.

+ +

Conservancy's Copyleft Compliance Projects are run in a collaborative manner with +the project developers. All copyright holders involved have the opportunity +to give input and guidance on Conservancy's strategy in dealing with +compliance issues. Thus, all Conservancy's compliance matter have full +support of relevant copyright holders.

+ +

Member Project Compliance Project

Historically, Conservancy was well-known for its ongoing license -compliance efforts on behalf of its BusyBox member project. In May -2012, Conservancy -announced a coordinated compliance effort on behalf of its BusyBox and -Samba projects, and also launched this unique project, called the GPL +compliance efforts on behalf of its BusyBox member project. Today, Conservancy +does semi-regular compliance work for its BusyBox, Evergreen, Git, Inkscape, Mercurial, +Samba, Sugar Labs and Wine member projects. If you are a copyright holder +in any member project of Conservancy, please contact the project's leadership committtee, +via <PROJECTNAME@sfconservancy.org> +for more information on getting involved in compliance efforts in that project. +

+ +

GPL Compliance Project For Linux Developers

+ +

In May +2012, Conservancy +launched the GPL Compliance Project for Linux Developers, which handles compliance and enforcement activities on behalf of more than a dozen Linux copyright holders.

-

Conservancy's GPL Compliance Project is run in a collaborative manner with -the project developers. All copyright holders involved have the opportunity -to give input and guidance on Conservancy's strategy in dealing with -compliance issues. Thus, all Conservancy's compliance matter have full -support of relevant copyright holders.

+

The GPL Compliance Project for Linux Developers is comprised of copyright +holders in the kernel, Linux, who have contributed to Linux under its +license, the +GPLv2. These copyright holders have formally asked Conservancy to engage +in compliance efforts for their copyrights in the Linux kernel. In addition, +some developers have directly assigned their copyrights on Linux to Conservancy, +so Conservancy also enforces the GPL on Linux via its own copyrights in Linux.

+ +

Linux copyright holders who wish to assign copyright to or sign an enforcement agreement with +Conservancy should contact <linux-services@sfconservancy.org>.

+ + +

The Debian Copyright Aggregation Project

+ +

In August 2015, Conservancy announced the Debian Copyright Aggregation +Project. This project allows Debian contributors to assign copyrights to +Conservancy, or sign enforcement agreements allowing Conservancy to enforce +Free and Open Source (FOSS) licenses on their behalf. Many Debian contributors +have chosen each of these options already, and more continue to join.

+ +

Debian contributors who wish to assign copyright to or sign an enforcement agreement with +Conservancy should contact <debian-services@sfconservancy.org>.

+ +

Conservancy's Commitment to Copyleft License Compliance

Conservancy is dedicated to encouraging all users of software to comply with Free Software licenses. Toward this goal, in its compliance efforts, Conservancy helps distributors of Free Software in a friendly spirit of - cooperation and participation. In this spirit, Conservancy also sponsors + cooperation and participation. In this spirit, Conservancy has co-published, + with the Free Software Foundation (FSF), the principles that both organizations + follow in their compliance efforts. + Also in collaboration with the FSF, Conservancy also sponsors the Copyleft and the GNU - General Public License:A Comprehensive Tutorial and Guide, in - collaboration with the Free Software Foundation (FSF), - which Conservancy formally + General Public License:A Comprehensive Tutorial and Guide, + which formally launched in fall 2014. The Guide includes tutorial materials about copyleft and compliance with copyleft licenses, including A @@ -48,7 +90,7 @@ support of relevant copyright holders.

blog post outlining the compliance process is likely the best source.

If you are aware of a license violation or compliance issue regarding - Linux, or + Debian, Linux, or any Conservancy member project (and in particular BusyBox, Evergreen, Inkscape, Mercurial, Samba, Sugar Labs, or Wine), @@ -56,11 +98,9 @@ support of relevant copyright holders.

<compliance@sfconservancy.org>.

Finally, Conservancy welcomes in support of the GPL Compliance Project - for Linux Developers. Just use the in support of our GPL Compliance Projects. + Just use the . Be sure to mention “GPL Compliance Project for - Linux Developers” in the memo line or description field of the - donation.

+ methods listed.

{% endblock %}