community: Add WG Chair and Tech Lead sections. Fixes #3890

[puwun]

Description of Changes

Added detailed sections for WG Chair and WG Tech Lead roles to the community membership documentation content/en/docs/about/membership.md

Related Issues

Closes: #3890

Checklist

• You have signed off your commits
• Ensure you follow best practices from our contributing guide.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign johnugeorge for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• content/en/docs/about/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[google-oss-prow]

Hi @puwun. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[github-actions]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[Arhell]

/ok-to-test

[juliusvonkohout]

WHat is the purpose of the PRß is this aligned with the KSC ? CC @varodrig

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thesuperzapper]

Holding for now, as I dont think there has been a discussion about changing/formalizing the WG Chair / Tech Lead roles on the website.

/hold

[andreyvelich]

@chasecadet @thesuperzapper @franciscojavierarceo @juliusvonkohout This PR should fix this issue: kubeflow/community#972 ?
Shall we merge it and iterate over time to improve it?

[thesuperzapper]

As discussed in KSC meeting, let's preference doing this in the community repo.

I also think we have not agreed on the process to become a working group lead/chair.

Previously it was simply by the recommendation of existing leads, confirmed by KSC. It also seems that we should have a discussion with the working groups before making changes.