Unmaintained collection: community.digitalocean

The community.digitalocean collection looks unmaintained / abandoned, it has:

It’s possible that it’s planned to replace the collection with digitalocean.cloud. 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.

4 Likes

It’s hacktoberfest so maybe the community can join in? https://hacktoberfest.org

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.

1 Like

@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.

1 Like

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.

2 Likes

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 What do you think?

It looks like this collection is now officially unmaintained, which might make things easier for us.

Thanks for this @mamercad!

The process for officially unmaintained collections is clear: Ansible Community Package Collections Removal Process — Ansible Community Documentation

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.

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

2 Likes