Unmaintained collection: netapp_eseries.santricity

Project Discussions
, , ,
1

The netapp_eseries.santricity collection looks unmaintained / abandoned, it has:

3

let’s start the process then:)

4

I did, there’s an issue in the repository and I’ve mentioned this to @newsbot to get it into the next Bullhorn.

According to the process we now have to wait a couple of weeks until we start a vote. I’ll try to remember opening a vote 4 weeks after the next Bullhorn release.

1 Like
5

For the record: The Bullhorn #143

1 Like
6

I’d like to vote on removing this collection from Ansible 11 since it looks unmaintained. The vote will end 2024-08-21.

Steering Committee vote
  • Remove it from Ansible 12
  • Keep it in Ansible 12
0 voters
Community vote
  • Remove it from Ansible 12
  • Keep it in Ansible 12
0 voters
7

I’ve asked internally to see if we’ve got any contacts.
Though seems like one of the maintainers left NetApp over a year ago, and the other maintainer hasn’t been active on GitHub for over a year.

8

Sounds pretty unmaintained to me :slight_smile:

9

Two maintainers have appeared. I’ve asked if they can look at the CI Failures in that collection.

So let’s give them a few weeks to see if they get it sorted.

2 Likes
10

Not to put too fine a point on this, but even if they do I have feeling we’ll see netapp_eseries.santricity on my list of possibly unmaintained collections next year again :worried:

11

I agree. Let’s suspend the vote and take another look in a couple of weeks. (I’ll change my vote to “keep” for now.)

1 Like
12

@gundalow @felixfontein What do you mean with a few / couple of weeks?

Not to put too fine a point on this, but there hasn’t been any activity. I don’t see any commits and no PRs, either, since those two “maintainers” have appeared and claimed they’re working on the collection.

How long do we want to wait? If they really want to stay in the Ansible Community Package, I think they should have done something already.

Not to put too fine a point on this, but @gotmax23 updated collection failures today. It looks like there are still some problems… of course there are, since there hasn’t been any new release.

I think we should remove them from the ACP. This doesn’t mean they can’t publish on galaxy and are still be part of the ansible community at large. But I think we should throw this collection out of the ACP.

@SteeringCommittee I think we should try to keep the ACP healthy. And removing this collection would really help there. Should we start another vote?

13

We have addressed the majority of failure found in the sanity checks. The fixes will be included in our next update. We are hoping to get the update pushed within a month.

14

There have been no public commits since January 31, 2023. Fixing them locally does not count as addressing them. Even if you don’t want to commit these changes to the main branch for some reason, you could at least open PRs so that interested collection users can review them.

3 Likes
15

@mcwhiteside Sorry, but it’s hard to see if anyone is really working on the collection if this happens completely internally.

If I’ve seen at least some commits addressing the sanity test issues, even if they haven’t been released yet, I wouldn’t have brought up the question to remove the collection again :person_shrugging:

I’m satisfied for now and will wait a couple of more weeks.

16

Only publishing changes on release time is not good practice. Let’s re-evaluate it in mid October; then we have ~two weeks time before the Ansible 11 feature freeze.

1 Like
17

There has been a new release both on GitHub and Galaxy.

I’ll tick this off on my lists in Possibly unmaintained collections in Ansible 10 and Possibly unmaintained collections in Ansible 11.

1 Like