-
Notifications
You must be signed in to change notification settings - Fork 24
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
Vendor-Neutral Channel Registry CEP #91
base: main
Are you sure you want to change the base?
Conversation
cep-channel-registry.md
Outdated
- Description | ||
- Channel dependencies, that link a given channel to other channels | ||
- Homepage and GitHub URL, Logo, etc. | ||
- Wether the channel is commercial, and where the Terms of Service are located |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add an example for that as well?
"homepage": "https://conda-forge.org", | ||
"github_url": "https://github.com/conda-forge", | ||
"logo_url": "https://conda-forge.org/assets/img/logo.png", | ||
"commercial": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"commercial" might not be enough to elaborate the complexity of terms of services, I'd suggest to instead add a legal
field, that would be an optional field to enable to describe what it is. Also, a terms_url
to point to the specific terms that are currently valid?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, legal
could be a mapping with license
, description
, terms_url
?
Co-authored-by: Daniel Holth <[email protected]>
Rendered version: https://github.com/wolfv/ceps/blob/channel-registry/cep-channel-registry.md