> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-steering-committee/working-group/working-groups/working-group-meeting-notes/2026/february-26-2026.md).

# February 26 2026

### Attendees: 

| Name                                                 | Attendance | Role                                  |
| ---------------------------------------------------- | ---------- | ------------------------------------- |
| [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes        | WG Lead/Secretary                     |
| Thiago Nunes                                         | Yes        | Intersect Member                      |
| Vaibhav S                                            | Yes        | Intersect Member                      |
| Maureen Wepngong                                     | No         | DRep                                  |
| Terence McCutcheon                                   | No         | Intersect                             |
| Lorenzo Bruno                                        | Yes        | Head of Product Curation at Intersect |
| Jose Miguel De Gamboa                                | No         | ISC Voting Member                     |
| Randy                                                | No         | <p><br></p>                           |
| Wilco van de Burgwal                                 | Yes        | <p><br></p>                           |
| Veleria Devaux                                       | No         | <p><br></p>                           |
| Gnobudy John                                         | No         | <p><br></p>                           |

Recording: [Intersect Governance WG Weekly - 2026/02/26 14:59 CET - Recording](https://drive.google.com/file/d/1YXYWR9XrpfBxUC4V8QvzuxvjqVujyJro/view)

Transcript: [Intersect Governance WG Weekly - 2026/02/26 14:59 CET - Transcript](https://docs.google.com/document/d/112MCfAwu4K0rGTsrFdzeGmcuMtHFHVtOwiv3r2-Dc8c/edit?tab=t.0#heading=h.pa2ji27f8hfp)

### Agenda

* Committee Members Role & Responsibilities
* Chair and Vice Chair Policy

### Decisions/Actions

| Discussion Point                  | Notes                                                                                                                                                                                                                                                                                                                                                               | Actions: Responsible / Note                                                                                                                 |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Chair & Vice Chair Policy         | <p>- Fixed conflicting text regarding terms; changed layout to alpha-numeric format for better cross-referencing.</p><p>- No-Confidence Motions: Kept internal to committee voting, while behavioral/whistleblower complaints will be routed through secretaries to protect member identities.</p>                                                                  | Lorenzo: Bring the finalized policy to the ISC next Monday for a formal closing vote.                                                       |
| Committee Member Responsibilities | <p>- Thiago and Gintama argued that checking and replying to their specific committee Discord channels should be a mandatory duty (not a recommendation), given their monthly stipend.</p><p>- Lorenzo noted that strict mandates are difficult for volunteer roles, but the workload can be balanced dynamically between chairs, vice chairs, and secretaries.</p> | Lorenzo: Add a baseline communication responsibility to the text, ensuring it allows the chair and vice chair to split the workload.        |
| Discord Structure & Tracking      | <p>- The current Discord setup makes navigation and accountability difficult. Wilco flagged severe inactivity in the MCC.</p><p>- Gintama noted that server engagement can be fixed by implementing a proper roles-and-permissions hierarchy.</p>                                                                                                                   | Gintama: Draft and send a Discord optimization and contribution-tracking blueprint next week.                                               |
| MBO Budget Mechanics              | - Clarified that chairs sign contracts purely to verify that funds match what the committee/DReps approved; actual project execution is the legal responsibility of the contracted entity, not the committee.                                                                                                                                                       | None (Clarification).                                                                                                                       |
| Document Strategy & Roadmap       | - The group agreed to pass a high-level "Version 1" baseline document now rather than delaying for perfection.- Wilco suggested structuring future proposals to clearly show: Current State → Flaws → Proposed Improvements.                                                                                                                                        | Lorenzo: Expand the document's introduction to contextualize the current state.Working Group: Provide final text feedback over the weekend. |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://committees.docs.intersectmbo.org/intersect-steering-committee/working-group/working-groups/working-group-meeting-notes/2026/february-26-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.