11-licensing: Punt to choosealicense.com, the OSI, and the FSF #229
Conversation
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
No changes to the thrust, but this commit cleans up a few details. Once we've introduced "creative work" and provided some examples, stick to the more general term for the rest of the paragraph (instead of shifting between "creative work", "code", "source code", etc.). Drop the "has not waived" sentence. We just said it's copyright, and the distinction between licencing and "advertis[ing] as freely available" isn't clear to me. In the "reusing" sentence, the threat is the copyright holders, which may not be the original authors (the authors may have assigned their copyright to another party). And the unlicensed infringement will have always been illegal, it doesn't become illegal when the copyright holders start enforcing their copyright.
[1] currently lists 10 criteria, and they get deeper than we can go in five to ten minutes (e.g. "License Must Be Technology-Neutral"). [1]: http://opensource.org/osd
Don't list licenses here or sumarize licenses. Instead, just paraphrase the main choosealicense.com critera, suggest folks choose a common license, and point them at reliable resources.
This is orthogonal to licensing, although it makes life easier for folks consuming CC BY work.
This was referenced Feb 4, 2016
"project repository" -> "repository"
Also add a link to the file in GitHub.
|
On Sun, Mar 06, 2016 at 07:26:04AM -0800, Ivan Gonzalez wrote:
I left off your line-wrapping commit (fccdb23) and cherry-picked your |
|
Perfect! Thanks a lot! |
iglpdc
added a commit
that referenced
this pull request
Mar 6, 2016
11-licensing: Punt to choosealicense.com, the OSI, and the FSF
zkamvar
pushed a commit
that referenced
this pull request
May 8, 2023
11-licensing: Punt to choosealicense.com, the OSI, and the FSF
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
And other tightening for the licensing topic. Details in the
individual commit messages and background discussion in #227. The
basic idea is that we should lay the ground work for what licensing is
for and the sorts of things covered by licenses, but not get down to
the level of which licenses to choose. That information is covered in
external sources that have more eyeballs, lawyers, and UI designers
involved than we'll have.