Reporting violations

[mr]

How about we create an easy to follow template? That way it should be
obvious what is required and what might be missing for someone before they
start reporting.

Cheers,

Alan

2008/11/22 Shane Martin Coughlan <coughlan at fsfeurope.org>

> 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.
>
> Thanks
>
> Shane
>
> --
> Shane Coughlan
> FTF Coordinator
> Free Software Foundation Europe
> Office: +41435000366 ext 408 / Mobile: +353858303486
> coughlan at fsfeurope.org
> Support Free Software > http://fsfe.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gpl-violations.org/pipermail/legal/attachments/20081122/17558f96/attachment.htm>