From 8b4497c6dbfb126e50935e12296174d81d27b59c Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Tue, 11 Nov 2014 18:59:29 -0500 Subject: [PATCH] This may better appear here. --- compliance-guide.tex | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/compliance-guide.tex b/compliance-guide.tex index 9421941..256e5dd 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -1204,11 +1204,6 @@ There are several other issues that are less common, but also relevant in a GPL compliance situation. To those who face them, they tend to be of particular interest. -% FIXME-URGENT: integrate -Non-compliance with GPLv3 in the -distribution of Javascript on the Web is becoming more frequent -%FIXME-URGENT: END - \section{LGPL Compliance} \label{lgpl} @@ -1377,6 +1372,14 @@ with GPLv2, the license gives you clear provisions that you can rely on when you are forced to cut off support, service or warranty for a customer who has chosen to modify. +% FIXME-soon: write a full section on Javascript compliance. Here's a +% potentially useful one-sentence introduction for such a +% section. + +% Non-compliance with GPLv3 in the +% distribution of Javascript on the Web is becoming more frequent +%FIXME-soon: END + % FIXME-URGENT: integrate, and rewrite so it doesn't laud behavior that is % ultimately problematic.