-
Notifications
You must be signed in to change notification settings - Fork 715
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
REQUEST: Publish KubeCon / K8s Contributor summit message using GH announcements #5193
Comments
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? |
cc @kubernetes/owners @kubernetes/steering-committee |
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. |
Fortunately there's an API: https://docs.github.com/en/enterprise-cloud@latest/rest/announcement-banners/organizations If people agree, this can be part of the org 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: