Clear and unambiguous time periods for source availability#4
Open
farnz wants to merge 1 commit intopjakma:masterfrom
Open
Clear and unambiguous time periods for source availability#4farnz wants to merge 1 commit intopjakma:masterfrom
farnz wants to merge 1 commit intopjakma:masterfrom
Conversation
This closes off two gaps: 1. It was unclear how long I needed to make source available if I distributed a binary; now it's clear that source must be available for 2 years. 2. The intent of 3.1c is to ensure that I can get modifications; however, if the software is such that the results are useful years after it ran, I could deploy and publish modifications, use the software, get my results, shut down the deployment, wait 2 years after the deployment started, get rid of the modified source and crow about my results. You then don't get the benefit of my modifications, even though I'm compliant.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This closes off two gaps:
It was unclear how long I needed to make source available if I distributed a binary; now it's clear that source must be available for 2 years.
The intent of 3.1c is to ensure that I can get modifications; however, if the software is such that the results are useful years after it ran, I could deploy and publish modifications, use the software, get my results, shut down the deployment, wait 2 years after the deployment started, get rid of the modified source and crow about my results. You then don't get the benefit of my modifications, even though I'm compliant.