community
community copied to clipboard
New Repo: knative/eventing-kafka
Repo information
Org: knative
Repo: eventing-kafka
Purpose (Description):
For storing all the Kafka components we have. Related to breaking down the overloaded eventing-contrib repo.
for Kafka components we have users and APis are stable, and are already at v1beta1 level. unlike other pieces of eventing-contrib, it does not seem right to move the KafkaSource and KafkaChannel to the sandbox.
Sponsoring WG:
- Eventing-Delivery
Actions to fulfill
This area is used for the TOC to track the repo creation process
-
[ ] Add this issue to the TOC project board for review.
-
[ ] Send a PR adding entries for this repo in
/peribolos/knative-sandbox.yaml- [ ] Add the repository and a description.
- [ ] Grant
Knative Admintheadminprivilege. - [ ] Grant the sponsoring WG the
writeprivilege.
Once the TOC has approved the above, it will merge and Peribolos will create an empty repository.
-
[x] (golang) Send a PR to add aliases for
knative.dev/$REPONAMEimport 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 master -
[ ] Set up test-infra following the docs linked at the beginning.
-
[ ] Create a sample PR to verify Prow (e.g. edit the boilerplate README)
Once Prow has been verified.
- [ ] Have a member of the TOC enable branch protections so that
tideis a required presubmit check.