Spec 3.0 Meeting, 16:00 UTC Wednesday July 19th 2023

[asyncapi-bot]

Meeting Info	Details
Purpose	This is the meeting for community member involved in works related to 3.0 release of AsyncAPI Specification.
Time	16:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Place for your topic
3. Q&A

Notes

Add notes here after the meeting.

[derberg]

Meeting was fully about @fmvilas idea about tracking progress on 3.0 implementation

AI notest:

• Fran, Sergio, and Lukasz were discussing technical issues and preparations for a video call. They were planning to start the call and Fran was going to lead the discussion. - PLAY @0:01:
• Fran and Sergio discussed how to better organize their work on the specification for launching version three. They proposed splitting the tasks into deliverables and focused on enabling early validation and adding support for documentation and code generation. - PLAY @6:59:
• Fran and Lukasz discussed the plan for migrating to version three of the project. They decided to prioritize completing React components, parser, template, and mark, and partially completing the server API. They also discussed the importance of involving the community in the migration process and encouraging new contributors to pick specific tasks. - PLAY @17:42:
• Fran proposed splitting tasks in a different way to release version three and provide value to both end users and other contributors with different priorities. The goal was to prioritize finishing the parser and JSON schema file to enable the use of the new React component and minimize dependencies. - PLAY @23:30:
• Fran and Lukasz discussed the approach of delivering value in each deliverable by focusing on specific features and dependencies. They planned to enable validation support on Studio and CLI, migrate React components and templates, and gradually provide more value until everything is migrated. - PLAY @25:54:
• Lukasz and Fran discussed the organization of tasks and dependencies for their project. They decided to group tasks by feature and prioritize completing cycle one before moving on to cycle two. - PLAY @37:28:
• Fran and Sergio discussed the idea of organizing tasks in cycles and using a visual tool to track progress. They debated whether cycles should be strictly followed or used as a clue for prioritizing tasks, ultimately deciding that organizing tasks based on value and delivering incremental value was more important. - PLAY @49:37:
• Fran and Sergio discussed the challenges of breaking down a big project into smaller tasks and how to assign tasks in Shaper. They also considered the idea of creating issues for each screen and agreed that it would improve communication and organization. - PLAY @1:01:00:
• Sergio, Fran, and Lukasz discussed the advantages of a project management approach that hides unnecessary dependencies and allows for a quick overview of progress on each task without the need to click through multiple cycles. They also mentioned that the tool they were using was not designed for the shape-up approach, but they found ways to adapt it for their needs. - PLAY @1:10:32:
• Fran, Lukasz, Sergio, and others discussed the progress tracking and completion indicators for the Studio project cycles. They mentioned plans to add indicators for completion progress and discussed the challenges of integrating authentication with GitHub for plug previews. - PLAY @1:16:13:
• Fran, Sergio, and Lukasz discussed the idea of releasing version 3 of a tool before completing all the features, in order to provide value to potential contributors. They also talked about the need to improve the documentation and address issues related to clarity and examples based on the previous version. - PLAY @1:23:20: