Move this text around to the right place before rewriting it.
This commit is contained in:
parent
97deccc4d1
commit
7b2a124827
1 changed files with 24 additions and 20 deletions
44
gpl-lgpl.tex
44
gpl-lgpl.tex
|
@ -2549,6 +2549,30 @@ requirements. Specifically, GPLv3~\S2\P2 guarantees the basic freedoms of
|
|||
privately modifying and running the program.
|
||||
|
||||
% FIXME: transition, and some word smith
|
||||
|
||||
GPLv3 now gives an explicit permission for a client to provide a copy of
|
||||
its modified software to a contractor exclusively for that contractor to
|
||||
modify it further, or run it, on behalf of the client. However, the
|
||||
client can only exercise this control over its own copyrighted changes
|
||||
to the GPL-covered program. The parts of the program it obtained from
|
||||
other contributors must be provided to the contractor with the usual GPL
|
||||
freedoms.
|
||||
|
||||
This permission is stated in section 2. It permits a user to convey
|
||||
covered works to contractors operating exclusively on the user's behalf,
|
||||
under the user's direction and control, and to require the contractors
|
||||
to keep the user's copyrighted changes confidential, but only if the
|
||||
contractor is limited to acting on the user's behalf, just as the user's
|
||||
employees would have to act.
|
||||
|
||||
The strict conditions in this provision are needed so that it cannot be
|
||||
twisted to fit other activities, such as making a program available to
|
||||
users or customers. By making the limits on this provision very narrow,
|
||||
we ensure that in all other cases the contractor gets the full freedoms
|
||||
of the GPL.
|
||||
|
||||
% FIXME: transition, and some word smith
|
||||
|
||||
The explicit prohibition of sublicensing ensures that enforcement of the GPL
|
||||
is always by the copyright holder. Usually, sublicensing is regarded as a
|
||||
practical convenience or necessity for the licensee, to avoid having to
|
||||
|
@ -2633,26 +2657,6 @@ activities is not clear and may depend on variations in copyright law.
|
|||
The practices seem basically harmless, so we have decided to make it
|
||||
clear they are permitted.
|
||||
|
||||
GPLv3 now gives an explicit permission for a client to provide a copy of
|
||||
its modified software to a contractor exclusively for that contractor to
|
||||
modify it further, or run it, on behalf of the client. However, the
|
||||
client can only exercise this control over its own copyrighted changes
|
||||
to the GPL-covered program. The parts of the program it obtained from
|
||||
other contributors must be provided to the contractor with the usual GPL
|
||||
freedoms.
|
||||
|
||||
This permission is stated in section 2. It permits a user to convey
|
||||
covered works to contractors operating exclusively on the user's behalf,
|
||||
under the user's direction and control, and to require the contractors
|
||||
to keep the user's copyrighted changes confidential, but only if the
|
||||
contractor is limited to acting on the user's behalf, just as the user's
|
||||
employees would have to act.
|
||||
|
||||
The strict conditions in this provision are needed so that it cannot be
|
||||
twisted to fit other activities, such as making a program available to
|
||||
users or customers. By making the limits on this provision very narrow,
|
||||
we ensure that in all other cases the contractor gets the full freedoms
|
||||
of the GPL.
|
||||
|
||||
\section{GPLv3~\S3: What Hath DMCA Wrought}
|
||||
\label{GPLv3s3}
|
||||
|
|
Loading…
Reference in a new issue