[Vote ended on 2024-10-07] Should we remove community.network from the Ansible community package?

Project Discussions
, , , ,
41

It’s a little bit unfortunate because the collection is unmaintained and deprecated. I really think we should get rid of it as soon as possible.

However, I agree that we shouldn’t archive the collection now and wait until Ansible 11 is really EOL.

42

Now that Ansible 11 is EOL I guess we should archive the community.network repository. WDYT?

43

Considering there has not been any reaction on Status of `community.network` · Issue #616 · ansible-collections/community.network · GitHub, and assuming no objections have come up somewhere else, I guess that’s fine now. Should we announce it ahead of time and give it another 1-2 weeks, or just archive it and then announce it? (It’s still possible to un-archive it later if it turns out that’s necessary/useful for whatever reason.)

44

It has been deprecated for more than one year, with notices in the README. I would say it is unlikely another week or two will make any difference, but I do not oppose that grace period either.

45

How about: if anyone has a preference for a grace period (and voices that opinion in the next few days), then we’ll have one, otherwise it’s instant archive?

3 Likes
46

I think the repo should be archived. It’s been deprecated long enough, and nobody voiced a preference for a grace period. A grace period of 1 to 2 weeks is over now, anyway.

Additionally, as far as I can see nobody is working on this collection anymore. Archiving would make clear that it’s dead.

At the end of the day, it can be un-archived when necessary. Or somebody can fork it, or re-use code from this collection in another one.

edit: Sorry, I don’t want to get on your nerves. But somehow this collection regularly turns up in my mind and I think we should get things straight. Even if it’s only for my peace of mind.

2 Likes
47

I agree, let’s archive it now. (Or whenever the next person who has the appropriate permissions is back from vacation =) .)

3 Likes
48

Archived, thanks everyone!

1 Like
49

I think it’s safe to say that at this point, the deprecation notice has been out for long enough that it’s not worth holding out hope for any further support or updates. If you’re still relying on the deprecated functionality, it might be time to start looking into alternatives or migrating to something more modern.

1 Like