Mention initial copyright year and add contributors to copyright #508
Conversation
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
Collaborator
|
@hemanth, thoughts on this? Makes sense to me but you've been a maintainer longer than I have, so I wanted to confirm. |
Collaborator
|
Yup it's absolutely right. As per the second point only 2010 must be sufficient.
I am sure @tj wouldn't mind to have contributors in the copyright, given that he has handed over even larger projects like express to the FOSS world, he wouldn't mind about this change. |
I am not a lawyer but according to http://www.copyright.gov/circs/circ01.pdf (See screenshot of relevant section below), mentioning the first year of publication in the copyright is a good thing  Mentioning 2010 as the first release happened at that time - https://github.com/tj/git-extras/releases/tag/0.0.1 Also adding `Contributors` to copyright because TJ Holowaychuk is not the only person owning copyright for the whole project. The copyright is collectively owned by all contributors, or more precisely: every contributor owns a copyright on the code he or she has contributed. The only way to retain full copyright over code is to ask for signing contributor's agreement before merging in changes. This is, in fact, what some companies who license commercially their free software do.
Contributor
Author
|
Updated the pull request to mention 2010 alone (removed the year range) |
Owner
|
👍 |
hemanth
added a commit
that referenced
this pull request
Jan 30, 2016
Mention initial copyright year and add contributors to copyright
Collaborator
tardypad
pushed a commit
to tardypad/git-extras
that referenced
this pull request
Jul 13, 2016
Mention initial copyright year and add contributors to copyright
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I am not a lawyer but according to http://www.copyright.gov/circs/circ01.pdf (See screenshot of relevant section below), mentioning the first year of publication in the copyright is a good thing
Mentioning 2010 as the first release happened at that time - https://github.com/tj/git-extras/releases/tag/0.0.1
Also adding
Contributorsto copyright because TJ Holowaychuk is not the only person owning copyright for the whole project. The copyright is collectively owned by all contributors, or more precisely: every contributor owns a copyright on the code he or she has contributed.The only way to retain full copyright over code is to ask for signing contributor's agreement before merging in changes. This is, in fact, what some companies who license commercially their free software do.