-
Notifications
You must be signed in to change notification settings - Fork 838
feature(website): Update Graduation and Community calls #4103
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
Comments
/area website |
/good-first-issue |
@varodrig: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hey @varodrig , Can I work on this? |
Do I have to update all the calls? |
Doesn't the calendar already reflects this? |
Not sure @andreyvelich @thesuperzapper do you know? |
Can we just link the Graduation meeting in this table? |
Yes, but we do need to update the meeting agenda in the word document clarify that's bi-weekly and the upcoming dates. will that work? |
Yes, please update it @varodrig! |
Uh oh!
There was an error while loading. Please reload this page.
This is a Feature Request
Graduation calls now happen bi-weekly, changing the frequency of the community calls.
The community calls now happen bi-weekly
What would you like to be added
Why is this needed
Community calls happen every week, but now, with Graduation, we want to prioritize it, and because of this, we are using the same Community call every other week. Because of this, we need to reflect the change of frenquency of the community calls and add the Graduation call to the website.
Page to Update or indicate if it is a new page (provide the full path):
Update event page
https://www.kubeflow.org/docs/about/community/
Additional details:
As an example:
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: