Reporting violations

[Loic Dachary]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shane Martin Coughlan wrote:
> Hi all
>
> It would be really useful violation reports could contain:
>
> (1) The name of the project code that may have been violated (2) A
> statement regarding what licence this code is under (3) A link to
> the project site (4) The name and website of the party who may be
> violating the code (5) The reason why a violation is believed to
> exist
>
> Forwarding big threads and so on makes it difficult to assess the
> situation.  Bare facts first, then we can ask questions where
> required.
Hi,

Regarding (5) I often suggest that the violation is reported as a
HOWTO. The HOWTO explains what must be done to get the facts and
concludes with the list of things that are missing or modified
contrary to the licensing terms. I then obey the HOWTO and submit the
result to a lawyer. In rare cases (such as a violation involving a
device connected to the internet), it may be difficult to run the
HOWTO, but most of the time it is trivial and the result can be used
as-is.

Cheers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkqZTEACgkQ8dLMyEl6F210SgCgt40jvAsHHmqHNwN4fnJvQ+wt
OWwAn2iPW63GEwyZq04pdaX5j3C8XQ94
=Oowl
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: loic.vcf
Type: text/x-vcard
Size: 289 bytes
Desc: not available
URL: <http://lists.gpl-violations.org/pipermail/legal/attachments/20081124/01c34ca4/attachment.vcf>