-
Notifications
You must be signed in to change notification settings - Fork 9
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
Reconsider liscense #41
Comments
Thanks for the feedback @mikevo . Before using the current CC0 license, I sought advice from the Reddit open source community and was advised to use this. What license do you suggest I should use? |
I think the problem with your current liscencing is that everyone can use your work under CC0 but I think what you want is that only the projects and NGOs that you assign (claiming process) a logo to can use it under this CC0 liscense and not everyone. I'm not a legal expert but I think you can liscense a single work in this case each logo with multiple liscenses at the same time as you are the copyright holder. Hence, it should be possible to use one liscence for everyone on all logos (this one imho schould be quite restrictive) and the CC0 liscence for the projects on the logo they claimed (without transferring the copyright to them). Otherwise the projects that claimed a logo ar not the only ones that can use the logo for basically everything. |
Before applying further liscences. You should read this article https://creativecommons.org/about/cclicenses/ |
@mikevo This is exactly what I thought I was doing. I guess I didn't articulate it well. By the way, feel free to make a pull request implementing your preferred method of licensing. I could do it, but it'll take a while for me to come back to this. |
I think you should reconsider the your liscense choice as CC0 allows anyone to use your logos for anything.
This contradicts your concept of "giving" logos to open source projects and NGOs as they are already public domain and can hence can be used without claiming by anyone which cannot simply be revoked.
The text was updated successfully, but these errors were encountered: