mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Danny Brow" <dan@fullmotions.com>
Cc: "Kernel-List" <linux-kernel@vger.kernel.org>
Subject: RE: Reporting GPL violations - a little OT
Date: Thu, 21 Oct 2004 13:53:57 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEPHPCAA.davids@webmaster.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410211311250.10582@twin.uoregon.edu>


> On Thu, 21 Oct 2004, Danny Brow wrote:
>
> > Just wondering where to report possible GPL violations.
>
> the authors of the software in question are the best place to start.
>
> joelja

	My opinion is that you should first report it to the violators. See if they
acknowledge the violation or argue that it's not a violation. If they
acknowledge the violation, see if they fix it. If they argue it's not a
violation, look at their argument and see if it's reasonable.

	If you are convinced that it really is a GPL violation and that the
violators either won't acknowledge it or acknowledge it and won't fix it,
then you should report it on the most appropriate public forum associated
with either GPL violations specifically or the application whose license is
being violated.

	IMO, for the Linux kernel, the LKML is appropriate once you've exhausted
direct contacts with the violator.

	DS



  parent reply	other threads:[~2004-10-21 21:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 20:06 Danny Brow
2004-10-21 20:12 ` Joel Jaeggli
2004-10-21 20:33   ` Danny Brow
2004-10-21 20:53   ` David Schwartz [this message]
2004-10-21 20:10 Danny Brow
2004-10-21 21:08 ` Denis Vlasenko
2004-10-26  0:50 ` Werner Almesberger

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=MDEHLPKNGKAHNMBLJOLKAEPHPCAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=dan@fullmotions.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®