Document Repository Setup

[jlewi]

Now that we have multiple repositories in the GitHub org we should standardize and document how repositories should be configured.

Background
#22
kubeflow/training-operator#433

Some things to cover

• Setting up Prow and basic tests
• Per Disable GitHub review requirement and rely on prow? #22 we don't want GitHub to require pull request reviews because we will rely on prow and tide to merge PRs based on /lgtm & /approve
• Reviewable should not be configured as a status check because this blocks tide (tide plugin should ignore Reviewable and possibly other status checks kubernetes/test-infra#7140)

[gaocegege]

I think it should be in high priority since the docs in tf-operator is outdated and the users may be puzzled.

[jlewi]

@gaocegege Which docs? Why would users be affected by repository configuration?

[gaocegege]

@jlewi Not the config, I mean that the README in tf-operator is outdated. For example, we have no master now but the README is not updated. If we have docs repository we could put all docs in one repo and there is no consistency problem between different repos.

[jose5918]

I'll take this since I just started the process of setting up the PyTorch repo

[jlewi]

/assign @jose5918

[jose5918]

Still working on it kubeflow/testing#72, but will finish documenting once I get through all the rough spots and actually have a fully set up repo.

[jlewi]

Some additional things we should document here