Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of Projects Required for LWKD #232

Open
fykaa opened this issue Sep 15, 2023 · 4 comments
Open

List of Projects Required for LWKD #232

fykaa opened this issue Sep 15, 2023 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@fykaa
Copy link
Member

fykaa commented Sep 15, 2023

We require a list of relevant projects from which we can draw news, updates, PRs, etc. for the LWKD newsletter.

Also feel free to include them in the comments, and we will take them into account.

Tasks

Preview Give feedback
No tasks being tracked yet.
@jberkus
Copy link
Contributor

jberkus commented Oct 2, 2023

Yeah, so we want to limit this to close projects -- ones that are required to build Kubernetes, mostly, and things like installers. We would NOT want to include the whole CNCF universe.

Examples would be:

  • Etcd
  • CSI
  • CNI
  • CRI-O & Containerd
  • Kops
  • CoreDNS
  • gRPC
  • GoLang (this usually shows up in Version Updates anyway)

And, of course, subprojects of Kubernetes are all included, like:

  • kubeadm
  • clusterAPI
  • nginx-ingress

There's some borderline ones, where we might include something from them if it's major, like new major version or a serious security hole. This could include:

  • Helm
  • Prometheus
  • OpenTelemetry
  • Sigstore (because it affects our builds)

A good rule of thumb would be: "if the project exists in a competitive space, probably don't include it".

@jberkus
Copy link
Contributor

jberkus commented Jan 23, 2024

per other issue, we've added Kubespray.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024
@jberkus
Copy link
Contributor

jberkus commented Apr 23, 2024

/remove lifecycle-stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants