You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A general KubeCon reminder has been published via GitHub announcements to CNCF member orgs:
We also publish a similar message on the K8s.io website:
Maybe something like this?
Join us at KubeCon for the K8s Contributor Summit! We have healthy mix of talks,
several hours of unconference sessions, SIG and WG meetings Monday Nov 11th
before the KubeCon kicks off. Hope to see you there!
Currently our kubernetes.io banners are approved by steering since they're messages on blast from the project, this seems like something we'd use in the same way (kubecon banners are pretty much rubber-stamped, but the same mechanism gets used/protected for other announcements)
We ... unofficially threw one together for the prow.k8s.io migration earlier this year as a github banner and not a website banner since that was only contributor facing, but we should probably look at handling it similarly.
Maybe we can control this with git? Is there an API?
If there's no API, we could still create a README.md in some repo, make steering the OWNER, and then trust whoever manually mirrors that file to GitHub to faithfully reproduce the message approved by steering.
That's slightly more process than just a GitHub issue, but not too much and doesn't need tooling.
Organization or Repo
kubernetes*
Name of integration
N/A
Link to integration website
N/A
Describe what is attempting to be accomplished
What: Create a GitHub announcement for KubeCon & the K8s Contributor Summit
ref: cncf/foundation#863
A general KubeCon reminder has been published via GitHub announcements to CNCF member orgs:
We also publish a similar message on the K8s.io website:
Maybe something like this?
/cc @caniszczyk
Additional context for request
No response
The text was updated successfully, but these errors were encountered: