community

community copied to clipboard

This repo should verify-codegen

3

It'd be nice if we had a verify-codegen PR check for this repo, it seems we constantly mess this up: #808, #806, and then in the latest changes #802 #801

benmoss

How do we transition func Task Force to a Functions Working Group?

1

See above, what's the checklist of things?

omerbensaadon

[policy] 'Supporting' K8s versions that have reached their end-of-life

2

Related thought: we should probably be specific about how we might handle cases like the above, where there is a supported version of knative with an EOL k8s version. We...

dprotaso

PROCESS CHANGE: Rename the repo eventing-natss to eventing-nats

10

releated issue https://github.com/knative-sandbox/eventing-natss/issues/145 For we will both support nats streaming and nats jetstream,so rename the repo to `eventing-nats` so that it hosts all NATS related eventing components, NATS/JetStream Channel/Source/Sink/Broker.

zhaojizhuang

PROCESS CHANGE: Should we disable the auto-closing issue robots

4

Via this twitter thread: https://twitter.com/BenTheElder/status/1407786826413207555 Relevant k8s issue: https://github.com/kubernetes/kubernetes/issues/103151

julz

/assign @julz From the 18 May 2021 Security WG meeting.

evankanderson

Security WG: Engage with Eventing

1

evankanderson

Have the VMT sign up for the disclosure lists for upstream dependencies

2

At a minimum: * Kubernetes * Envoy * Istio / Contour / Gloo / Ambassador (?) * CloudEvents * Kafka (?) * RabbitMQ (?) At a minimum, we shoud be...

evankanderson

We now have a community contact rotation for eventing and other WGs, but there's no great way to notify people when they're up next in the rotation. This seems like...

grantr

New Repo: kn-plugin-source-github

4

## Repo information Org: knative-sandbox Repo: kn-plugin-source-github Purpose (Description): The `kn` plugin for for GitHub events source Sponsoring WG: client ## Actions to fulfill This area is used for the...

maximilien