community
community copied to clipboard
kubevirt
Contact project maintainers for stale projects and ask them whether it is safe to archive these
We should contact project maintainers of stale projects and ask them whether it is safe to archive them.
Hint: Archiving can be done over kubevirt/project-infra orgs.yaml
Originally posted by @dhiller in https://github.com/kubevirt/community/pull/236#discussion_r1295740347
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.
/lifecycle stale
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.
/lifecycle stale
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.
/lifecycle rotten
From my investigation the repos, in order of longest time since they were updated are: 2 Years: https://github.com/kubevirt/qe-tools https://github.com/kubevirt/test-benchmarks
3 Years: https://github.com/kubevirt/demo https://github.com/kubevirt/kubevirt-tutorial (Looks solid, could be salvageable/updated) https://github.com/kubevirt/libvirt (Marked deprecated in README; not archived)
4 Years: https://github.com/kubevirt/ansible-kubevirt-modules https://github.com/kubevirt/machine-remediation https://github.com/kubevirt/cpu-nfd-plugin https://github.com/kubevirt/kvm-info-nfd-plugin
5 Years: https://github.com/kubevirt/krew-index https://github.com/kubevirt/cloud-image-builder https://github.com/kubevirt/web-ui (Marked deprecated in README; not archived) https://github.com/kubevirt/web-ui-operator https://github.com/kubevirt/web-ui-design
6 Years: https://github.com/kubevirt/cluster-api-provider-external https://github.com/kubevirt/cdi-operator https://github.com/kubevirt/origin-web-console https://github.com/kubevirt/origin-web-console-server https://github.com/kubevirt/run https://github.com/kubevirt/storage-demo https://github.com/kubevirt/test-infra-containers https://github.com/kubevirt/vmctl
7 Years (Honorable Mention): https://github.com/kubevirt/external-storage https://github.com/kubevirt/gluster-kubernetes
8 Years (The Champion): https://github.com/kubevirt/k8s-start
I'll notify the mailing list and look into a way of batch notifying maintainers in the repos themselves.
Wow.
Thanks for checking this.
Did your script (I hope it was a script) also check if any branches saw any update more recently?
I just used the github 'sort by oldest' filter and ran through them. I did not check additional branches, but after a quick poke of about 40% of the repos here and their branches it looks pretty accurate.
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.
/lifecycle stale
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.
/lifecycle stale
Following the notice of intention on the mailing list, I've created: https://github.com/kubevirt/project-infra/pull/3686