0 1 0
Kallithea Admin (kadmin) - 2 months ago 2020-07-17 21:11:33
bkuhn@sfconservancy.org
Copyleft Compliance: rewrite about page in light of strategic plan The copyleft-compliance/about.html page doubles as the introduction page to our compliance work. This is a start at the rewrite of that page to link off to the new items and have new text to inspire interest in the project.
1 file changed with 59 insertions and 42 deletions:
↑ Collapse Diff ↑
...
 
@@ -4,41 +4,56 @@
4 4
 
{% block content %}
5 5
 
<h1 id="ourwork">Conservancy's Copyleft Compliance Projects</h1>
6 6
 

	
7
 
<p>Free and open source software is
8
 
        everywhere and in everything; yet our software freedom is constantly
9
 
        eroded.  With the help of its volunteers, <a href="/members/current/">member projects</a>, and <a href="/about/staff/">staff</a>,
10
 
  Conservancy stands up for users' software freedom via its copyleft compliance work.</p>
11
 

	
12
 
<p>Conservancy engages in copyleft compliance work in two different ways: by acting directly
13
 
on behalf of <a href="/projects/">Conservancy's Member Projects</a> who request
14
 
Free and Open Source License compliance efforts, and for
15
 
specific, targeted member projects for communities of developers.</p>
16
 

	
17
 
<p>Conservancy's Copyleft Compliance Projects are run in a collaborative manner with
18
 
the project developers.  All copyright holders involved have the opportunity
19
 
to give input and guidance on Conservancy's strategy in dealing with
20
 
compliance issues.  Thus, all Conservancy's compliance matter have full
21
 
  support of relevant copyright holders.</p>
22
 

	
23
 
<p>In addition to taking feedback internally from those who participate as
24
 
  part of the coalitions described below, Conservancy also welcomes feedback
25
 
  and discussion with the general public about our copyleft compliance
26
 
  efforts.  This discussion happens on
27
 
  Conservancy's <a href="https://lists.sfconservancy.org/mailman/listinfo/principles-discuss">principles-discuss</a>
28
 
  mailing list, which is named
29
 
  for <a href="/copyleft-compliance/principles.html">Principles of
30
 
  Community-Oriented GPL Enforcement</a> which Conservancy follows in all our
31
 
  copyleft compliance.</p>
32
 

	
33
 
<h2 id="projects">Compliance Project For Our Fiscally Sponsored Projects</h2>
7
 
<p>As existing donors and supporters know, the Software Freedom Conservancy
8
 
  is a 501(c)(3) non-profit charity registered in New York, and Conservancy
9
 
  helps people take control of their computing by growing the software
10
 
  freedom movement, supporting community-driven alternatives to proprietary
11
 
  software, and defending free software with practical initiatives.
12
 
  Conservancy accomplishes these goals with various initiatives, including
13
 
  defending and upholding the rights of software users and consumers under
14
 
  copyleft licenses, such as the GPL.</p>
15
 

	
16
 
<p>Free and open source software (FOSS) is everywhere and in everything; yet
17
 
our software freedom is constantly eroded.  With the help of its
18
 
volunteers, <a href="/members/current/">member projects</a>,
19
 
and <a href="/about/staff/">staff</a>, Conservancy stands up for users'
20
 
software freedom via its copyleft compliance work.</p>
21
 

	
22
 
<p>Conservancy's primary work in copyleft compliance currently focuses on
23
 
our <a href="/copyleft-compliance/enforcement-strategy.html">Strategic GPL
24
 
Enforcement Initiative</a>.  This initiative, launched in August 2020,
25
 
represents the culmination of nearly 15 years of compliance work of
26
 
Conservancy spanning ten different fiscally sponsored projects, past lawsuits
27
 
against more than a dozen defendants, and hundreds of non-litigation
28
 
compliance actions.</p>
29
 

	
30
 
<p>For these many years, Conservancy has always given the benefit of the
31
 
  doubt to companies who exploited our good nature and ultimately simply
32
 
  ignore the rights of users and consumers.  In that time, the compliance
33
 
  industrial complex has risen to a multi-million-dollar industry &mdash;
34
 
  selling (mostly proprietary) products, services, and consulting to
35
 
  companies.  Yet, these compliance efforts ignore consistently the most
36
 
  essential promise of copyleft &mdash; the complete, Corresponding Source
37
 
  and "the scripts used to control compilation and installation of the
38
 
  executable".</p>
39
 

	
40
 
<p>We encourage our supporters and software freedom enthusiasts everywhere to
41
 
  <a href="/copyleft-compliance/enforcement-strategy.html">read our detailed
42
 
  strategic plan for GPL enforcement</a> and its companion
43
 
  project, <a href="/copyleft-compliance/firmware-liberation.html">Our
44
 
    Firmware Liberation Project</a>.</p>
45
 

	
46
 
<h2 id="projects">Compliance Relationship to Fiscally Sponsored Projects</h2>
34 47
 

	
35 48
 
<p>Historically, Conservancy was well-known for its ongoing license
36
 
compliance efforts on behalf of its BusyBox member project.  Today, Conservancy
37
 
does semi-regular compliance work for its BusyBox, Evergreen, Git, Inkscape, Mercurial,
38
 
Samba, Sugar Labs, QEMU and Wine member projects.  If you are a copyright holder
39
 
in any member project of Conservancy, please contact the project's leadership committtee,
49
 
compliance efforts on behalf of its BusyBox member project.  Today,
50
 
Conservancy does semi-regular compliance work for its BusyBox, Git, Inkscape,
51
 
Mercurial, Samba, QEMU and Wine member projects.  If you are a copyright
52
 
holder in any member project of Conservancy, please contact the project's
53
 
leadership committtee,
40 54
 
via <a href="mailto:PROJECTNAME@sfconservancy.org">&lt;PROJECTNAME@sfconservancy.org&gt;</a>
41
 
for more information on getting involved in compliance efforts in that project.
55
 
for more information on getting involved in compliance efforts in that
56
 
project.
42 57
 
</p>
43 58
 

	
44 59
 
<h2 id="linux">GPL Compliance Project For Linux Developers</h2>
...
 
@@ -71,7 +86,6 @@ Conservancy should
71 86
 
  with <a href="mailto:linux-services@sfconservancy.org">&lt;linux-services@sfconservancy.org&gt;</a>
72 87
 
  first.</p>
73 88
 

	
74
 

	
75 89
 
<h2 id="debian">The Debian Copyright Aggregation Project</h2>
76 90
 

	
77 91
 
<p>In August 2015, <a href="/news/2015/aug/17/debian/">Conservancy announced the Debian Copyright Aggregation
...
 
@@ -106,24 +120,27 @@ Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&l
106 120
 
<p>However, the Guide is admittedly a large document, so for those who are
107 121
 
  interested in a short summary of describing how Conservancy handles GPL
108 122
 
  enforcement and compliance
109
 
  work, <a href="/blog/2012/feb/01/gpl-enforcement/">this
110
 
  blog post outlining the compliance process</a> is likely the best source.</p>
123
 
  work, <a href="/blog/2012/feb/01/gpl-enforcement/">this blog post outlining
124
 
  the compliance process</a> is likely the best source.</p>
111 125
 

	
112 126
 
<h2 id="reporting">Reporting GPL Violations To Us</h2>
113 127
 

	
114 128
 
<p>If you are aware of a license violation or compliance issue regarding
115
 
  Debian, Linux, or
116
 
  any <a href="/members/current/">Conservancy member
117
 
  project</a> (&mdash; in particular BusyBox, Evergreen, Inkscape, Mercurial,
129
 
  Debian, Linux, or any <a href="/members/current/">Conservancy member
130
 
  project</a> (&mdash; in particular BusyBox, Git, Inkscape, Mercurial,
118 131
 
  Samba, Sugar Labs, or Wine),
119 132
 
  please <a href="mailto:compliance@sfconservancy.org">contact us by email at
120
 
    &lt;compliance@sfconservancy.org&gt;</a>.</p>
133
 
  &lt;compliance@sfconservancy.org&gt;</a>.</p>
134
 

	
135
 
<!--- FIXME: bkuhn is rewriting this blog post fresh the weekend of --
136
 
      2020-07-18 so we need not link to ebb.org anymore when we roll out
137
 
      these changes --> 
121 138
 

	
122 139
 
<p>If you think you've found a GPL violation, we encourage you to
123 140
 
   read <a href="http://ebb.org/bkuhn/blog/2009/11/08/gpl-enforcement.html">this
124
 
   personal blog post by our Distinguished Technologist, Bradley M. Kuhn</a>,
125
 
   about good practices in discovering and reporting GPL violations.  (We'd
126
 
   also like someone to convert the text of that blog post into a patch for
141
 
   personal blog post by our Policy Fellow, Bradley M. Kuhn</a>, about good
142
 
   practices in discovering and reporting GPL violations.  (We'd also like
143
 
   someone to convert the text of that blog post into a patch for
127 144
 
   <a href="http://compliance.guide">The Compliance Guide on
128 145
 
   copyleft.org</a>; submit it
129 146
 
   via <a href="https://k.copyleft.org/guide/">k.copyleft.org</a>.)</p>
0 comments (0 inline, 0 general)