[Vote ends 2026-10-08] Proposal: trim and restrict the Ansible community package down to a Steering-Committee-selected set

Thanks everyone for your comment!
How about the following long term plan (taking trimming down and backwards compatibility into consideration), i.e. a sequence of topics to eat the elephant one bite at a time:

  1. In this proposal: We vote for/against stopping including new collections
  2. Next topic (if topic 1 resulted in “for stopping”): We discuss and vote on specific criteria for inclusion. All will get reflected in the current inclusion policy doc on docs.ansible.com
  3. Next topic (if previous topic resulted in “for”): We discuss trimming down the package to core and a limited set of collections. We’ll use the criteria we’ve developed in the previous topic. We’ll vote on it. If not supported, we will not proceed further.
  4. Next topic (if trimming down in topic 3 is supported): we’ll discuss community.general collection split, vote.
  5. Next topic (if trimming down in topic 3 is supported): We’ll discuss and vote on a deprecation plan for all collections we haven’t decided to leave in the package.

What does everyone think?