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

REQUEST: Publish KubeCon / K8s Contributor summit message using GH announcements #5193

Open
mrbobbytables opened this issue Oct 1, 2024 · 4 comments
Labels
area/github-integration Third-party integrations, webhooks, or GitHub Apps

Comments

@mrbobbytables
Copy link
Member

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:
image

We also publish a similar message on the K8s.io website:
image

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!

/cc @caniszczyk

Additional context for request

No response

@mrbobbytables mrbobbytables added the area/github-integration Third-party integrations, webhooks, or GitHub Apps label Oct 1, 2024
@jeefy
Copy link
Member

jeefy commented Oct 1, 2024

Here's how it would (generally) look:

image

@BenTheElder
Copy link
Member

BenTheElder commented Dec 10, 2024

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?

@BenTheElder
Copy link
Member

cc @kubernetes/owners @kubernetes/steering-committee

@pohly
Copy link
Contributor

pohly commented Dec 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-integration Third-party integrations, webhooks, or GitHub Apps
Projects
None yet
Development

No branches or pull requests

4 participants