The following is an updated version of my proposal from Should we allow moving content out of community.general and community.network to collections that are not part of Ansible? · Issue #167 · ansible-community/community-topics · GitHub,
We allow to move content out of c.g and c.n to other collections outside of Ansible under the following conditions:
- The new collection is appropriately licensed and does not require a CLA to contribute.
- None of the contributors who contributed to the content in the last 6 months objects in a four-weeks period after the plan to deprecate the module has been announced.
- There is a deprecation period of at least 6 months during which deprecation warnings are shown. The deprecation notice must mention that the content is moved to a collcetion outside the Ansible community package, and that users need to install that collection separately.
- If community members or contributors bring up good reasons in these 6 months to not do the move, the Steering Committee will discuss these and vote on them before the content is removed.
Redirects are only added if full backwards compatibility can be ensured. If they are not used, tombstoning has to be used, and the tombstone message needs to explicitly mention the new collection and that the content in the new collection is not fully backwards compatible.
What do you think, in particular @SteeringCommittee? Does this sound reasonable / acceptable / …?