Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License issue with new "Progressive style" track #55

Open
gibmat opened this issue Aug 4, 2024 · 2 comments
Open

License issue with new "Progressive style" track #55

gibmat opened this issue Aug 4, 2024 · 2 comments

Comments

@gibmat
Copy link

gibmat commented Aug 4, 2024

#54 added a new "Progressive style" track from Approaching Nirvana titled "Sonar". Unfortunately, this track is not licensed as CC-BY-SA-4.0. Approaching Nirvana does have a licensing page on their site.

I found the following statement on a YouTube video that they recently uploaded:

I'm thrilled to have this song included in the in-development build of OpenRCT2. Roller Coaster Tycoon 2 is a game I played a ton of as a kid and it's cool to have my music involved with the RCT2 community. Sonar is part of the "progressive" style in the music section of OpenRCT2.

So, that's a good indication that the author approves of this use of their work.

Correcting the issue

At a minimum, a written statement by Approaching Nirvana needs to be included with the track that proper permission has been given to use it in the OpenRCT2 project.

Ideally, Approaching Nirvana would agree to dual-license this track as CC-BY-SA-4.0 to match the rest of the tracks in this repo. If not, an appropriate statement will need to be added to the repo's COPYING file as well.

I know it can feel like nit-picking over things like this, but it's important to ensure proper attribution and licensing information is available for the various assets used by OpenRCT2.

@karst
Copy link
Member

karst commented Aug 17, 2024

Hia! Sorry about the confusion, this track is licensed CC BY-SA 4.0 unlike his other music. We disclosed this in DM on discord.

@gibmat
Copy link
Author

gibmat commented Sep 1, 2024

Great, thanks for the clarification! It would probably be good it there could be a note in the repo documenting this discussion just so there's no confusion at some point in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants