Last active
August 9, 2016 07:01
-
-
Save pathway27/9d2c422b45d89f1cc77df3ba3343a5a6 to your computer and use it in GitHub Desktop.
Licensing and Copyright when Porting (Derivative Works)
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
I've read quite a bit online. | |
I really don't want to pay a lawyer on FOSS license use or copyright when it has to do with open-source and Free Software. | |
My aims were to port some sofware licensed under GPLv2 to a different platform. | |
TLDR: | |
Include original Copyright license and disclaimer, and add your own copyright for the port/derivative. | |
http://opensource.stackexchange.com/questions/2794/project-port-to-another-language-dealing-with-copyright-notices-when-using-ap/2795#2795?newreg=93677e403e5e4583a9996a38450215f5 | |
http://programmers.stackexchange.com/questions/324465/licensing-when-porting | |
No one actually cares... esp. in the homebrew scene. | |
A “derivative work” is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications which, as a whole, represent an original work of authorship, is a ''derivative work''. | |
That last line has a lot of synonyms each with different connotations. | |
the l |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment