New Repo: `eventing-integrations`

[matzew]

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

Repo information

Org: knative-extensions

Repo: eventing-integrations

Purpose (Description):

The repository contains the integration images for data-plane parts of the Knative EventiSource and EventSink CRD. The generic EventSource and EventSink CRD is discussed on this feature track: https://docs.google.com/document/d/1UOEbi2kBgH65QaYa4fhvZRxlkUWrqKrptbe9PFDw1bc/edit

Sponsoring WG: Knative Eventing

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.

• [X] 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.

• [x] Send a PR adding entries for this repo in /peribolos/knative-extensions.yaml. Please mind the alphabetical order when adding to a list.
  • [x] Add the repository and a description.
  • [x] Grant Knative Admin the admin privilege.
  • [x] 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).

• [x] Have a lead from the sponsoring WG bootstrap the Git repository by using an appropriate "template" repository (basic, sample-controller, sample-source).

  Follow the instructions from Creating a repository from a template

• [x] Send a PR adding the repo to knobots. Then run the community files update action to propagate new OWNER_ALIASES.

• [x] Add your GitHub Team to the OWNERS file for your repo.

• [x] Set up prow for a new repo

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

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

• [x] 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 CLOMonitor (more information).

[aliok]

LGTM

TOC needs to approve.

I like the idea.

[pierDipi]

LGTM

[dsimansk]

+1

[dsimansk]

@knative/technical-oversight-committee PTAL

[psschwei]

+1 I guess technically the non-former-TOC folks on @knative/steering-committee should weigh in too

[dsimansk]

All applicable steps have been completed. The new repository is ready for source code contribs now.

Calling it a day! /close

[knative-prow[bot]]

@dsimansk: Closing this issue.

In response to [this](https://github.com/knative/community/issues/1611#issuecomment-2386389295): >All the applicable steps have been completed. The new repository is ready for source code contribs now. > >Calling it a day! >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.