I should have added that we already maintain several collections (See, among them the Icinga director collection that is part of ansible. So we’ve got some experience there.
But I’ll make sure to review the guidelines again.
For ansible-nomad and ansible-consul I recommend creating issues to offer helping with maintaining them. I couldn’t find any such issues yet (but then I also didn’t look too closely). Make sure to ping the persons who committed/merged to the repositories in the last years so they shouldn’t miss this.
For community.grafana it’s probably best to ping the current maintainers (someone needs to look up who these are, the community team should be able to do that) and give them a bit more time to react. If there is no reaction, or only positive feedback, getting you added as maintainers by the community team should be no problem.
(I’m saying that as someone who’s not part of the community team, but I can’t think of a reason why they wouldn’d do that )
Those issues seem like a good place to start, and as @felixfontein says, we can help if you get no traction in a while. Keep us updated with your progress, please!
It’s great to see someone offering to maintain orphaned collections! As mention by all, thanks for that!
Seeing you are already maintaining quite a few collections, I would suggest you join the @CollectionMaintainer group here: Collection maintainers & contributors - Ansible , it’s going to become increasingly important to stay up to date on news affecting collection developers and maintainers!
By the way, are you sharing those collections in the new Galaxy?