Suggestion to extend CODEOWNERS with new contributor

[derberg]

@fmvilas I'd like to propose we extend list of codeowners for the specification and the json schema repo. I hope @dalelane agrees 🙏🏼

@dalelane, even though affiliated with IBM, demonstrated several times that he is a great community member and helped in many specification-related works that were not directly beneficial only to IBM. What I mean is that from my perspective Dale demonstrated he can be trusted to help in spec maintenance for the good of the community and not the company he works for:

• Dale voluntarily coordinated latest 2.3 release of AsyncAPI specification (https://www.asyncapi.com/blog/release-notes-2.3.0). This makes him learn contributing guide in practice.
• Dale is working on a PR to improve current release process basing on 2.3 release experience
• Dale helps a lot in the community in spec topic related to Kafka:
  • Helped to extend security part of the spec feat: add SASL security scheme types for use by Kafka specs #502
  • Writes articles in his private blog about AsyncAPI and Kafka https://dalelane.co.uk/blog/?p=4219
  • Is also a code owner of Kafka binding https://github.com/asyncapi/bindings/blob/master/CODEOWNERS#L11
• Dale not only cares about the spec but also related tools, he is a codeowner for Avro Schema parser -> https://github.com/asyncapi/avro-schema-parser

Technically speaking, @fmvilas I'd love to have Dale as codeowner:

• here https://github.com/asyncapi/spec/blob/master/CODEOWNERS#L8
• here https://github.com/asyncapi/spec-json-schemas/blob/master/CODEOWNERS#L9

@dalelane I hope you accept 🙏🏼 I personally would be honored 🍺

P.S. I summarized your achievements for the first time while writing this issue. I have to say you raised a bar for new potential code owners pretty high 😆 and I bet I did not mention all topics

[fmvilas]

Huge YES from my side ♥️🙌🎉

[dalelane]

That's very kind, I'd love to - thank you!

[fmvilas]

PRs created ☝️

[asyncapi-bot]

🎉 This issue has been resolved in version 2.3.1-2022-04-release.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[asyncapi-bot]

🎉 This issue has been resolved in version 2.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀