The current collection inclusion requests are now handled mostly by Andersson007.
There’s not much interest to do other required reviews neither from the Steering Committee nor from the community. This causes delays in inclusion requests approval and including the collections in the package, which, in turn, might cause frustration on the collection maintainer side.
Future of the package: Also the Ansible community package as it is now is questioned from time to time by community members including by the Steering Committee members. Such a discussion is happening now.
It can hypothetically affect the inclusion process but even if the package will be abolished / trimmed down to core + a few core collections, the inclusion process will likely evolve to a community-approved collections review process with a Galaxy badge and their docs presence on docs.ansible.com as rewards and motivation for collection developers.
What can be done from my perspective (see the stories and their sub-tasks):
Optimize the process, experiment. Now one attempt is under way on the forum.
Optimize the requirements (it’s imo time to update them: kick out irrelevant ones and maybe add some new)
Optimize the related SC policies
Some natural changes to the collection requests review phenomenon that can potentially come from the future of the Ansible package topic mentioned above.
Andersson007
commented
5 months ago
Epic: Optimize collection inclusion
Background
The current collection inclusion requests are now handled mostly by Andersson007. There’s not much interest to do other required reviews neither from the Steering Committee nor from the community. This causes delays in inclusion requests approval and including the collections in the package, which, in turn, might cause frustration on the collection maintainer side.
Future of the package: Also the Ansible community package as it is now is questioned from time to time by community members including by the Steering Committee members. Such a discussion is happening now. It can hypothetically affect the inclusion process but even if the package will be abolished / trimmed down to core + a few core collections, the inclusion process will likely evolve to a community-approved collections review process with a Galaxy badge and their docs presence on docs.ansible.com as rewards and motivation for collection developers. What can be done from my perspective (see the stories and their sub-tasks):
User stories
Related sources
Definition of done
This one have user stories. Each has sub-tasks. The stories are done when all the sub-tasks are done. The epic is done when all stories are done.