-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License drafting #158
Draft
n8willis
wants to merge
4
commits into
master
Choose a base branch
from
license
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
License drafting #158
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f739d4e
Initial 'public specification license' added as LICENSE file.
n8willis 733a844
license: revise and clarify code-snippet and quotation language. Add …
n8willis f89e5a2
license: fix missing word in Implementation section; calrify that an …
n8willis 883cd63
license: regularize usage of 'these documents' vs 'the work'. Using '…
n8willis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(copied from the
git note
for 733a844 because it seems those are not visible on GitHub anymore)This commit fixes an error in the 'above/below' wording caused by me rearranging things. It also attempts to clarify the wording around permitting code-snippets to be reused without condition.
A lingering question is whether or not the license needs to specify that the covered bits are marked up with particular semantic tags. That would be easy to do for a fixed output, like HTML
<code>
,<pre>
, and<tt>
, but would not be very flexible if someone regenerated LaTeX output, for instance.Finally, this commit adds a 'do not make quotations of longer than 20% of the original work' clause to the quotation section. This is an arbitrary number, but the intent is to stop a potential bad actor from quoting 100% of the work in a comment and sneaking around the other terms that way. It may warrant further revision, since I am not certain that 20% is a useful number when all of the character tables and build documents are included.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(copied from the
git note
for 883cd63 because it seems those are not visible on GitHub anymore)The intent of the "these documents"/"the work" distinction here is that we want to be clear when enumerating permissions that pertain to the entire work, such as redistributing it, and still be clear when discussing activities that would only apply to one page/paragraph/idea. E.g., you might implement support for JUST ONE shaping model, so the Implementation section doesn't say you have to implement 'the work' in order to be in compliance. Not sure everyone will find that nuance useful, but they might.