# Unmaintained collection: community.digitalocean **URL:** \ **Category:** Project Discussions\ **Tags:** digitalocean, collections, community-wg\ **Created:** [October 2, 2025, 5:06pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602 "2025-10-02T17:06:00Z")\ **Posts on this page:** 9\ **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 2, 2025, 5:06pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/1 "2025-10-02T17:06:00Z")
The [community.digitalocean](https://github.com/ansible-collections/community.digitalocean) collection looks unmaintained / abandoned, it has: - no new commits since [Aug 20, 2024](https://github.com/ansible-collections/community.digitalocean/pull/385) - no new release since [Aug 20, 2024](https://github.com/ansible-collections/community.digitalocean/releases/tag/1.27.0) - no CI run since [Sep 4, 2024](https://github.com/ansible-collections/community.digitalocean/actions/runs/10692603915) - CI doesn’t test with ansible-core \> 2.16 - no reaction on [Validate compatibility with ansible-core 2.19](https://github.com/ansible-collections/community.digitalocean/issues/387) It’s possible that it’s planned to replace the collection with [digitalocean.cloud](https://github.com/digitalocean/ansible-collection). But this collection doesn’t really look actively maintained, either. Anyway, `community.digitalocean` hasn’t been deprecated officially. And it doesn’t mention `digitalocean.cloud` in the README as an alternative. _edit_: @mamercad I think you’ve been active on both collections, so maybe you want to have a look at this. ---
**Author:** ![bbaassssiiee](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bbaassssiiee/32/1927_2.png) [@bbaassssiiee](https://forum.ansible.com/u/bbaassssiiee)\ **Post date:** [October 4, 2025, 7:22pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/2 "2025-10-04T19:22:23Z")
It’s #hacktoberfest so maybe the community can join in? [https://hacktoberfest.org](https://hacktoberfest.org) ---
**Author:** ![mamercad](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mamercad/32/3807_2.png) [@mamercad](https://forum.ansible.com/u/mamercad)\ **Post date:** [October 6, 2025, 4:09pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/3 "2025-10-06T16:09:46Z")
Unfortunately, I haven’t had cycles lately to put towards either collection. I’m trying to find internal ownership of these collections. If it’s up to me, I’d deprecate `community.digitalocean` in favor of `digitalocean.cloud`. ---
**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, 12:12pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/4 "2025-10-18T12:12:01Z")
@mamercad If nobody wants to work on this collection I suggest to mention in the README that it’s deprecated, point people to `digitalocean.cloud` there and archive the repo. ---
**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 27, 2025, 6:15pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/5 "2025-10-27T18:15:11Z")
I’ve just seen that there’s a `digitalocean` tag and have added it right now. Since it looks like nobody wants or has the time to work on this collection, I think we should start a vote on removing it from the Ansible Community Package soon. I’ll give it a last try and mention it on Bullhorn again. Maybe this or adding the tag will make someone step up and work on the collection. If not, I think we should vote on removing it. ---
**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 1, 2025, 2:48pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/6 "2025-11-01T14:48:10Z")
Do you think we should vote on removing the collection from Ansible 14 or 15? I would prefer 14. But I’m not sure if this is really possible. The problem is: If I start a vote now, we won’t be able to finish it in time for Ansible 12.2.0. But until 12.3.0 will be released, 13.0.0 should already be GA. And I think our process says to deprecate for and remove collections in latest stable release + 2. Of course, we can do a 12.3.0 release early just to deprecate this collection and remove it from Ansible 14. [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) What do you think? ---
**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 1, 2025, 4:37pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/7 "2025-11-01T16:37:17Z")
It looks like this collection is now [officially unmaintained](https://github.com/ansible-collections/community.digitalocean/pull/390), which might make things easier for us. Thanks for this @mamercad! ---
**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:** [November 2, 2025, 11:26am UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/8 "2025-11-02T11:26:21Z")
The process for officially unmaintained collections is clear: [Ansible Community Package Collections Removal Process — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#removing-a-collection-that-has-been-explicitly-deprecated-or-abandoned-by-its-former-maintainers) Since feature freeze for Ansible 13 has not yet happened (it will happen in a few days), we can (and should) remove community.digitalocean from the upcoming Ansible 13.0.0b1 release (and announce the removal in the next 12.2.0 and 11.12.0 releases, which will also happen in a few days). There’s also no vote required. ---
**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:** [November 2, 2025, 11:59am UTC](https://forum.ansible.com/t/unmaintained-collection-community-digitalocean/44602/9 "2025-11-02T11:59:02Z")
I created a PR to remove community.digitalocean from Ansible 13.0.0: [Remove deprecated community.digitalocean from Ansible 13 by felixfontein · Pull Request #620 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/pull/620)