Personal tools

Momentary Compliance

From GPLv3 Wiki

(Difference between revisions)
Revision as of 17:14, 3 March 2006
syeates (Talk | contribs)
added test case
← Previous diff
Current revision
brett (Talk | contribs)
offer an explanation of the 60-day window
Line 1: Line 1:
-Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise . Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period.+Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise an appropiate HTTP error code is returned. Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period.
- +
 +:This isn't how the 60-day window in section 8 works. What it says is that after you have corrected a violation, copyright holders only have a 60-day window in which to terminate your rights under the license. So, in this case, once Party C notices that Party B is not in compliance right now, they can notify Party A, who will have 60 days to revoke Party B's rights -- even if Party B has permanently fixed the violation since then. --[[User:brett|brett]] 12:42, 6 March 2006 (EST)
Back to [[Test Cases]] Back to [[Test Cases]]

Current revision

Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise an appropiate HTTP error code is returned. Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period.

This isn't how the 60-day window in section 8 works. What it says is that after you have corrected a violation, copyright holders only have a 60-day window in which to terminate your rights under the license. So, in this case, once Party C notices that Party B is not in compliance right now, they can notify Party A, who will have 60 days to revoke Party B's rights -- even if Party B has permanently fixed the violation since then. --brett 12:42, 6 March 2006 (EST)

Back to Test Cases