-
Notifications
You must be signed in to change notification settings - Fork 13
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
Lack of a license #5
Comments
I don't believe that a packaging recipe is copyright protected, and it would be impossible to enforce its licensing and detect possible violators. The packaging was initially heavily influenced by Arch Linux official and AUR packages. These don't have or require a license, so I see no reason to add one.
The actual code here comes as patch files, and those have git commit message and author details, or a link to where it came from, so the original license should be applied. Icons mainly come from the upstream source, or official distributed binaries, so having them here for packaging falls under fair use. |
The issue is less enforcing the licensing, more making sure no potential issues arise. I would appreciate some clear terms on which I can use the recipes. |
You can treat the packaging as public domain, and use it as you like. |
Probably best to add a license (like the CC0) to have some clear terms on which people can utilize the manifests published here. Without one, any content is considered proprietary by platforms such as GitLab.
The text was updated successfully, but these errors were encountered: