Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upCopyright removed #1
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
I'm not a lawyer, but as far as I know, anybody should be able to fork MIT license projects and attach a stricter license. I'll look for a way to resolve this issue.
crocket
commented
May 9, 2017
•
|
I'm not a lawyer, but as far as I know, anybody should be able to fork MIT license projects and attach a stricter license. I'll look for a way to resolve this issue. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rjc
May 9, 2017
Like I've stated above, one can do whatever they wish with the software as long as they don't claim they're the original author - I specifically mentioned copyright, not license, violation.
rjc
commented
May 9, 2017
|
Like I've stated above, one can do whatever they wish with the software as long as they don't claim they're the original author - I specifically mentioned copyright, not license, violation. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
Although I think the commits serve as copyrights according to C4, I added copyrights to README.
C4 states that
All patches are owned by their authors. There SHALL NOT be any copyright assignment process.
Thus, the mere existence of their commits automatically gives them copyrights.
crocket
commented
May 9, 2017
•
|
Although I think the commits serve as copyrights according to C4, I added copyrights to README. C4 states that
Thus, the mere existence of their commits automatically gives them copyrights. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
I just realized that C4 automatically assigns copyrights to commit authors. Thus, I removed copyright from README to remove redundancy.
Do you think it's good?
crocket
commented
May 9, 2017
•
|
I just realized that C4 automatically assigns copyrights to commit authors. Thus, I removed copyright from README to remove redundancy. Do you think it's good? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rjc
May 9, 2017
I know nothing of C4 but the commits, which you have mentioned, are only available if ones is to use a repository with all of its history intact. None of that information will be available in a release tarball.
The easiest way to avoid any issues is to retain the current license :^)
Otherwise you may need to copy the old copyright notices, most likely with its old license, into each and every source file which contained the reference to the LICENSE file - you can of course keep the refeference as it already points to the new license... but I'm not a lawyer either :^P
rjc
commented
May 9, 2017
|
I know nothing of The easiest way to avoid any issues is to retain the current license :^) Otherwise you may need to copy the old copyright notices, most likely with its old license, into each and every source file which contained the reference to the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
If you think this project got the copyrights wrong, you could submit a pull request.
This copyright thing is beyond my mental bandwidth for now at least.
I'll merge a pull request anyway if it doesn't look crazy.
crocket
commented
May 9, 2017
•
|
If you think this project got the copyrights wrong, you could submit a pull request. This copyright thing is beyond my mental bandwidth for now at least. I'll merge a pull request anyway if it doesn't look crazy. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rjc
May 9, 2017
Copyright is a serious matter and I wouldn't leave it like that as this usually doesn't end well for the fork.
Just my $0.02.
rjc
commented
May 9, 2017
|
Copyright is a serious matter and I wouldn't leave it like that as this usually doesn't end well for the fork. Just my $0.02. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
Although I could add it back myself, I would like a contributor to add it.
I prefer it that way. I'll wait for some time for a contributor feedback in the form of pull request.
Maybe, if no one sends a pull request for a while, I'll add it back.
crocket
commented
May 9, 2017
•
|
Although I could add it back myself, I would like a contributor to add it. Maybe, if no one sends a pull request for a while, I'll add it back. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
May 9, 2017
I am very new to this copyright business, so I was somewhat careless.
FRIGN, a suckless member, told me it was necessary to have the original copyright information below MPLv2. I'll do that very soon and close this.
crocket
commented
May 9, 2017
•
|
I am very new to this copyright business, so I was somewhat careless. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
crocket
commented
May 9, 2017
|
This one is closed by d56c018 |
rjc commentedMay 9, 2017
Hi,
In the last commit you had changed the license from
MIT/Xone to anMPLv2.0.At the same time you had removed all of the copyright notices of the original authors.
The original license clearly states that you're to do whatever you like with the software, as long as you include said copyright notice.
The source files only contain reference to the
LICENSEfile.It looks like you might be in violation of the original authors' copyright.
Regards,
rjc