> For the complete documentation index, see [llms.txt](https://steeringcommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://steeringcommittee.docs.intersectmbo.org/working-group/working-groups/working-group-meeting-notes/2025/may-22-2025.md).

# May 22, 2025

## Attendees: 

<table data-header-hidden><thead><tr><th width="217.5234375"></th><th width="162.625"></th><th></th></tr></thead><tbody><tr><td>Name</td><td>Attendance</td><td>Role</td></tr><tr><td><a href="mailto:simo.simovic@intersectmbo.org">Simo Simovic</a></td><td>Yes</td><td>WG Lead/Secretary</td></tr><tr><td>Phil Lewis</td><td>Yes</td><td>ISC Member</td></tr><tr><td>Thiago Nunes</td><td>No</td><td>Interim ISC Member</td></tr><tr><td>Pedro Lucas</td><td>Yes</td><td>OSC Chair, Representing two Enterprise Members</td></tr><tr><td>Nicholas Cerny</td><td>Yes</td><td>Civics Committee Chair</td></tr><tr><td>Vaibhav S</td><td>Yes</td><td>GMC Member</td></tr><tr><td>Naushad Fouze</td><td>Yes</td><td>Product Committee</td></tr><tr><td>Jose Iadicicco</td><td>Yes</td><td>Community Member</td></tr><tr><td>Maureen Wepngong</td><td>Yes</td><td>DRep</td></tr><tr><td>Terence McCutcheon</td><td>Yes</td><td>Intersect</td></tr><tr><td>Tevo Saks</td><td>No</td><td>Community Member</td></tr><tr><td>Nana Safo</td><td>No</td><td>DRep</td></tr></tbody></table>

Recording: [Intersect Governance WG Weekly - 2025/05/22 15:57 CEST - Recording](https://drive.google.com/file/d/1qXVuMs95I03MGc6nS5bK5uPnQsEPibeY/view)

Transcript: [Intersect Governance WG Weekly - 2025/05/22 15:57 CEST - Transcript](https://docs.google.com/document/d/1wKc9Ph5RmcNY497sfZan76WqYfNLLAnoIAMzABj-4tU/edit?tab=t.0#heading=h.drj5vvn54wrj)

## Agenda

* Update from last week
* Voting Members
* Document Review
* Recommendations Discussion

## Decisions/Actions

<table data-header-hidden><thead><tr><th width="166.25"></th><th></th><th></th></tr></thead><tbody><tr><td>Discussion Point</td><td>Notes</td><td>Actions: Responsible / Note</td></tr><tr><td>Voting Member Criteria and Quorum</td><td>Discussion on defining who is eligible to be a voting member of the WG, including ideas such as attendance thresholds (e.g., 3 meetings to join, 2 missed to drop off). Agreement to start with a list and adjust if needed.</td><td>Simo: Track attendance and maintain list of voting members; group agreed on a flexible threshold-based approach.</td></tr><tr><td>Recommendation Register &#x26; Problem Framing</td><td>Discussion on improving how issues are entered into the recommendation register, emphasizing clarity in problem statements before discussing solutions.</td><td>All members: Review and revise entries to clearly state problem statements; flag high-priority items for next meeting.</td></tr><tr><td>Election Transparency and Voting Stats</td><td>Debate on the value and risks of live voting stats and dashboards. Pros: improved transparency and campaign adaptation. Cons: strategic voting, potential bias.</td><td>Marine, Gintama: Reframe suggestions as problem statements and update register; Phil: Flag topic for further review next session.</td></tr><tr><td>One-Person-One-Vote Concerns</td><td>Concerns about sybil resistance, especially for board elections. Suggestions included KYC, participation tracking, and merging multiple accounts under one identity.</td><td>Phil: Mark sybil resistance for board election as high priority; Lorenzo, Pedro: Explore options for identifying and merging accounts.</td></tr><tr><td>Technical Barriers to Membership</td><td>Issue raised that wallet-based payments for membership are not functioning consistently. Impacts community participation.</td><td><br></td></tr><tr><td>Meeting Structure and Time Use</td><td>Agreement to structure meetings with focus on problem statements first, and reserve time for solution ideation. Consider asynchronous collaboration or breakout sessions.</td><td><br></td></tr></tbody></table>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://steeringcommittee.docs.intersectmbo.org/working-group/working-groups/working-group-meeting-notes/2025/may-22-2025.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.