Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Question about open sourcing and protecting art

A topic by RKillen created Mar 17, 2024 Views: 149 Replies: 6
Viewing posts 1 to 4
Submitted

Hi all, I created my first git at the request of a fellow jammer. I am fine with open-sourcing the project.

My question is this: What license (or licensing combo) should I consider if I want to explicitly make my code available for use but want to maintain full rights over my art and music?

Understand that I am a novice programmer, so nobody will actually want any of my code, but I like to do things right.

Submitted

I'd like to do that as well, but I don't have many info about it. I will make some researches and notify you if I find something useful!

Submitted

I'll do the same

Submitted

I'm in the same boat. I was checking the Creative Commons licenses, and this could be an option:

https://creativecommons.org/licenses/by-nc-nd/4.0/

CC BY-NC-ND 4.0 Deed

Attribution-NonCommercial-NoDerivs 4.0 International

You are free to:

  1. Share — copy and redistribute the material in any medium or format
  2. The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

  1. Attribution — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  2. NonCommercial — You may not use the material for commercial purposes .
  3. NoDerivatives — If you remix, transform, or build upon the material, you may not distribute the modified material.
  4. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Submitted

Thank you for the very in depth reply! Very informative. And much appreciated.

Submitted (2 edits)

You can have different licenses for each different file/folder in your project. Github can generate license files for you as well, but it's good practice to put on your README.md all the licenses you have too, for example you can look at my repository to see how you can license everything correctly, just beware because my assets are all creative commons, so take care not to use the same licenses I did.

There are a bunch of open source licenses, the MIT is the simplest and easiest one to use, it just requires the users to keep the license file if they take your code. Another famous one is the GPL-2.0, which requires the user to also publish their work under the same license if they use your code. If you want to have full rights over your art and music, you should probably make them proprietary and write your legal notice with your conditions.

Submitted (1 edit)

Excellent advice. Thank you!

I took a look at your license and readme files. They were incredibly helpful. Thank you again!