Rockbox Technical Forums

Rockbox General => Rockbox General Discussion => Topic started by: tirred on February 04, 2021, 10:51:34 AM

Title: Help with releasing code translations
Post by: tirred on February 04, 2021, 10:51:34 AM
I recently converted some rockbox code into another language as a library. Aside from crediting rockbox as the source, I'm assuming my code also needs to be released under GPLv2?  Do I just need to drop a LICENSE file in the root of the repo?

Thanks for any help!
Title: Re: Help with releasing code translations
Post by: saratoga on February 04, 2021, 01:01:01 PM
Yes, if you used our GPL code, you need to keep the GPL license.  Aside from that, you don't need to do anything else. 

A LICENSE file is a good idea,  you can also put the license at the top of the files.
Title: Re: Help with releasing code translations
Post by: tirred on February 04, 2021, 01:44:58 PM
I've always been confused about LICENSE vs license at the top of the file. Is it recommended to do both? Personally, I don't see the sense in gunking up code files with a block of static text across them all. I just notice a lot of projects tend to do both.
Title: Re: Help with releasing code translations
Post by: saratoga on February 04, 2021, 04:11:15 PM
I think it is just a matter of preference, but I like to put at least a note in the header if code has a particular license.
Title: Re: Help with releasing code translations
Post by: speachy on February 04, 2021, 05:04:14 PM
Each individual code file could be under a separate license (eg the stuff you got from rockbox is GPLv2+, but you might have got code from somewhere else that was, for example, BSD or GPLv3)

But the top-level LICENSE file should describe what applies to the overall software package.  Which presumably needs to be GPLv2 (or v3), given that you incorporated GPL code from rockbox...
Title: Re: Help with releasing code translations
Post by: tirred on February 04, 2021, 05:17:14 PM
Awesome! Thank you both so much!