Skip to content

Conversation

@patchback
Copy link

@patchback patchback bot commented Oct 24, 2024

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 :)

* Add rules on moving content to collections outside of Ansible.

* Apply suggestions from code review.

Co-authored-by: Maxwell G <[email protected]>

* One more from gotmax23.

* Reference section on CLAs.

---------

Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit efb2c67)
@patchback patchback bot requested a review from a team as a code owner October 24, 2024 18:32
@ansible-documentation-bot ansible-documentation-bot bot added the sc_approval This PR requires approval from the Ansible Community Steering Committee label Oct 24, 2024
@samccann samccann merged commit b007fce into stable-2.16 Oct 24, 2024
8 checks passed
@samccann samccann deleted the patchback/backports/stable-2.16/efb2c671ffb0b083025d5cb384555c0f1f261678/pr-1971 branch October 24, 2024 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sc_approval This PR requires approval from the Ansible Community Steering Committee

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants