Closed quetzalliwrites closed 9 months ago
I suggest we clarify in the description of this issue that this doc should be based on AsyncAPI Spec version 3.
assigned to @Trohit20 (ignore mistake PR from Mahfuza 😄✌🏽)
Working on it. Thank you
how is this one going, @TRohit20? 😄
Hey @alequetzalli , Just wrapped up working with the Reply Info Draft referring to this issue. Will set up a Knowledge sharing call with SME the coming week and start working on the draft related to this issue. I will make sure to share the outline with SME and @alequetzalli soon after and start working on it. Thanks!!
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience :heart:
@alequetzalli Resolved via #2231 Please verify from your side.
The issue in context is now resolved as PR #2231 (merged) adds the document intended to the AsyncAPI website. Hence, closing the issue.
As part of Google Season of Docs 2023 at AsyncAPI, we're going to write in-depth explanations of the different sections of an
AsyncAPI document
to avoid difficulties in implementing EDAs.This task is part of the Docs EPIC: https://github.com/asyncapi/website/issues/1507.
For this issue, we'll cover: