Changeset - 21aff912c8b8
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 6 years ago 2018-03-24 02:58:34
bkuhn@ebb.org
Parity with two phrases already used in AGPLv3's main body.

AGPLv3§2 uses the phrase "output from running a covered work", so we use the
same phrase here. §6(e) already uses the phrase "general public", and of
course "propagate" is a defined term from AGPLv3§0.

This reworked definition of "Covered Output" better normalizes its definition
to fit the standard terminology of AGPLv3, and also removes the 'deployed on
a website'. We actually don't want to create the idea that deploying on the
website is the only way to be eligible for the additional permission. The
key issue is to assure that any items that receive the additional permission
are distributed to the general public, as we want "one last step" of Affero
requirement for the Covered Output, which only once available to the public
can then be combined with other software more liberally.
1 file changed with 3 insertions and 2 deletions:
0 comments (0 inline, 0 general)
AGPLv3-Web-Template-Output-Additional-Permission.txt
Show inline comments
...
 
@@ -7,8 +7,9 @@ references this Additional Permission.
 

	
 
1. DEFINITIONS
 

	
 
"Covered Output" means a covered work in the HTML, Javascript, and CSS languages generated by
 
the Program that are deployed to create a website and distributed publicly.
 
"Covered Output" means a covered work in the HTML, Javascript, and/or CSS
 
languages, that was output from running a covered work and is propagated to
 
the general public.
 

	
 
The "Output Licenses" are, for covered works written in HTML, the Creative Commons
 
Public Domain Dedication 1.0 Universal or any later version as published by
0 comments (0 inline, 0 general)