Rename Knative Channels Working Group to Knative Eventing Delivery

[devguyio]

Description

During the approval discussion of the Channels Working Group with the TOC, the scope was increased to include all eventing delivery aspects of Knative. That means this includes topics such as broker eventing delivery efficiency, trigger filtering efficiency etc. So I propose to change the working group name to Eventing Delivery WG due to the following reasons:

1. Current name is confusing specially for new comers, they wouldn't expect that the broker or other higher level objects would be within its scope.
2. To highlight that this includes the delivery aspects of all Eventing Objects.

Changes if approved

1. Rename the WG name to Eventing Delivery Working Group
2. Change the following to reflect the new name
   1. Google Calendar invitation
   2. Google doc for the notes
   3. The folder on the shared Google Drive
   4. The slack channel

[matzew]

Discussion from last weeks call, see https://docs.google.com/document/d/1uxlulaAf2m_yZUqCIeI-inul2gsqP69PElnZdO0FHUo/edit

Aslom: the group contains more than just channels. So rename would make sense
Lionel: Sources are also delivering events

Summary: Delivery behavior defined here (in this group) should apply on _all_ components inside of Knative Eventing 

[akashrv]

I am a bit confused with the proposal and the direction here. As per our mission Eventing contains 3 parts - Developer Experience, Event Delivery, Event Sources (or ecosystem). Having sources as a separate WG made sense as it reuired dedicated focus. Also having dedicated focus on messaging channels esp to build expertise around different channel implementation such as kafka, and natss made sense. However expanding it to "overall event delivery" seems like something that the current Eventing WG should focus on isn't it? To put in other words - what is the charter or focus or current Eventing WG?

[matzew]

Fair point. So perhaps... not sure... we keep the Channels as something that messaging focused, and keep the overall "Eventing delivery" contract as the core of the Eventing WG ?

In an org. chart I see it like this

                            EVENTING WG
                          /              \
                        /                  \
                      /                      \
        SOURCES WG                      Channels WG

Reflecting the summary from last weeks Channel's call...

Summary: Delivery behavior defined here (in this group) should apply on all components inside of Knative Eventing

IMO keeping the delivery aspects on the Eventing WG, would match well, that this concept applies to all components in KNE

[aslom]

Discussed in February 13 WG meeting

[matzew]

Proposal to TOC for renaming:

https://docs.google.com/document/d/1cSTc9FA9DWS198OOQeUUHOicnvM0jAQNPMb_Ln297jc/edit#

[aslom]

Now that official WG name is Eventing Delivery to keep naming consistent in Slack we should rename eventing-channels slack channel to eventing-delivery? @Abd4llA @matzew @grantr

[aslom]

Slack channel was renamed and calendar updated - anything else left? Google doc was also updated.

Not sure about "The folder on the shared Google Drive" ? How do you find in which folder is google doc such as https://docs.google.com/document/d/1uxlulaAf2m_yZUqCIeI-inul2gsqP69PElnZdO0FHUo/edit#heading=h.6s9tvd9v01tq ?

[devguyio]

@aslom Drive directory was already renamed. This is the link of the drive https://drive.google.com/drive/u/0/folders/0APnJ_hRs30R2Uk9PVA

[aslom]

Great thank you @Abd4llA so after checking tomorrow in Eventing WG that issue may be closed?

[Harwayne]

/close

We think the renaming is done everywhere. If it hasn't we will fix the problems as we find them.

[knative-prow-robot]

@Harwayne: Closing this issue.

In response to [this](https://github.com/knative/eventing/issues/2401#issuecomment-628695000): >/close 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.