Invite Heiko Henning to join as code owner about spec

[GreenRover]

Thanks for this honor. I am happily accepted the nomination.

[GreenRover]

The PRs are created:

• #1017
• asyncapi/spec-json-schemas#489
• asyncapi/bindings#241

@fmvilas I try to earn me code ownership for parser-js may be later. I guess there are enough open todos.

[fmvilas]

Yeah, don't get me wrong, I don't know if you deserve to be a code maintainer of the parser or not. I just wanted to clarify that becoming a code owner of the spec gives you the right to become code owner of bindings and spec-json-schemas but not other stuff. Or at least that's what I remember we discussed 😄

[smoya]

Yes Yes Yes!🙌

[derberg]

Sounds good to me 🚀 Through request/reply work I'm sure @GreenRover learned a lot on how things work here and how the process of adding features looks like, and how important it is to accommodate different use cases.

[char0n]

Of course yes, we all remember request/reply exceptional work ;)

[smoya]

@dalelane I think your vote is the only one missing here 🙏 I see you have a 👍 in the issue description but I believe better to be explicit in a comment if you don't mind.

[dalelane]

sorry - yes, happy to support this

[smoya]

@GreenRover if you are still into this, do you want to create a PR adding your user to the CODEOWNERS file on:

• https://github.com/asyncapi/spec
• https://github.com/asyncapi/spec-json-schemas
• https://github.com/asyncapi/bindings
• https://github.com/asyncapi/parser-js (not sure if you are happy with this one as well 🤔. I don't recall if you ended up working on it)

[fmvilas]

I think parser shouldn't be included. Just spec, spec-json-schemas, and bindings.

[smoya]

I recently announced it in Slack. @thulieblack will schedule a Tweet for ~tomorrow. (Thanks!)

Closing the issue