-
Notifications
You must be signed in to change notification settings - Fork 483
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
[WIP] Add rules on moving content to collections outside of Ansible #1971
base: devel
Are you sure you want to change the base?
Conversation
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Show resolved
Hide resolved
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Outdated
Show resolved
Hide resolved
|
||
For the community "catch all" collections, we have slightly different rules. We allow to move content out of community.general and community.network to other collections outside of Ansible under the following conditions: | ||
|
||
1. The new collection is appropriately licensed and does not require a CLA to contribute. |
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.
Instead of "does not require a CLA to contribute," can we say "follows the Contributor License Agreements policy" and make that a link to the the "Contributor License Agreements" section? There's more detail there about what constitutes a CLA and also that we allow the DCO.
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.
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Outdated
Show resolved
Hide resolved
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Outdated
Show resolved
Hide resolved
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Outdated
Show resolved
Hide resolved
docs/docsite/rst/community/collection_contributors/collection_requirements.rst
Show resolved
Hide resolved
I did some grammar policing, but this looks good to me, and I agree with the policy here. Thanks! |
Co-authored-by: Maxwell G <maxwell@gtmx.me>
This is basically the proposal of https://forum.ansible.com/t/5738/2.
I was not able to find a rule in the requirements that if content is moved out from collections in Ansible, that the resulting collection also has to be part of Ansible. Since the original discussions are more than two years old (ansible-community/community-topics#167), I'm missing the context... If someone remembers (or finds where this is mentioned in the requirements or elsewhere in the docs), please mention it here :)