-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
Add CC license in readme #3770
Add CC license in readme #3770
Conversation
- Update TOC to include Support and emojis - Add more badges - Minor adjustment to information hierarchy
- Add Go badges - Add a workflow status badge (feel free to change)
Added Creative Commons license to resolve owncast#3422
There's a larger issue filed at #3422 to work on this, and make sure we have actual documentation around our assets and its license. I think a badge can be fine, but I'm not sure it's that useful without something more substantial that can be referenced. If the badge displays it has a license, but there's no actual place that's written down, I don't think that gets us quite where we need to be. It's also more than just the docs we need to worry about. Things like the logo, custom icons, video content we make, etc. These should all have a license as well. But I also haven't put any thought into what the format is that makes sense to do such a thing. What do you think? |
I'm not sure which custom icons we have. But according to CC FAQ website, they said that it is not recommended to use the license on logo. Maybe I understand it wrongly?
Other than putting it on the readme, can we put it on the footer owncast.online site too so that it is always there? Looking at CC website footer https://chooser-beta.creativecommons.org/ and wikipedia, the CC license notice shows up on every page of the website. That's if we are licensing or marking the whole page or blog, you can paste the code at the bottom of the page.
|
Creative Commons license format adheres to Creative Commons LICENSE CHOOSER
We don't have many custom images, just a couple for social actions like follow, share like: https://owncast.online/components/?path=/docs/owncast-frontend-assets-images--docs. We also have misc images used for random places that aren't used within the product itself. We don't currently have a trademark on our logo, or even an application for it, so as it stands it's completely unlicensed and ambiguous. It seems like a CC license would at least define what is allowed with it, but I could be wrong. |
So for those created graphics, would need to Add a metadata tag to each graphic asset file, indicating the chosen CC license. Though I'm not sure how to go about doing so in storybook. I can think of marketing assets as one of the items to have CC license, not sure if people would use follow, like, repost graphics on their sites. Since the icons is primarily used in our product as button icons, I don't think it needs license because I can't think of a use case being used outside of Owncast. This could help with CC license notice: https://chooser-beta.creativecommons.org/
|
#3422
Update readme to include CC license as we have custom assets