Closed mariolenz closed 11 months ago
@Andersson007 Looking at the output of my example, it looks like you've released dellemc.os10 v1.2.0 but I don't see it on galaxy. And, therefor, it's not part of the community package.
I looked through the list, here are my guesses:
Officially unmaintained:
Seems unmaintained, parts might no longer work:
No activity (including no bug reports and PRs) - i.e. might simply be working without need of changes:
Not sure:
Actively maintained (just no release):
Regarding the script: I guess it would make sense to integrate that into antsibull. I'm not sure how exactly though (i.e. whether as a subcomand of antsibull-build, or as a new CLI tool).
Officially unmaintained:
- google.cloud (we decided that :) )
Yes, I know. But if I haven't included this people would have asked why my script didn't find out why google.cloud
hasn't changed since 3.0.0 ;-)
Actively maintained (just no release):
- cyberark.conjur (https://github.com/cyberark/ansible-conjur-collection/commits/main)
cyberark/ansible-conjur-collection#175
It looks like @Andersson007 tagged a new release v1.2.0 but somehow it's not on Galaxy.
@Andersson007 Looking at the output of my example, it looks like you've released dellemc.os10 v1.2.0 but I don't see it on galaxy. And, therefor, it's not part of the community package.
@mariolenz yep, i know, the collection was forgotten at that time (now maybe it is too). We had merged several PRs with independent folks and I released the collection as maintainers had not responded.. After that we noticed that it hadn't appeared on galaxy automatically which means they hadn't publish it via Zuul. IIRC finally someone appeared promising to release publish it on Galaxy.
If it still hasn't happened, we could consider it unmaintained.
yep, i know, the collection was forgotten at that time (now maybe it is too).
@Andersson007 Not only dellemc.os10. If I use my script to compare 6.2.0 against 4.0.0 (instead of 3.0.0), there are also dellemc.os6 and dellemc.os9 on the list of collections that that are still the same version.
If it still hasn't happened, we could consider it unmaintained.
I think that dellemc.os6 and dellemc.os9 might be possible candidates, too. All commits from this year are from you ;-P
Not sure:
@felixfontein I think mellanox.onyx is unmaintained. It looks like the only changes throughout 2022 and 2021 were fixes to sanity tests and similar from @Andersson007, the latest release on Galaxy is 1.0.0 from 2 years ago and there hasn't been a CI run since 4 months.
@Andersson007 do you know what the state of mellanox.onyx is? If not, we should start the unmaintained process for it to see whether we can get a reaction.
@mariolenz @felixfontein yep, let's start the process, thanks! if the original maintainers don't respond in the removal issue, we could offer the reporter to become a maintainer.
Result of unchanged-dependencies.py 7.0.0 4.0.0
:
IMO community.fortios is similar unmaintained as community.google (some community team members did some generic maintenance work, but otherwise it looks dead - the only interaction with potential users was in https://github.com/ansible-collections/community.fortios/issues/5, and there was actually no interaction so far).
@felixfontein I'll have a look at this. And also at community.skydive
and ngine_io.exoscale
.
ngine_io.exoscale is probably still maintained, though CI has been disabled for quite a long time now and the CI matix hasn't been updated for a similar amount of time. CC @resmo who is (or was) maintaining it.
The repository for community.skydive is apparently also used for skydive.skydive (https://github.com/ansible-collections/skydive/blob/master/galaxy.yml#L7-L8), which doesn't really exist (https://galaxy.ansible.com/skydive/skydive) - or maybe only on Automation Hub (can't check, I have no access)? Anyway, it seems to be maintained by the ansible network team.
@Qalthos do you know whether the ansible network team still maintains this, and if not, who does / should?
Regarding the script: I guess it would make sense to integrate that into antsibull. I'm not sure how exactly though (i.e. whether as a subcomand of antsibull-build, or as a new CLI tool).
If #183 is accepted and merged, maybe we could put it into the scripts/
directory. At least until we find a better solution.
Thoughts?
cc @Andersson007
unchanged-dependencies.py 8.1.0 6.0.0
:
I'd like to work on finding (possibly) unmaintained collections once Ansible 9 is released. But is this the right place to keep track?
I mean, just keep this issue and add new lists? Or open a new issue per Ansible release here? Or maybe move it to ansible-build-data? Or wait on the new forum and track things there?
we could continue using this issue and move to discourse later when things are fully up and running there
unchanged-dependencies.py 9.0.0a3 7.0.0
:
unchanged-dependencies.py 9.0.0 7.0.0
:
Moving to the forum: Possibly unmaintained collections in Ansible 9
Summary
I am not aware that we have a way to detect unmaintained collections. Therefor, I've written a small script to compare dependencies between versions. The idea is that if a collection version didn't change between, say, 3.0.0 and 6.2.0, this collection might be unmaintained.
Do you think this might be useful? If so, where should we put it? It has to be run in the ansible-community/ansible-build-data directory, so we could add it to this repository directly. Or do we have another repo for tools concerning the community package where we can add it?
Of course, this question only arises if you consider this useful. If not, we don't have to discuss where to put this script.
Result of running
unchanged-dependencies.py 6.2.0 3.0.0
:unchanged-dependencies.py
: