> 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-8-2026.md).

# January 8 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                                   | No         | Intersect                             |
| Lorenzo Bruno                                        | No         | Head of Product Curation at Intersect |

Recording: [Intersect Governance WG Weekly - 2026/01/08 15:00 CET - Recording](https://drive.google.com/file/d/1VTK_u-h8i-uAJLA1I4vEVmORkt1FhZDI/view)

Transcript: [Intersect Governance WG Weekly - 2026/01/08 15:00 CET - Transcript](https://docs.google.com/document/d/1k2Do9A7PPIk3zolb40K3GqAx7MWBpEnaiedJWFn27dA/edit?tab=t.0)

### Agenda

* Committee Chair/Vice Chair Election Process
* Extending Committee term

### Decisions/Actions

| Discussion Point                          | Notes                                                                                                                                                                                                                                               | Actions: Responsible / Note                                                                                                                                       |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ISC Chair Requirement                     | Review of Jose's (ISC) feedback on whether the ISC needs a formal chair. The group noted the ISC's unique composition (existing committee chairs + executive team) and discussed if this exclusion should be formalized in policy or the ISC remit. | Simo Simovic to check with other ISC members for consensus on whether to formally exclude the ISC from the Chair Election Policy or update the ISC remit.         |
| "Abandoned" Positions                     | Debate on defining the mechanism for declaring a chair/vice chair position "abandoned" (e.g., missing two meetings without notice). The group discussed if this requires a formal motion of no confidence or a new bullet point in the policy.      | Simo Simovic to draft language regarding "abandoned positions" while balancing the need for formality with existing dismissal policies.                           |
| Chair/Vice Chair Roles & Responsibilities | Gintama and Thiago emphasized the need for a unified, non-fragmented document outlining the specific leadership duties and expectations for chairs to improve committee maturity and accountability.                                                | Simo Simovic to locate and consolidate fragmented onboarding packs into a single, standardized "Chair Roles and Responsibilities" policy.                         |
| Two-Year Term Extension                   | The group discussed two paths: starting 2-year terms in April 2026 or delaying until October 2026. Thiago argued for moving quickly to solve participation issues; Gintama warned against rushing without proper vetting/eligibility rules.         | Working Group to continue the debate next week on the technical execution path (direct extension vs. new elections) and eligibility criteria for 2-year mandates. |


---

# 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-8-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.