-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Repo: eventing-ceph #234
Closed
1 of 10 tasks
Harwayne opened this issue
Aug 25, 2020
· 0 comments
· Fixed by knative-extensions/eventing-ceph#1, knative/eventing-contrib#1585 or knative/test-infra#2435
Closed
1 of 10 tasks
New Repo: eventing-ceph #234
Harwayne opened this issue
Aug 25, 2020
· 0 comments
· Fixed by knative-extensions/eventing-ceph#1, knative/eventing-contrib#1585 or knative/test-infra#2435
Comments
Closed
49 tasks
This was referenced Sep 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repo information
Org:
knative-sandbox
Repo:
eventing-ceph
Purpose (Description): Converts Ceph notifications to Cloud Events for use with Knative Eventing.
Sponsoring WG: Sources WG
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
Knative Admin
theadmin
privilege.write
privilege.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:
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.
tide
is a required presubmit check.Helps with knative/eventing-contrib#1482
FYI @lberk.
The text was updated successfully, but these errors were encountered: