All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Turner <novalis@fsf.org>
To: linux-kernel@vger.kernel.org
Subject: Linksys/Cisco GPL Violations
Date: 29 Sep 2003 14:22:47 -0400	[thread overview]
Message-ID: <1064859766.20847.33983.camel@banks> (raw)

[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]


To Linux Developers Concerned about the Linksys/Cisco GPL Violations:

We are in ongoing negotiating with Linksys/Cisco about this issue.
Information from Andrew Miklas and others has been very helpful to us in
our negotiations, and we encourage others to share with us any technical
information about this or any other GPL violation.

This isn't the first GPL violation we have dealt with; we've been
actively
enforcing the GPL for over ten years.  Our usual practice is not to
publicly announce details of ongoing violation negotiations, because we
find that private negotiation yields quicker and better cooperation.
By building a relationship with violators where we are helping them to
come
into compliance, we avoid having to fight in court, and are able to
spend
less resources per violation.  Our number one goal in any GPL violation
case is to get proper and full compliance with the license; everything
else is secondary.

GPL violations sometimes take time to resolve.  We wish that we could
force resolution quicker, but we haven't found a way to do that.  We
have,
however, discovered a variant of Brooks's Law: adding more lawyers to a
GPL violation usually makes it take longer.  Lawyers are reluctant to
admit to mistakes, because they fear it could be used against them.
Engineers and product managers are typically interested in fixing
mistakes, so we try our best to work with them first before escalating
to
legal teams on both sides.  Such escalation has happened on this
violation, so it will take additional time to resolve the matter.

In addition, we are leading a coalition of many copyright holders in the
WRT54G, as Linux is only one part of a large body of GPL'ed software in
the product.  We formed this coalition because, having done enforcement
cases for a product with a broad range of copyright holders before, we
have found that separate enforcement actions and/or law suits from
individual copyright holders make attainment of compliance more
difficult.

We will continue to do everything necessary to obtain full compliance on
this and any other products where violations can be confirmed.  On this
particular violation, we will keep the community informed when issues
come
up that impact the rights of everyone whose work is being distributed by
Cisco or any of its subsidiaries.

If you are a copyright holder on software in the WRT54G, or any other
Cisco product, you are welcome join this coalition.  Please email
<license-violation@fsf.org> for details.

Sincerely,

David Turner, GPL Compliance Engineer, FSF
Bradley M. Kuhn, Executive Director, FSF


-- 
-Dave Turner
GPL Compliance Engineer
Support my work: http://svcs.affero.net/rm.php?r=novalis&p=FSF

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-09-29 18:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 18:22 David Turner [this message]
2003-10-06  8:29 ` Linksys/Cisco GPL Violations David Woodhouse
2003-10-10 13:09   ` Florian Schirmer
2003-10-10 13:16     ` David Woodhouse
2003-10-10 13:26       ` Florian Schirmer
2003-10-10 13:39         ` David Woodhouse
2003-10-10 14:18           ` Florian Schirmer
2003-10-10 14:25             ` David Woodhouse
2003-10-11  5:37               ` Andre Hedrick
2003-10-11  6:35                 ` David Woodhouse
2003-10-11  7:03                   ` Andre Hedrick
2003-10-13  9:40                   ` Florian Schirmer
2003-10-10 15:11     ` [Linux-bcom4301-priv] " James Stevenson
2003-10-10 15:29       ` Sasa Ostrouska
2003-10-10 16:36         ` Florian Schirmer
2003-10-10 16:58           ` Luite Stegeman
2003-10-10 15:58     ` Rob Flickenger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1064859766.20847.33983.camel@banks \
    --to=novalis@fsf.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.