I guess it would be best if the collection would declare its deprecation because no one is actively maintaing it itself on Bullhorn to begin with. Like frr.frr and openvswitch.openvswitch did. Ideally mentioning that This collection is not supported with ansible-core>2.17 or There will be no work done on making this collection work with ansible-core>2.17 or similar.
I don’t want to do this because I haven’t worked on this collection at all. I suggest someone who has worked on this collection recently (hint hint @Andersson007).
This would change the situation considerably for us. We wouldn’t start a vote on a collection that’s considered unmaintained or that we know is unmaintained, but on one that declared itself unmaintained. And denies compatibility with / supporting ansible-core 2.18, which the next Ansible Community Package will be based on.