Add WG Deployment and Manifests

[PatrickXYS]

Given WG deployments and manifests have established and PRs have merged.

kubeflow/community#402

kubeflow/community#435

Creating two teams to own kfctl and manifests repo.

[kubeflow-bot]

This change is 

[PatrickXYS]

/cc @Bobgy @jlewi @yanniszark @Jeffwan

[yanniszark]

This is interesting!
So the procedure is something like:

1. Add new workgroup in kubeflow/community.
2. Add group in internal/acls. (this could be automated)
3. Add leads to OWNERS files in the respective repos (this can't really be automated since not all leads are relevant to all projects).

@PatrickXYS is there a place where this procedure is documented.
Also, I am surprised that we give write access to repos. Why is this needed?
Shouldn't everything go through OWNERS files and the k8s-ci-bot or am I missing something?

[jlewi]

@yanniszark it should probably be documented somewhere in community; probably in one of these docs.
https://github.com/kubeflow/community/tree/master/wgs

Also, I am surprised that we give write access to repos

I believe write access is needed to cut branches and releases. I consider this as a stop gap. Giving more and more folks write access isn't going to be scalable but for now its ok.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi, PatrickXYS

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jlewi]

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

[yanniszark]

@jlewi thanks for the info :)