Studio planning, 10:00 UTC Thursday June 15th 2023

[asyncapi-bot]

Meeting Info	Details
Purpose	Discuss Studio planning
Time	10: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.

[rajendrakashi]

G'day,

I was listening to youtube channel - thx for introducing this new methology. I have a doubt and curiosity in regards to the dependency between the pitches - appreciate if you clarify Example, If a person bet on one of the pitch that he/she can not make in that cycle which is blocking for next pitch.

[rajendrakashi]

And another request, I am a solution designer - how can I contribute?

[derberg]

@fmvilas hey, you have some questions ☝🏼 and also I guess the stream took place and you can close this issue already

[fmvilas]

@fmvilas hey, you have some questions ☝🏼 and also I guess the stream took place and you can close this issue already

Thanks, @derberg! 🙏

G'day,

I was listening to youtube channel - thx for introducing this new methology. I have a doubt and curiosity in regards to the dependency between the pitches - appreciate if you clarify Example, If a person bet on one of the pitch that he/she can not make in that cycle which is blocking for next pitch.

We bet on pitches/issues as a community or group of recurring contributors and maintainers. So the responsibility is not on a single person. We always try to make sure we plan stuff we'd be able to accomplish in 6 weeks. If for some reason we can't finish during the cycle, it gets postponed to the next cycle (and even during the 2 weeks in between cycles). That's not usually the case in Shape Up but we're not that strict given that not everyone can work full-time on AsyncAPI.

Our aim with Shape Up here is to have a more or less reliable timeframe and a set of priorities to work on as a group. We're not a company and we don't have customers so it's ok to "not be on time".

And another request, I am a solution designer - how can I contribute?

Have a look at https://shapeit.app/projects/org/asyncapi/16 and pick an issue that is not yet started. Leave a comment in the issue saying that you're starting to work on this issue, and that's it. Also, joining Slack #04_tooling channel and commenting there helps to raise awareness.

Once you start working on an issue, make sure you give somewhat regular updates so everyone knows you haven't abandoned it 😄 Reach me out on Slack or reply here if you still have questions and I'll be happy to guide you.

[fmvilas]

I'm closing the issue since this meeting already finisihed but feel free to continue the conversation.