search

knative / community

Knative governance and community material.
https://knative.dev/community
Other
252 stars 233 forks source link

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

Closed zhaojizhuang closed 7 months ago

zhaojizhuang commented 3 years ago

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 commented 3 years ago

cc @knative/technical-oversight-committee

devguyio commented 3 years ago

Thanks for stepping up @zhaojizhuang ! I'm so excited to have folks who want to grow our NATS support! @wallyqs might be interested in this as well !

evankanderson commented 3 years ago

I can help with the actual repo rename; reach out to me on Slack.

evankanderson commented 3 years ago

/assign

zhaojizhuang commented 3 years ago

@evankanderson Great! Thank you

I can help with the actual repo rename; reach out to me on Slack.

dprotaso commented 1 year ago

@evankanderson are you still working on this or should we close this?

dprotaso commented 11 months ago

/unassign @evankanderson

/assign @pierDipi

@pierDipi is this still important given the current state of eventing-natts?

dprotaso commented 11 months ago

Moving this off the TOC backlog

dprotaso commented 9 months ago

Talked about it - decided @pierDipi should make the call if this is still relevant as the eventing wg lead

dprotaso commented 9 months ago

Likewise @pierDipi it was noticed that the integration is actively maintained again - should it be on the release train?

aliok commented 7 months ago

/close

Closing this ticket after 3 years of no activity. Let's reopen if it becomes relevant again.

knative-prow[bot] commented 7 months ago

@aliok: Closing this issue.

In response to [this](https://github.com/knative/community/issues/666#issuecomment-2020216759): >/close > >Closing this ticket after 3 years of no activity. Let's reopen if it becomes relevant again. 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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.