Open anishasthana opened 1 month ago
cc @andreyvelich
/good-first-issue
@andreyvelich: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
/assign me
@anishasthana: GitHub didn't allow me to assign the following users: me.
Note that only kubeflow members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign @anishasthana
@andreyvelich Should we move some of the contents of https://github.com/kubeflow/community/blob/master/wgs/wg-governance.md#all-leads over to https://www.kubeflow.org/docs/about/membership/? So there aren't two sources of truth for WG leads and chairs.
@andreyvelich Should we move some of the contents of https://github.com/kubeflow/community/blob/master/wgs/wg-governance.md#all-leads over to https://www.kubeflow.org/docs/about/membership/? So there aren't two sources of truth for WG leads and chairs.
Sure, maybe we can combine information from https://github.com/kubeflow/community/blob/master/wgs/wg-governance-requirements.md and https://github.com/kubeflow/community/blob/master/wgs/wg-governance.md, and write it into website.
I would suggest to remove those docs from the kubeflow/community
after it.
This follows up on #3827
Add a section for WG Leads and WG Chairs