Date: 2026-07-15 20:00 to 21:00 UTC
Next Meeting: TBD
This meeting is the first meeting with the second set of role changes, as voted upon in the previous meeting on 2026-07-01. This meeting was facilitated by @prod, previously held by @PGComai between (2026-04-17) and (2026-07-01). Secretary duties are now held by @maidmage, previously held by @prod between (2026-04-17) and (2026-07-01). Leadership duties still remain under @Tomaterr, whose term has been extended to 2026-10-02. This is also @PGComai's first meeting as delegate, although the admin circle has yet to have an official meeting as of this time.
- @maidmage (secretary)
- @outfrost
- @PGComai (delegate)
- @prod (facilitator)
- @Tomaterr (leader)
- Determining a different method for scheduling meetings
- Discussing leadership styles and the role of the leader in our circle.
- Discussing the role of async community circle discussions on the forum and how it interacts with meeting structure.
- Recapping previous decisions made in previous meetings (specifically on the code of conduct) to ensure we are on the same page.
- This above agenda point has been pushed to next meeting, due to a lack of time in this current meeting.
- Creating a concretely defined inactivity system.
- Future Meetings will be determined using a custom "Master When To Meet" (https://prod.kr/tsuki/meeting) made by Prod. This will replace the previous system of making multiple when2meet links.
- Leadership is to remain as is. Outfrost and Tomaterr are to discuss any differences or concerns in a one-on-one outside of meetings.
- The community-circle forums are to be used as a space for ideation, but not decision making. Decisions will still be made inside of meetings.
- Individuals who are unable to make two consecutive meetings, without communicating to the circle reasoning for your absence, will be treated as inactive users.
- inactive users are not included in the headcount for attendance and forfeit their consideration towards any votes/decisions.
- inactive users are not immediately removed from the circle and can return to active status at any time. Removal of inactive users is a separate process that has not been discussed officially.
- Recapping previous decisions made in previous meetings (specifically on the code of conduct) to ensure we are on the same page.
- Deciding on how many people must be present in a meeting in order to make decisions (a quorum).
- More TBA
- There has been a concern of leadership falling out of sociocratic ideals. In previous meetings, there was a feeling that leadership had felt authoritarian or too boss-like, with unstated expectations on both work that needed to be done and when it needed to be done by.
- The "raising hand" feature has been noted to promote argumentative discussion that tends to focus around two individuals, which has had a negative effect on everyone's equal opportunity to speak during rounds.
- Due to issues regarding the admin circle over this term, the leader role's task of relaying information between admin and the community circle has been mostly irrelevant.
- While we as a circle are in agreement about using the forum for exploring ideas, a few concerns were brought up.
- Decisions should be held in meetings, and not asynchronously in the forums.
- There is a worry that the forum discussions would replace Sociocracy's Participatory Proposal Writing Process.
- There is a need to expedite the process of forum discussion and to bring said discussions to meetings. A few ideas were floated, but no decisions have been made officially.
- People who read a thread should note if they agree or disagree with the ideas, even if they do not have anything to add, or are unable to add to the discussion at the moment. If in agreement, @prod has suggested that people comment "I agree with this, let's propose this in the meeting".
- Summaries of the discussion could be made to help reduce the amount of reading.
- After the meeting it was noted that @Fuguesoft has joined one of the matrix channels for the Community Circle. We have realized that the text channel was accidentally public. A proper invite will be offered to @Fuguesoft, if they are indeed interested in joining the circle, and the channel permissions will be fixed.