[PR #1971/efb2c671 backport][stable-2.18] Add rules on moving content to collections outside of Ansible #2053
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #1971 as merged into devel (efb2c67).
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 :)