[ Thanks to sakgarg
for this link. ]
“Some of the advice is common sense (suspected
violations are best handled in private, reported only to the
involved parties, and organizations such as GPL-Violations and the
appropriate branch of the Free Software Foundation), but reminders
are always useful, especially in the heat of the moment.“The guide illustrates that reporting a possible license
violation should be as specific as filing a bug report. Forwarded
email threads, if necessary, should only include pertinent
information. Links to the project, the parts of the code involved,
as well as the license by which the code is protected should be
included.”