website: Create Kubeflow Governance Section

[andreyvelich]

As part of CNCF graduation, we should define clear Kubeflow Governance structure: kubeflow/community#655

Right now, governance information is separated between kubeflow/community and kubeflow/website.

It would be nice to create dedicated Website page called Kubeflow Governance under About section: https://www.kubeflow.org/docs/about/, which summarize all Kubeflow committees and highlight members in those groups.
Similar to how Jupyter shows its governance overview: https://jupyter.org/governance/overview.html

For example, these sections can be in the governance section: https://www.kubeflow.org/docs/about/community/#kubeflow-steering-committee

Additionally, that will give folks recognition for the work they are doing.

Kubeflow Working Groups.
Kubeflow Outreach Committee
Kubeflow Steering Committee.

cc @kubeflow/kubeflow-steering-committee @varodrig @chasecadet @jbottum

/good-first-issue

[google-oss-prow]

@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.

In response to this:

As part of CNCF graduation, we should define clear Kubeflow Governance structure: kubeflow/community#655

Right now, governance information is separated between kubeflow/community and kubeflow/website.

It would be nice to create dedicated Website page called Kubeflow Governance under About section: https://www.kubeflow.org/docs/about/, which summarize all Kubeflow committees and highlight members in those groups.
Similar to how Jupyter shows its governance overview: https://jupyter.org/governance/overview.html

For example, these sections can be in the governance section: https://www.kubeflow.org/docs/about/community/#kubeflow-steering-committee

Additionally, that will give folks recognition for the work they are doing.

Kubeflow Working Groups.
Kubeflow Outreach Committee
Kubeflow Steering Committee.

cc @kubeflow/kubeflow-steering-committee @varodrig @chasecadet @jbottum

/good-first-issue

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.

[varodrig]

agree. this is a great way to recognize our community and provide more clear information.

[juliusvonkohout]

Yes, there should be a single source of truth and probably most of the community repository should just be on the website.

[thesuperzapper]

Also, as this issue has been marked with "good first issue", I just want to warn any new contributors that there would be significant discussion on any such PR, and it would take a while to get merged.

It's likely better if someone who has at least some knowledge of the community raises the PR, so they can participate in the discussion.

---

Additionally, @andreyvelich @juliusvonkohout we need to agree what stuff will be on the website vs community repo.

I think it's best to have governance documents versioned as markdown files on the community repo (with its associated permissions), and only have the website be a non-binding "summary", including list of groups/members, and links to the actual documents.

[andreyvelich]

I agree that the gov documents can be in the community repo for versioning.
In the Kubeflow Website we can just have high-level information about each Kubeflow committee, list of participants, and redirect to the governance charters in kubeflow/community.

Initially, I expect the governance page just be very small that shows the 3 main entities of Kubeflow with their roles and members:
Kubeflow Working Groups.
Kubeflow Outreach Committee
Kubeflow Steering Committee.

For the KSC and WGs, we can just get information from here: https://www.kubeflow.org/docs/about/community/#kubeflow-steering-committee

[franciscojavierarceo]

In the Kubeflow Website we can just have high-level information about each Kubeflow committee, list of participants, and redirect to the governance charters in kubeflow/community.

+1

[terrytangyuan]

+1

[juliusvonkohout]

+1