New Repo: Infra

[krsna-m]

Use this issue type to request a new repo in knative-sandbox (or
knative, which may require additional discussion).

Repo information

Org: knative

Repo: Infra

Purpose (Description):
We discussed in Productivity WG meeting about splitting out the configs and other non-go related things to a new repo which would make more sense for new contributors and a landing spot for Productivity in general.

Sponsoring WG: Productivity

Actions to fulfill

This area is used to track the repo creation process.
The requestor and sponsoring WG lead should perform the steps listed below and cross out the checkmarks when done.
The TOC is involved only in the TOC Gate steps.

• Add this issue to the TOC project board for review. You are responsible for moving your entry on the board to "Needs Discussion" or "In Progress" as you move forward in this checklist.

You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the Add cards interface.

• Send a PR adding entries for this repo in /peribolos/knative-sandbox.yaml. Please mind the alphabetical order when adding to a list.
  • Add the repository and a description.
  • Grant Knative Admin the admin privilege.
  • Grant the sponsoring WG the write privilege.

TOC Gate: Once the TOC has approved the above, it will merge and Peribolos will create an empty repository.

• (golang) Send a PR to add aliases for knative.dev/$REPONAME import paths (sample).

• Have a lead from the sponsoring WG bootstrap the Git repository by pushing an
  appropriate "template" repository (basic,
  sample-controller,
  sample-source) to the new repository as
  a git remote. For example:

    git clone https://github.com/knative-sandbox/sample-controller.git
    cd sample-controller
    git remote add newrepo https://github.com/knative-sandbox/$REPONAME.git
    git push newrepo main

• Add your GitHub ID to the OWNERS file for your repo.

• Set up prow for a new repo

• Bootstrap your CI jobs using hack project (look at other sandbox repos for reference)

• Create a sample PR to verify Prow (e.g., edit the boilerplate README)

• Verify that within 24 hours the appropriate branch protections have been applied
  requiring tide to pass before PRs are merged.

• (optional) Send a PR adding the repo to knobots.

[rhuss]

+1 from the TOC for moving things forward.

Alternative would be:

• Move out tools to dedicated repos from test-infra and keep configs in test-infra (but that is much more work at the beginning).

[krsna-m]

Setup to a point where we can work from it. Thanks all