> 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/january-29-2026.md).

# January 29 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                      |
| Jose Iadicicco                                       | No         | Community Member                      |
| Maureen Wepngong                                     | Yes        | DRep                                  |
| Terence McCutcheon                                   | Yes        | Intersect                             |
| Lorenzo Bruno                                        | Yes        | Head of Product Curation at Intersect |
| Jose Miguel De Gamboa                                | Yes        | ISC Voting Member                     |
| Randy                                                | Yes        | <p><br></p>                           |
| Wilco van de Burgwal                                 | Yes        | <p><br></p>                           |
| Valeria Devaux                                       | Yes        | <p><br></p>                           |

Recording: [Intersect Governance WG Weekly - 2026/01/29 14:56 CET - Recording](https://drive.google.com/open?id=1Ppcki4ZAFLve2vDabSVxHiXZEo1R_oz6\&authuser=0)

Transcript: [Intersect Governance WG Weekly - 2026/01/29 14:56 CET - Transcript](https://docs.google.com/document/d/1PuBSPYjoV2sKKV3rRLiqdUpS4QPEetTx3c7lE22DSNQ/edit?tab=t.0#heading=h.kkhtzapu00mm)

### Agenda

* Committee Members Role & Responsibilities
* Extending Committee term

### Decisions/Actions

| Discussion Point                  | Notes                                                                                                                                                                                                                                      | Actions: Responsible / Note                                                                                                       |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Committee Member Responsibilities | Brainstorming focused on shifting the role from "execution" to "advisory and steering." Consensus reached that members provide expertise, while the secretary and dedicated working groups handle operations.                              | Lorenzo Bruno to consolidate Miro board notes into a draft "Committee Member Roles & Responsibilities" document for final review. |
| April 2026 Election Timeline      | Valeria proposed a high-level plan: Applications open March 30 (3 weeks), Voting starts April 20 (2 weeks), Results announced May 6.                                                                                                       | Valeria Devaux to lock these dates and begin the "Comms Plan" for a late February launch.                                         |
| Participation & Performance       | Wilco and Jose raised concerns about "ghost members" who apply with AI-generated bios but do not participate after election. Suggestion made for a 6-month membership residency or working group experience as an eligibility requirement. | Gintama to present a data-backed document next week regarding committee participation rates vs. working group activity.           |
| Election Tooling Improvements     | Discussion on reducing "voter fatigue" by simplifying candidate summary sheets and potentially adding video introductions (30-60 seconds) to verify English proficiency and genuine commitment.                                            | Lorenzo Bruno to assess the feasibility of adding video upload capabilities to the member area for the April cycle.               |
| Gaming the System                 | Concerns were raised about "Happy Meal" voting (buying cheap memberships to sway results). Lorenzo noted a 6-month membership rule and verification metrics are in place to flag suspicious behavior.                                      | <p><br></p>                                                                                                                       |


---

# 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/january-29-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.