Timeline for What if someone published program on invalid license and then fixed it?
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 27, 2023 at 14:06 | history | edited | Trish | CC BY-SA 4.0 |
added 186 characters in body
|
Jun 27, 2023 at 14:05 | comment | added | Trish | @Brandin Adding wrong copyright information is also copyright infringement of a different kind. law.cornell.edu/uscode/text/17/1202 | |
Jun 27, 2023 at 11:43 | comment | added | Brandin | Well, if there was no copyright information in the original version, then "forking" that version which has no information is technically allowed by GitHub. Of course, now I'm stuck -- definitely I don't have permission to put my own notice on that fork or add my own different license on that forked code. | |
Jun 27, 2023 at 11:32 | comment | added | Trish | @Brandin technically wrong: You do not grant them the ability to claim copyright - Removing copyright information or claiming copyright on something you have no copyright on is copyright infringement and not covered by the fork-license (which is enforceable) | |
Jun 27, 2023 at 10:38 | comment | added | Brandin | Yes this is true except for one caveat - on GitHub, at least - whenever you agree to be a member and to publish code there, one of the things you agree to in the Terms of Service is to let GitHub and other GitHib users to use (or "fork") your public code within their platform (regardless of the license that you mention explicitly, if any). | |
Jun 20, 2023 at 17:30 | vote | accept | Szyszka947 | ||
Jun 20, 2023 at 17:30 | comment | added | Szyszka947 | I'm that poor man :|. Thanks you, I can sleep calm! | |
Jun 20, 2023 at 15:51 | history | answered | Trish | CC BY-SA 4.0 |