chore: add Essential Building Blocks working group

[jonaslagoni]

Description

TODO:

•  Align on description and name
• Create a discussion proposing the working group for the TSC
• Create the proper channels, projects, etc after approval

[jonaslagoni]

@m-wild @lorenzsimon @VisualBean @Pakisan @Souvikns I made a suggestion here about what to call the working group and its description, please have a look and feel free to suggest something completely different ✌️

After we all agree I am gonna create a discussion proposing the working group (same as here https://github.com/orgs/asyncapi/discussions/1094) for the TSC before finishing the PR.

[lorenzsimon]

Let me also throw Tooling Core into the ring. (As the working group name)

[m-wild]

Is it worth trying to say these are building blocks for the different language ecosystems, rather than core to asyncapi? Maybe there's no difference?

[jonaslagoni]

Is it worth trying to say these are building blocks for the different language ecosystems, rather than core to asyncapi? Maybe there's no difference?

I see them as being no different from one another, they are core to AsyncAPI as a whole as well as the different language ecosystems 🤔

[jonaslagoni]

Gonna fix this later after the TSC voting process

[smoya]

I would love to see the OKRs before voting :P

[jonaslagoni]

@smoya we have not discussed how we want to measure how we are doing, if we even want to use OKRs for the working group.

We have a common direction, that indeed is a bit vague yet, but getting more concrete after every meeting.

If you want to dive into the current thoughts on what we want to do, look at the last meeting (recap in the issue)

[thulieblack]

@fmvilas please create the @essential_building_blocks_wg team 😉

[smoya]

@fmvilas please create the @essential_building_blocks_wg team 😉

Suggestion: to prefix all teams in gh, and channels or groups in Slack with wg- so it gets easy and intuitive to find them. Just suggesting.

[jonaslagoni]

Thanks @thulieblack ✌️