Closed rimolive closed 4 months ago
@kimwnasptd are you alright with the organizer change and should we switch to the new Zoom as well?
As it says at the top of this file, never remove a recurring meeting from this file otherwise it will end up in the calendar forever.
You have to move it to the legacy section and set its end date in the past.
My apologies to that. I made the changes as requested.
cc @kubeflow/kubeflow-steering-committee @juliusvonkohout @kimwnasptd
/lgtm
I will probably add the new zoom bridge in a follow up PR.
/lgtm
/assign @yuzliu
/lgtm
I just saw that the proposed meeting is named Kubeflow Platform Meeting (Manifests + Security WG)
.
It's hard to imagine that "Kubeflow Platform" should not also involve the distribution owners? I am not sure we should be calling the meetings "Kubeflow Platform" if they are only referring to Manifests/Security WGs.
I just saw that the proposed meeting is named
Kubeflow Platform Meeting (Manifests + Security WG)
.It's hard to imagine that "Kubeflow Platform" should not also involve the distribution owners? I am not sure we should be calling the meetings "Kubeflow Platform" if they are only referring to Manifests/Security WGs.
Then lets ask @andreyvelich @terrytangyuan @jbottum what they think. Based on what they decide we could change it.
From my perspective, this meeting should be the main place for users if they have questions related to Kubeflow Platform components. For example, questions about Profile Controller, KFAM, Central Dashboard, etc.
Distributions should certainly join these calls since they are main consumers of Kubeflow Manifests.
From my perspective, this meeting should be the main place for users if they have questions related to Kubeflow Platform components. For example, questions about Profile Controller, KFAM, Central Dashboard, etc.
Distributions should certainly join these calls since they are main consumers of Kubeflow Manifests.
Can you approve it then or do we have to make changes?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: terrytangyuan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
CC @kimwnasptd @akgraner for review