Changeset - a772f7fa2886
[Not reviewed]
Merge
0 6 8
eximious - 4 years ago 2019-09-11 16:41:40
deb@seagl.org
Merge branch 'master' of ssh://k.sfconservancy.org/website
5 files changed:
0 comments (0 inline, 0 general)
www/conservancy/static/about/staff/index.html
Show inline comments
...
 
@@ -83,13 +83,26 @@ included financial trading software development on GNU/Linux and
 
previously involved writing system software for hardware companies,
 
including driver writing for the kernel named Linux at ATI (now AMD) and
 
Qualcomm.  He founded a company that designs and builds magnetic stripe
 
readers for security hobbyists where he designed the hardware and
 
developed the device's tools and firmware, which are both free software.
 
Denver also writes free software in his spare time, with patches accepted
 
into Wine, the kernel named Linux, and GNU wdiff.  Denver received his
 
BMath in Computer Science from the University of Waterloo.  He gives presentations
 
about digital civil rights and protecting the free software ecosystem,
 
having spoken at conferences such as CopyCamp Toronto, FOSSLC's
 
Summercamp, and the Open Video Conference.</p>
 

	
 
<h2 id="dimesio">Rosanne DiMesio - Technical Bookkeeper</h2>
 

	
 
<p>Rosanne DiMesio is the Technical Bookkeeper at the Software Freedom
 
Conservancy where she handles incoming and outgoing accounting
 
activities for all its member projects as well as financial operations
 
for Conservancy itself. Rosanne has been volunteering with the Wine
 
Project since 2008 where she focuses on user support and documentation.
 
She has worked as an English teacher, a freelance writer and as IT
 
support. She is passionate about helping free software projects improve
 
their user experience. Rosanne received her Masters in Communication &amp;
 
Theater at the University of Illinois at Chicago and her Bachelor&rsquo;s
 
degree in English from the University of Chicago.</p>
 

	
 
{% endblock %}
www/conservancy/static/copyleft-compliance/about.html
Show inline comments
 
{% extends "base_compliance.html" %}
 
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
 
{% block submenuselection %}AboutCompliance{% endblock %}
 
{% block content %}
 
<h1>Conservancy's Copyleft Compliance Projects</h1>
 
<h1 id="ourwork">Conservancy's Copyleft Compliance Projects</h1>
 

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

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

	
 
<p>Conservancy's Copyleft Compliance Projects are run in a collaborative manner with
...
 
@@ -21,25 +21,25 @@ compliance issues.  Thus, all Conservancy's compliance matter have full
 
  support of relevant copyright holders.</p>
 

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

	
 
<h2>Compliance Project For Our Fiscally Sponsored Projects</h2>
 
<h2 id="projects">Compliance Project For Our Fiscally Sponsored Projects</h2>
 

	
 
<p>Historically, Conservancy was well-known for its ongoing license
 
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, QEMU and Wine member projects.  If you are a copyright holder
 
in any member project of Conservancy, please contact the project's leadership committtee,
 
via <a href="mailto:PROJECTNAME@sfconservancy.org">&lt;PROJECTNAME@sfconservancy.org&gt;</a>
 
for more information on getting involved in compliance efforts in that project.
 
</p>
 

	
 
<h2 id="linux">GPL Compliance Project For Linux Developers</h2>
 

	
...
 
@@ -74,25 +74,25 @@ Conservancy should
 

	
 
<h2 id="debian">The Debian Copyright Aggregation Project</h2>
 

	
 
<p>In August 2015, <a href="/news/2015/aug/17/debian/">Conservancy announced the Debian Copyright Aggregation
 
Project</a>.  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.</p>
 

	
 
<p>Debian contributors who wish to assign copyright to or sign an enforcement agreement with
 
Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&lt;debian-services@sfconservancy.org&gt;</a>.</p>
 

	
 
<h2>Conservancy's Commitment to Copyleft License Compliance</h2>
 
<h2 id="commitment">Conservancy's Commitment to Copyleft License Compliance</h2>
 

	
 
<p>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 has co-published,
 
  with the Free Software Foundation (FSF), <a href="/copyleft-compliance/principles.html">the principles that both organizations
 
  follow in their compliance efforts</a>.
 
  Also in collaboration with the FSF, Conservancy also sponsors
 
  the <a href="https://copyleft.org/guide/"><cite>Copyleft and the GNU
 
  General Public License:A Comprehensive Tutorial and Guide</cite></a>,
 
  which <a href="/news/2014/nov/07/copyleft-org/">formally
 
  launched in fall 2014</a>.  The Guide includes tutorial materials about
...
 
@@ -100,39 +100,39 @@ Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&l
 
  including <a href="https://copyleft.org/guide/comprehensive-gpl-guidepa2.html"><cite>A
 
  Practical Guide to GPL Compliance</cite></a>.  The materials
 
  on <a href="https://copyleft.org/">copyleft.org</a> have been developed and
 
  improved since 2002, and are themselves copylefted, and developed
 
  collaboratively in public.</p>
 

	
 
<p>However, the Guide is admittedly a large document, so for those who are
 
  interested in a short summary of describing how Conservancy handles GPL
 
  enforcement and compliance
 
  work, <a href="/blog/2012/feb/01/gpl-enforcement/">this
 
  blog post outlining the compliance process</a> is likely the best source.</p>
 

	
 
<h2>Reporting GPL Violations To Us</h2>
 
<h2 id="reporting">Reporting GPL Violations To Us</h2>
 

	
 
<p>If you are aware of a license violation or compliance issue regarding
 
  Debian, Linux, or
 
  any <a href="/members/current/">Conservancy member
 
  project</a> (&mdash; in particular BusyBox, Evergreen, Inkscape, Mercurial,
 
  Samba, Sugar Labs, or Wine),
 
  please <a href="mailto:compliance@sfconservancy.org">contact us by email at
 
    &lt;compliance@sfconservancy.org&gt;</a>.</p>
 

	
 
<p>If you think you've found a GPL violation, we encourage you to
 
   read <a href="http://ebb.org/bkuhn/blog/2009/11/08/gpl-enforcement.html">this
 
   personal blog post by our Distinguished Technologist, Bradley M. Kuhn</a>,
 
   about good practices in discovering and reporting GPL violations.  (We'd
 
   also like someone to convert the text of that blog post into a patch for
 
   <a href="http://compliance.guide">The Compliance Guide on
 
   copyleft.org</a>; submit it
 
   via <a href="https://k.copyleft.org/guide/">k.copyleft.org</a>.)</p>
 
   
 
<h2>Donate to Support This Work</h2>
 
<h2 id="support">Donate to Support This Work</h2>
 

	
 
<p>Finally, Conservancy welcomes <a href="#donate-box"
 
  class="donate-now">donations</a> in support of our GPL Compliance Projects,
 
  and we encourage you to become a <a href="/supporter/">an official
 
  Supporter of Software Freedom Conservancy</a>. </p>
 
</div>
 
{% endblock %}
www/conservancy/static/copyleft-compliance/vmware-lawsuit-appeal.html
Show inline comments
 
{% extends "base_compliance.html" %}
 
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
 
{% block submenuselection %}VMwareLawsuitAppeal{% endblock %}
 
{% block content %}
 
<h2>The time has come to stand up for the GPL.</h2>
 

	
 
<p><strong>Update 2019-04-02:</strong> Please
 
  see <a href="https://sfconservancy.org/news/2019/apr/02/vmware-no-appeal/">this
 
  announcement regarding conclusion of the VMware suit in Germany</a>.  Since the suit has
 
  concluded, any funds you donate here will support our ongoing compliance efforts.  The
 
  remaining material below is left as it was before that announcement:</p>
 

	
 
<p><em>In March 2015, Conservancy <a href="/news/2015/mar/05/vmware-lawsuit/">announced Christoph Hellwig's
 
    lawsuit against VMware in Germany</a>.  In July 2016,
 
    we <a href="/news/2016/aug/09/vmware-appeal/">announced that Christoph
 
    would appeal the lower court's ruling</a>.</p>
 
    Support Conservancy's and Christoph's efforts in this area
 
    by <a href="/supporter/">becoming a Conservancy
 
    supporter</a> or <a href="#donate-box" class="donate-now">donating via
 
    the link on the right</a>.</em></p>
 

	
 

	
 
<p>We were told to ask nicely and repeatedly, so we did.</p>
 

	
www/conservancy/static/copyleft-compliance/vmware-lawsuit-faq.html
Show inline comments
 
{% extends "base_compliance.html" %}
 
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
 
{% block submenuselection %}VMwareLawsuitFAQ{% endblock %}
 
{% block content %}
 
<h1>Frequently Asked Questions about Christoph Hellwig's VMware Lawsuit</h1>
 

	
 
<p><strong>Update 2019-04-02:</strong> Please
 
  see <a href="https://sfconservancy.org/news/2019/apr/02/vmware-no-appeal/">this
 
  announcement regarding conclusion of the VMware suit in Germany</a>.  Since the suit has
 
  concluded, any funds you donate here will support our ongoing compliance efforts.  The
 
  remaining material below is left as it was before that announcement:</p>
 

	
 

	
 
<p>Conservancy maintains this
 
  <abbr title="Frequently Asked Questions">FAQ</abbr> list regarding
 
  <a href="/news/2015/mar/05/vmware-lawsuit/">Christoph Hellwig's lawsuit against VMware
 
  in Germany over alleged GPL violations on Linux</a> as a service to the
 
  Free Software community, and in particular, the copyleft community.  Conservancy
 
  realizes this lawsuit generates many questions and interest
 
  from the community.  Legal counsel (both Conservancy's own, and
 
  Christoph's lawyer, Till Jaeger) correctly advise us to limit our public
 
  comments regarding specific details of the case while litigation remains
 
  pending in court.  Nevertheless, Conservancy, as a
 
  non-profit charity serving the public good, seeks to be as transparent as
 
  possible.  If you have additional questions you'd like to see answered
www/conservancy/static/copyleft-compliance/vmware-lawsuit-links.html
Show inline comments
 
new file 100644
 
{% extends "base_compliance.html" %}
 
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
 
{% block submenuselection %}VMwareLawsuitLinks{% endblock %}
 
{% block content %}
 
<h1>Christoph Hellwig's VMware Lawsuit - Resources</h1>
 

	
 
<p>Christoph Hellwig's case against VMware in Germany has concluded.  You can
 
  view the relevant announcements and analysis that Conservancy has published
 
  about the case below, starting with the announcement regarding the conclusion
 
  of the case:</p>
 

	
 
<p>
 
  <ul>
 
    <li><a href="/news/2019/apr/02/vmware-no-appeal/">VMware Suit Concludes in Germany</a></li>
 
    <li><a href="http://faif.us/cast/2019/apr/22/0x66/"><cite>Free as in
 
    Freedom</cite> that discusses the conclusion of the lawsuit</a></li>
 
    <li><a href="/news/2016/aug/09/vmware-appeal/">Announcement of Appeal</a></li>
 
    <li><a href="/news/2015/mar/05/vmware-lawsuit/">Original Press Release</a></li>
 
    <li><a href="/copyleft-compliance/vmware-lawsuit-appeal.html">Funding our Compliance Work</a></li>
 
    <li><a href="/copyleft-compliance/vmware-lawsuit-faq.html">
 
      <abbr title="Frequently Asked Questions">FAQ</abbr> on VMware Lawsuit</a></li>
 
    <li><a href="/copyleft-compliance/vmware-code-similarity.html">VMware's &amp;
 
      Christoph's Code Similarity Analysis</a></li>
 
  </ul>
 
</p>
 
{% endblock %}

Changeset was too big and was cut off... Show full diff anyway

0 comments (0 inline, 0 general)