community
community copied to clipboard
knative
Knative governance and community material.
## Repo information Org: knative-sandbox Repo: kn-plugin-source-gitlab Purpose (Description): Code for `kn` plugin for GitLab event sources Sponsoring WG: client ## Actions to fulfill This area is used for the...
#Repo information Org: knative-sandbox Repo: kn-plugin-curl Purpose (Description): Contains the `$kn curl ` plugin that make it easy to curl Knative services See https://github.com/knative/client-contrib/issues/77 Sponsoring WG: client ## Actions to...
## 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...
Now that we have a (draft, pending) security policy, we should have a corresponding issue template, or several if appropriate. This is especially useful to the extent we can create...
In many places we refer to "alpha", "beta", and "stable" or "GA" API levels, but these are not formalized anywhere. We should explicitly define the properties of these different levels...
Things to include with your process proposal (delete this text): Since knative is now under CNCF, there is little to no benefit to keep a separate Trademark charter and rights....
Hi everyone, in my project I use Traefik to handle all of my ingress functionality and I'm looking to use knative to make all of my deployments serverless. My question...
# Changes This is a proposal to add the coverage level for Usable and Stable components. Even if the levels are not ok, we should be explicit about how much...
right now: knative.dev/serving redirects to pkg.go.dev/knative.dev/serving knative.dev/pkg redirects to pkg.go.dev/knative.dev/pkg But: https://knative.dev/net-kourier does not forward to https://pkg.go.dev/knative.dev/net-kourier and the same for all other go repos. Seems like the implementation for...
