Jonas Lagoni

Next couple of blocking issues to continue: cc code owners of spec: @derberg @fmvilas @dalelane - [x] https://github.com/asyncapi/spec/pull/753/ - [x] https://github.com/asyncapi/spec-json-schemas/pull/184 - [x] https://github.com/asyncapi/spec-json-schemas/pull/205 cc code owners of parser: @derberg...

@char0n updated 👍 > @jonaslagoni Could you add to the list [[3.0.0] Allow references to be used in any part of the specification](https://github.com/asyncapi/spec/issues/778) I can me mentor it of course....

The last blocker before RFC can move forward is https://github.com/asyncapi/spec-json-schemas/pull/221 cc code owners @derberg @fmvilas @dalelane

@GreenRover I added you to the list of champions for request/reply 🙂

cc current champions: @magicmatatjahu @smoya @jessemenning @Fannon @damaru-inc @char0n @GreenRover We should be completely ready to accept the 3.0 changes into the spec, JSON Schema documents, and parser so you...

@smoya added 👍

Sounds to me like a solid suggestion 👍 Unless we can detect these types of schemas in the parser, so you don't have to define anything 🤔 But that might...

### **{queue} problem** @prdatur cant figure out if this is a current problem you have or a suggestion for solution to request reply 😄 If it is a current problem...

> Would like to say we have forked 4 of the repos from https://github.com/asyncapi and have implemented the following: > > ``` > command: ... > request: ... > response:...

@195858 pinging @derberg again as it probably went under the radar. You can take a look at the [contributing guideline](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md#rfc-contribution-champions), as it describes the process of champion the issue through...