Org: Kubernetes/cluster-registry appears to be abandoned
Organization or repository
kubernetes/cluster-registry
Describe the issue
The repository hasn't been modified since March 13th. Issues in the repository are currently rotting away. Consider archiving this repository?
chases2
All 21 comments
/assign @pmorie @quinton-hoole
/sig multicluster
Assigning sig-multicluster chairs
cblecker
on 21 Dec 2019
@pmorie @quinton-hoole friendly ping :)
nikhita
on 28 Feb 2020
@pmorie @quinton-hoole Can you take a look at this?
nikhita
on 22 May 2020
sent an e-mail to the sig list
cblecker
on 25 May 2020
We discussed this in our May 26 meeting. The predominant sentiment seemed to be that the project is essentially defunct in its present form. It is possible that we will create something similar in the future, but the SIG does not want to be bound by prior decisions made in this repo. It is also likely that we will create any new repository for this in the kubernetes-sigs github org. I will send a message to the mailing list so that we can have a lazy consensus to archive this project.
pmorie
on 2 Jun 2020
@pmorie :wave: Just following up. Has there been a date set for the lazy consensus already? Couldn't find one the mailing list.
nikhita
on 15 Jun 2020
I don't think this repo should be archived, in addition, I've some idea about how this API should be enhanced. Please just wait for a while, we will discuss it at the SIG meeting.
RainbowMango
on 19 Jun 2020
@pmorie , any conclusion there? we'd like to use this report as cluster-api for multi-cluster scenario.
k82cn
on 24 Jun 2020
@k82cn @RainbowMango I'd recommend following up on the mailing list, github notifications can sometimes go to a black hole :upside_down_face:
nikhita
on 27 Jun 2020
sure, thanks very much for your reminder :)
k82cn
on 28 Jun 2020
Thanks for bumping, I see @RainbowMango's reply now.
If there's an objection, we should give this some additional discussion time in a SIG meeting. I have put an item on July 07, 2020 agenda to discuss. We will set a date for lazy consensus at that time.
pmorie
on 29 Jun 2020
We have deferred a decision on whether the existing repository will be archived or not; currently collecting use cases for a future cluster registry concept in the community in a world-writable doc. More information here. Anyone should feel welcome to add to this document; we'll discuss use-cases in coming SIG meetings. We'll provide notice when there is a 'last call' for use cases.
pmorie
on 10 Jul 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 8 Oct 2020
/remove-lifecycle stale
@pmorie has a decision been taken already?
nikhita
on 9 Oct 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 7 Jan 2021
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
fejta-bot
on 6 Feb 2021
/lifecycle frozen
On Sat, Feb 6, 2021 at 10:44 AM fejta-bot notifications@github.com wrote:
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community
https://github.com/kubernetes/community.
/lifecycle rotten—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/org/issues/1499#issuecomment-774401617,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24BUBECWABURND3VHDZ63S5TF4JANCNFSM4J5RNEMA
.
nikhita
on 6 Feb 2021
@pmorie do you know if a decision was reached? It's been some time now and the repo's still most recent activity is from 2+ years ago.
mrbobbytables
on 21 Feb 2021
Going ahead with the archival based https://github.com/kubernetes/community/pull/5661
nikhita
on 26 Mar 2021
Repo has been archived: https://github.com/kubernetes-retired/cluster-registry
Also sent a notice to the multicluster mailing list + k-dev - https://groups.google.com/g/kubernetes-dev/c/FaxRtx2t0nw
The following PRs should merge before this issue can be closed:
- https://github.com/kubernetes/org/pull/2602 - remove GitHub teams
- https://github.com/kubernetes/community/pull/5661 - remove repo from sigs.yaml
nikhita
on 26 Mar 2021
All related PRs have merged, closing
nikhita
on 5 Apr 2021
Related issues
lpabon
·
3Comments
RA489
·
3Comments
jmyung
·
3Comments
camilamacedo86
·
3Comments
savitharaghunathan
·
3Comments
Most helpful comment
We have deferred a decision on whether the existing repository will be archived or not; currently collecting use cases for a future cluster registry concept in the community in a world-writable doc. More information here. Anyone should feel welcome to add to this document; we'll discuss use-cases in coming SIG meetings. We'll provide notice when there is a 'last call' for use cases.