StackStorm TSC Meetings

[arm4b]

When

Every 2nd Tuesday of the month, 09:30 AM US Pacific time @StackStorm/TSC members (see OWNERS.md) are gathering for 1 hour to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed.

These meetings are open and we invite others to join them to be up to date with the latest project developments and progress.

Where

• Video Conference Link: https://meet.jit.si/StackStormTSC
  • If Jitsi unavailable - backup Zoom room: https://us02web.zoom.us/j/81082101702?pwd=N1V4TWdYRVQ4SXBsaFh1TFYvVDA0UT09
• Dial-in access info: https://meet.jit.si/static/dialInInfo.html?room=StackStormTSC
• Add to your calendar .ics
• 

Time zone distribution for the ST2 TSC members: https://www.worldtimebuddy.com/?qm=1&lid=5368361,4140963,12,2267057&h=5368361&date=2020-3-3&sln=9.5-10.5

Previous meetings and history

https://github.com/StackStorm/discussions/issues?q=is%3Aissue+is%3Aopen+label%3ATSC%3Ameeting

Meeting Agenda

To respect each other time, every meeting should have an Agenda ordered by priority, highlighting what are the plans so others are prepared with their updates, questions, answers, and opinions.
Example: #31

Drafting the Meeting Agenda

7+1 days before the meeting, the host should share in the #tsc Slack channel meeting agenda draft, so other members could propose more topics to discuss.

Publishing the Meeting Agenda

7 days before the meeting, the host should post in the Community new Issue with the meeting agenda.

Meeting Minutes

Every meeting should have a high-level report describing what topics were discussed, what decisions were made by the team and who was present from the @StackStorm/tsc.
Example: #1

Offline/Async Discussions

While some high-level ideas could be discussed live, many topics need deeper technical research, argument, design, follow-up and thought.
We encourage creating proposals with the detailed problem overview and possible solutions with pros/cons research, so others (including community members) can provide their insight and be part of the discussion before the decision takes place. This helps avoiding overloading the monthly meetings and solve the problems as they arise in async and remote-friendly way.

This could be done by opening a new Issue in StackStorm/discussions repository per StackStorm GOVERNANCE. History of Proposals and Discussions: https://github.com/StackStorm/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Aproposal