Hello
- we publish when significant changes have been made. As you mentioned, only updates related to CI etc have been made. So what is the point? Should we make publications … without changes? The collection is in use and works as it is. At the moment there is no effort to further expand api coverage and development as this is not our priority.
- No response does not mean no reaction, but that action has been taken that is not visible to anyone. If you want a response, the committee should make it clear in the question that a response is required!
- true/false is not a “feature” currently being worked on in the docs. Even in Ansible’s core modules, there are modules that still have a no/yes syntax. If that’s a reason to throw a working collection out of the community package, go for it…
I have a strong feeling that this “cleanup” of working and used collections will only lead to Ansible losing relevance.
“You can install collections manually”: → Yes, you can, but AFAIK there is no (for years) integrated update mechanism to update collections and roles. So you have to manually check for updates via more and more roles and collections… do we really think this is the way to go?
Just my 2 cents.