Aside from the overall instructions within the Architecture Community Basics page, we also have some basic principles within the community:
<aside> 👉🏼
Adapt these, add or remove, as you see fit in your organization.
</aside>
There is a community session every two weeks, which happens [onsite/hybrid/remote] at [location], (time). The structure of a standard session is described below. This structure is used as a template for the Session Records.
The main goal of the meeting’s format and structure is to keep the decentralized software architecture ways of working in motion, not to make as many decisions as possible within that meeting. Therefore, this meeting enables helpful discussions, findings, and decision-making that happen often asynchronously or during other ad-hoc sessions.
Occasionally, we may use the session slot for community retrospectives, knowledge transfers, co-creating new architecture designs and plans, etc. The facilitator will plan and notify the community beforehand.
We use this table to record and share each meeting’s most relevant notes and action points. The recording URL for each recorded session is also included.
Architecture Community - Session records
Here, you’ll find the most critical data for the topics discussed in the community, synchronously and asynchronously: action points, meeting notes, links to decisions, additional material, etc.