Changeset - 6d5ca098a11e
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-20 19:40:18
bkuhn@ebb.org
Reword these two paragraphs.
1 file changed with 12 insertions and 20 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -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
 
source package at the same time to enable effective seeding and distribution.
 

	
 
% FIXME: rewrite a bit.
 

	
 
We have made two changes that recognize and facilitate distribution of
 
covered works in object code form using BitTorrent or similar peer-to-peer
 
methods.  First, under new subsection 6e, if a licensee conveys such a work
 
using peer-to-peer transmission, that licensee is in compliance with section
 
6 so long as the licensee knows, and informs other peers where, the object
 
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.
 
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.
 

	
 
Second, GPLv3\S9 also clarifies 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-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!
0 comments (0 inline, 0 general)