Re: Final text of GPL v3
On Sat, 30 Jun 2007, Francesco Poli wrote:
> > When you convey a covered work, you waive any legal power to forbid
> > circumvention of technological measures to the extent such
> > circumvention is effected by exercising rights under this License with
> > respect to the covered work,
> This clause is troublesome, as it seems to be overreaching. For
> instance, it could be interpreted as covering legal powers to forbid
> "computer crimes" such as unauthorized intrusion into computer systems.
> E.g.: suppose that the covered work is a vulnerability scanner, or
> password cracker, or anyway a tool that could be used (among other
> things) to break into other people's computers. Using that tool in this
> manner is exercising a right "under this License"
Using a tool is not exercising a right under the license. The license
concerns itself only with copying and modification. (It is not an end
user license agreement.) Beyond that, I agree with MJ's analysis, but
I think the point I raised is an important additional one.
> Waiving legal rights can be seen as a fee: this clause could fail
All free licenses, and especially all copyleft licenses, require the
waiver of certain legal rights (such as the right to sue for copyright
infringement). The requirement in copyleft to provide source code can
also be seen as a fee--in fact, this has been cited as a reason for
considering the GPLv2 valid, enforcible and non- discriminatory with
respect to anti-trust law. If waving legal rights is a problem, we
have no licenses left. If something that merely *can* "be seen as a
fee" is a problem, then all copylefts are non-free.
> > d) If the work has interactive user interfaces, each must display
> > Appropriate Legal Notices; however, if the Program has interactive
> > interfaces that do not display Appropriate Legal Notices, your
> > work need not make them do so.
> Clause 5d is definitely worse than the corresponding clause 2c in
Are you talking about the missing "when started running...in the most
ordinary way"? That was highly ambiguous; this has the advantage of
being clear and direct, and I can't think of any circumstances where
it could actually be considered worse. I actually think the new
wording is a great improvement, as it closes a highly ambiguous
loophole (the worst kind).
> What is more awkward is that it seems that when a non-interactive
> work is modified so that it becomes an interactive work, the
> modifier is *compelled* to implement these features in *any* newly
> created interactive interface.
Um, GPLv2 has basically the same requirement: "If the modified program
normally read commands interactively when run, you must cause it...to
print or display an announcement...." The *only* exception listed is
"if the Program itself is interactive but does not normally print such
an announcement, your work based on the Program is not required to
print an announcement." The only difference I see is the removal of
"normally", which, like "the most ordinary way" is rather ambiguous.
I'm sorry, but I really don't see how this is a freeness issue *if* we
consider the GPLv2 to be a free license. The difference between these
requirements is *so* small that I don't see how anyone could accept
the one and reject the other.
Chris Waters | Pneumonoultra- osis is too long
firstname.lastname@example.org | microscopicsilico- to fit into a single
or email@example.com | volcaniconi- standalone haiku