# Possibly unmaintained collection: wti.remote **URL:** \ **Category:** Project Discussions\ **Tags:** collections, community-wg\ **Created:** [October 18, 2025, 11:57am UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705 "2025-10-18T11:57:07Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 18, 2025, 11:57am UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/1 "2025-10-18T11:57:07Z")
The [wti.remote](https://github.com/wtinetworkgear/wti-collection) collection looks unmaintained / abandoned, it has: - no new commits since [Apr 12, 2025](https://github.com/wtinetworkgear/wti-collection/commit/7a67a39ffdb3a7def3043227f083ec7b2fd7021b) - no new release since [Sep 16, 2024](https://github.com/wtinetworkgear/wti-collection/releases/tag/v1.0.10) - no CI run since [Nov 16, 2024](https://github.com/wtinetworkgear/wti-collection/actions/runs/11867743718) - no reaction on [Community package requirements: repository management](https://github.com/wtinetworkgear/wti-collection/issues/17) - no reaction on [Validate compatibility with ansible-core 2.19](https://github.com/wtinetworkgear/wti-collection/issues/18) _edit_: [Unmaintained collection: Removal from the Ansible Community Package](https://github.com/wtinetworkgear/wti-collection/issues/19) ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 18, 2025, 5:23pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/2 "2025-10-18T17:23:09Z")
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](https://github.com/wtinetworkgear/wti-collection/issues/19), 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.) ---
**Author:** ![wtinetworkgear](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wtinetworkgear/32/9683_2.png) [@wtinetworkgear](https://forum.ansible.com/u/wtinetworkgear)\ **Post date:** [October 21, 2025, 2:51pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/3 "2025-10-21T14:51:06Z")
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](mailto:kenp@wti.com) ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 21, 2025, 4:42pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/4 "2025-10-21T16:42:39Z")
Just to clarify, this is not about throwing the collection out of the Ansible ecosystem at large. It’s about the [Ansible Community Package](https://pypi.org/project/ansible/). People can still manually install the collection with `ansible-galaxy collection install wti.remote` even when it has been removed from the ACP. > [@wtinetworkgear](#): > > Our modules have been very stable 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](https://github.com/wtinetworkgear/wti-collection/issues/17). > [@wtinetworkgear](#): > > 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](mailto:kenp@wti.com) 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 😏 ---
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [October 21, 2025, 9:13pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/5 "2025-10-21T21:13:37Z")
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](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html). 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](https://forum.ansible.com/tags/c/project/7/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 ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 22, 2025, 3:55pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/6 "2025-10-22T15:55:40Z")
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](https://github.com/wtinetworkgear/wti-collection/issues/19). 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. ---
**Author:** ![wtinetworkgear](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wtinetworkgear/32/9683_2.png) [@wtinetworkgear](https://forum.ansible.com/u/wtinetworkgear)\ **Post date:** [October 23, 2025, 12:47pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/7 "2025-10-23T12:47:43Z")
@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. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [November 20, 2025, 7:05pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/8 "2025-11-20T19:05:03Z")
@wtinetworkgear It would be really great if you could activate the CI GHA workflow again. It looks like the last run was [Nov 16, 2024](https://github.com/wtinetworkgear/wti-collection/actions/runs/11867743718) and has been disabled since because there hasn’t been any activity in this repository for so long. Out of curiosity, there’s a [1.0.11a](https://github.com/wtinetworkgear/wti-collection/releases/tag/v1.0.11a) release now on GitHub (claiming to be the `Release v1.0.11 of the WTI Ansible Collection` without an a, which is a little bit confusing). But I don’t se this on galaxy. Is this intentionally? Like the a stands for alpha and you don’t want to publish alpha releases on galaxy? ---
**Author:** ![wtinetworkgear](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wtinetworkgear/32/9683_2.png) [@wtinetworkgear](https://forum.ansible.com/u/wtinetworkgear)\ **Post date:** [November 21, 2025, 2:49am UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/9 "2025-11-21T02:49:08Z")
@mariolenz We are looking into activating the CI GHA workflow, thanks for the reminder. The 1.0.11a “release” is my doing, we had a customer that urgently needed a cellular read module and I thought making a “release” would be the easiest for them to get the files. I am currently writing the cellular “write” module and that will be the release we where going to use in Galaxy. Sorry for the confusion, we will be more careful what we bundle. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [November 21, 2025, 4:03pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/10 "2025-11-21T16:03:43Z")
Thanks for the clarification! No problem there. I was just wondering 😃 ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [December 5, 2025, 4:58pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/11 "2025-12-05T16:58:02Z")
The 1.0.11a release seems to have been removed. But there’s a 1.0.11 (without “a”) release now. I’m pretty sure it’s been marked as a pre-release until recently, but it isn’t anymore. So it looks to be an official release now. However, I don’t find it on galaxy. @wtinetworkgear Do you have any problems publishing 1.0.11 on galaxy? If yes, I can’t help you there _directly_. But I could ask around for help if you want me to. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 2, 2026, 8:09pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/12 "2026-02-02T20:09:00Z")
There has been a new [release on GitHub](https://github.com/wtinetworkgear/wti-collection/releases/tag/v1.0.11) Dec 4, 2025. This has been two months(!) ago. But on galaxy, the latest release is still [1.0.10](https://galaxy.ansible.com/ui/repo/published/wti/remote?version=1.0.10) from 2024. I think we should remove the collection from ACP. Releasing on GitHub but not on galaxy looks like a problem to me… ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 10, 2026, 5:51pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/13 "2026-02-10T17:51:02Z")
If I don’t see 1.0.11 on galaxy soon, I’d like to start a vote on removing `wti.remote` from the community package. I guess the options to vote on would be: - Remove from Ansible 14 - Keep [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) What do you think? ---
**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\ **Post date:** [February 10, 2026, 8:33pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/14 "2026-02-10T20:33:05Z")
I am OK for removing the collection from community package. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 10, 2026, 9:00pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/15 "2026-02-10T21:00:35Z")
👍 for voting (and for the options you propose) ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [February 11, 2026, 7:42am UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/16 "2026-02-11T07:42:54Z")
Hi folks - Have we reached out to @wtinetworkgear over email? They provided an email in the [GitHub issue](https://github.com/wtinetworkgear/wti-collection/issues/19). They were responsive here previously too, maybe they’re having trouble uploading to Galaxy? 🤔 I can reach out via email explaining the situation and ask if they can upload [Release v1.0.11 · wtinetworkgear/wti-collection · GitHub](https://github.com/wtinetworkgear/wti-collection/releases/tag/v1.0.11) to Galaxy? ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 11, 2026, 3:57pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/17 "2026-02-11T15:57:33Z")
I didn’t contact them over email. Feel free to do so, maybe it helps. However, I _did_ ask them if there are any problems publishing on galaxy and offered to help them two months ago. Or, at least, to ask around for help because I can’t do anything there myself (see above). I’m not sure if it’s a good thing having collections in Ansible where people only react when emailed directly, but not when pinged via issues in their repo or here on the forum. ---
**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\ **Post date:** [February 12, 2026, 8:21am UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/18 "2026-02-12T08:21:26Z")
Hi @mariolenz I contacted them via email yesterday and got a response. They mentioned that they were OOO at the moment but would work on resolving the issues highlighted once back: - Triggering the GitHub Action CI to run tests against the collection again: [CI · Workflow runs · wtinetworkgear/wti-collection · GitHub](https://github.com/wtinetworkgear/wti-collection/actions/workflows/ansible-test.yml) - Updating the ansible-test.yml CI to test against the latest versions of Ansible Core: - stable-2.15 - stable-2.16 - stable-2.17 - stable-2.18 - stable-2.19 - stable-2.20 - devel - Ensuring that the most recent version (1.0.11) of the collection [Release v1.0.11 · wtinetworkgear/wti-collection · GitHub](https://github.com/wtinetworkgear/wti-collection/releases/tag/v1.0.11) is available on Ansible Galaxy: [Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/wti/remote/) Hope I got everything 🙂 Indeed you did offer to help on this post and in the GitHub issue. Apologies I didn’t mean to imply that you didn’t if that’s how it came across. I greatly appreciate you, and the rest of the Steering Committee’s ongoing work to keep the Ansible community package healthy. I don’t think this should block a vote on removing this collection from the community package. If the needed amendments are made, then I’m sure it can be added back again. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 12, 2026, 6:03pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/19 "2026-02-12T18:03:56Z")
> [@dbrennand](#): > > I contacted them via email yesterday and got a response. They mentioned that they were OOO at the moment but would work on resolving the issues highlighted once back Out of office since December 5, 2025? Because that’s the date when I’ve asked if there are any problems with publishing on galaxy… Well, let’s wait a couple of days and see what happens. Nevertheless, I think they should be more responsive both here in the forum and especially in their repo. It somehow sucks having to ping them via email. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 24, 2026, 6:26pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705/20 "2026-02-24T18:26:10Z")
At the end of the day, the Ansible Community Package only includes collection releases that are published on Galaxy. So if they’re fine with releasing on GitHub _only_, I don’t understand why they want to be included in the ACP. It just doesn’t make sense to me. Their users simply won’t get the latest collection release via ACP. If their idea is that users should install via GitHub, that’s fine for me… but why do they insist on keeping the collection in ACP, then? I’ll give them one or two days to publish 1.0.11 (released on GitHub 11! weeks ago) on Galaxy. If they don’t I’ll start a vote to remove the collection. cc @wtinetworkgear _edit_: I also have a problem with them not really reacting both here on the forum and in their issue tracker on GitHub. [Next page](https://forum.ansible.com/t/possibly-unmaintained-collection-wti-remote/44705.md?page=2)