Hi!
I wanted to use a title like "Is this project still maintained?" at first, but it's pretty obvious that it isn't
- no new commits to main since 2024-01-12
- last release 1.3.12 shortly after, 2024-01-23
- several open vulnerabilities, with unmerged Renovate version updates
- very little activity in issues, with people wondering if redhat-cop in general is "going abandonware"
I'm aware that redhat-cop projects are community driven, and are not official Red Hat projects - but we know from experience in working with our customers that this isn't immediately obvious; many like to use the OperatorHub to stay on recent, supported versions [0] instead of managing everything on their own.
Now I'm wondering how to can contribute to this issue.
For now, I think it's best to at least update the readme with a warning that this project currently lacks maintenance, and give details about future plans - if there are no future plans, this repository should probably be archived and removed from OperatorHub?
If maintenance stalled due to lack of contributors - how can we help? :)
Pinging point of contacts who "have a vested interest in the overall health and stability of the Red Hat Communities of Practice", as outlined on the contrib page:
[0] Some also think that OperatorHub automatically equates to "supported by Red Hat", which is somewhat understandable - earlier versions of the docs explained quite clearly that there are different levels of operators / support, but recent docs have this table past the middle of a single, giant page, which is easy to overlook. While this might be relevant context on why the maintenance status of redhat-cop projects should be as transparent as possible, it's obviously more of an OCP docs / user knowledge issue.
Hi!
I wanted to use a title like "Is this project still maintained?" at first, but it's pretty obvious that it isn't
I'm aware that redhat-cop projects are community driven, and are not official Red Hat projects - but we know from experience in working with our customers that this isn't immediately obvious; many like to use the OperatorHub to stay on recent, supported versions [0] instead of managing everything on their own.
Now I'm wondering how to can contribute to this issue.
For now, I think it's best to at least update the readme with a warning that this project currently lacks maintenance, and give details about future plans - if there are no future plans, this repository should probably be archived and removed from OperatorHub?
If maintenance stalled due to lack of contributors - how can we help? :)
Pinging point of contacts who "have a vested interest in the overall health and stability of the Red Hat Communities of Practice", as outlined on the contrib page:
[0] Some also think that OperatorHub automatically equates to "supported by Red Hat", which is somewhat understandable - earlier versions of the docs explained quite clearly that there are different levels of operators / support, but recent docs have this table past the middle of a single, giant page, which is easy to overlook. While this might be relevant context on why the maintenance status of redhat-cop projects should be as transparent as possible, it's obviously more of an OCP docs / user knowledge issue.