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.
Now that Ansible 11 is EOL I guess we should archive the community.network repository. WDYT?
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.)
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.
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