Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Reword these two paragraphs.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 15:40:18 -04:00
parent 5111178260
commit 6d5ca098a1
1 changed files with 11 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
gpl-lgpl.tex
View file

@ -2893,26 +2893,18 @@ transmission time. Third, in current practice, CCS packages themselves tend
-- thus, there generally will be too few participants downloading the same -- thus, there generally will be too few participants downloading the same
source package at the same time to enable effective seeding and distribution. source package at the same time to enable effective seeding and distribution.
% FIXME: rewrite a bit. GPLv3~\S6(e) addresses this issues. If a licensee conveys such a work of
object code using peer-to-peer transmission, that licensee is in compliance
with GPLv3~\S6 if the licensee informs other peers where the object code and
its CCS are publicly available at no charge under subsection GPLv3~\S6(d).
The CCS therefore need not be provided through the peer-to-peer system that
was used for providing the binary.
We have made two changes that recognize and facilitate distribution of Second, GPLv3\S9 also clarifies that ancillary propagation of a covered work
covered works in object code form using BitTorrent or similar peer-to-peer that occurs as part of the process of peer-to-peer file transmission does not
methods. First, under new subsection 6e, if a licensee conveys such a work require acceptance, just as mere receipt and execution of the Program does
using peer-to-peer transmission, that licensee is in compliance with section not require acceptance. Such ancillary propagation is permitted without
6 so long as the licensee knows, and informs other peers where, the object limitation or further obligation.
code and its Corresponding Source are publicly available at no charge under
subsection 6d. The Corresponding Source therefore need not be provided
through the peer-to-peer system that was used for providing the binary.
Second, we have revised section 9 to make clear that ancillary propagation of
a covered work that occurs as part of the process of peer-to-peer file
transmission does not require acceptance, just as mere receipt and execution
of the Program does not require acceptance. Such ancillary propagation is
permitted without limitation or further obligation.
% FIXME: where does this go?
Informing the peers is clearly enough; what seemed to be an additional
knowledge requirement was superfluous wording.
% FIXME-LATER: Would be nice to explain much more about interactions between % FIXME-LATER: Would be nice to explain much more about interactions between
% the various options of GPLv3~\S6(a-e), which might all be in play at once! % the various options of GPLv3~\S6(a-e), which might all be in play at once!