The wti.remote collection looks unmaintained / abandoned, it has:
While there have been reactions to our issues in the past (all four closed issues in that repo were by us), they were sometimes quite slow. Let’s see if there is any reaction to Unmaintained collection: Removal from the Ansible Community Package · Issue #19 · wtinetworkgear/wti-collection · GitHub, otherwise I think it’s OK to remove the collection. (Since we’re too late to remove it for Ansible 13, there will be plenty of time to undo this step before Ansible 14 is released, if the need arises.)
Yes, you have helped us in the past, we are a small company and with the administration things Ansible has thrown us , you have helped us in the past.
Our modules have been very stable and our last update in 2024 has coincided with our last hardware release. We are planning a new hardware release in the near future.
If you would like to talk about any issues you have with our small, older company, i would love to discuses any issues with you.
kenp@wti.com
Just to clarify, this is not about throwing the collection out of the Ansible ecosystem at large. It’s about the Ansible Community Package. People can still manually install the collection with ansible-galaxy collection install wti.remote even when it has been removed from the ACP.
Possibly, but how do you know? I don’t see any CI runs since nearly a year. So how do you know that your modules are really working with ansible-core 2.19, or the upcoming 2.20? And how could we see that they do?
Again, this is about keeping the ACP healthy. Nothing else. I suggest to get your CI running again (adding ansible-core 2.18 and 2.19 and, ideally, also the upcoming 2.20) and address what @gotmax23 mentioned in Community package requirements: repository management.
Small company or not, you are getting paid to work on this collection. I am not for working on Ansible, I’m doing it in my spare time. So please react on the issues we open in your repo. There are some 90 collections in ACP, I can’t have a 1:1 relationship to all of those.
Apart from everything else, I think this should be discussed openly for everyone to see. Discussing this with you via email would be the opposite. Open source is not only about open sources, but also about discussing things openly IMHO 
Hi @wtinetworkgear,
Thank you for reaching out to us, and I apologize if we didn’t communicate our processes more clearly. Just to clarify, Mario was just following the Steering Committee policy at Ansible Community Package Collections Removal Process — Ansible Community Documentation. The primary way the Steering Committee (and users of the community package) communicate with collection maintainers is via collection issue trackers, so if there is no response when we file issues, the natural assumption is that the maintainers are unresponsive and the collection is unmaintained. We do not keep track of anyone’s email address and emails are not part of any of our processes. (Of course, if you or anyone else thinks we should make changes to any of our policies or processes, you are very welcome to get in contact with the steering committee by creating a topic in Topics tagged community-wg).
So, as far as I see it, as long as the issues brought up in this post are resolved and maintainers of the collection are responsive to issues in the future, we can cancel this removal request. Note that (except in extenuating circumstances) all collection removals have a mandatory announcement/feedback and deprecation period and can be reversed.
Best,
Maxwell
Sorry, I might have been a little bit grumpy yesterday. Sorry for this 
Anyway, since @wtinetworkgear reached out to us the question of the collection being unmaintained should be answered: It still is! So I’ve closed the issue in the repo.
There might still be some collection requirement violations, but that’s different discussion.
However: @wtinetworkgear If you don’t run CI tests internally on a regular basis, you might want to activate them on GitHub again. Just to make sure there are no problems with ansible-core 2.19 or the upcoming 2.20 release.
@mariolenz No problem ! We all have our off day (in my case, many 
), I am going to assign this to one of our people, we will definitely take care of the collection requirement violations.