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

Bevy Logo License issue #45

Closed
DGriffin91 opened this issue Dec 2, 2023 · 2 comments · Fixed by #46
Closed

Bevy Logo License issue #45

DGriffin91 opened this issue Dec 2, 2023 · 2 comments · Fixed by #46

Comments

@DGriffin91
Copy link

DGriffin91 commented Dec 2, 2023

The addition of the CC0 license in #42 implies that the bevy logo is CC0, but it is not.
From @cart:

I retain all rights to the logo atm. The license section explicitly calls out that the code is dual licensed under mit/apache.

https://discord.com/channels/691052431525675048/745355529777315850/995411630563262519

I think either the logo or the CC0 license needs to be removed from the template.

I would prefer the CC0 license removed personally as I think it creates a high possibility that people using this template will either include assets that are somewhat permissively licensed, but not CC0 and forget to remove the license, or they don't intend for their personal assets to be licensed this way.

@ickk
Copy link
Member

ickk commented Dec 3, 2023

I think the CC0 license itself is very appropriate for this kind of repository. We want users of this template to completely own the copyright to whatever game they make with it.

That said, ideally the licenses themselves wouldn't be necessarily be included in the copy of the template that a user gets however, as they may not think to remove them when required.

As a workaround, we could keep the license text somewhere external to the source code

@cart
Copy link
Member

cart commented Dec 3, 2023

Yeah I think the Bevy logo should be removed to avoid confusion.

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

Successfully merging a pull request may close this issue.

3 participants