> 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/about/committee-members.md).

# Committee Members

## Committee Composition

* 4 Community Seats
* 7 Intersect Committee Chairs (the chairs of the Intersect Committees)
* 3 Intersect Team Members
* 1 Secretary

## Committee Members

<table><thead><tr><th>Position</th><th width="187">Name</th><th>Voting Member</th><th>Member Seat Rotation</th></tr></thead><tbody><tr><td>Secretary</td><td>Simo Simovic</td><td>No</td><td>N/A</td></tr><tr><td>Community Member Seat</td><td>Kristian Kowalsky<br></td><td>Yes</td><td>April '27</td></tr><tr><td>Community Member Seat</td><td>Jose Miguel de Gamboa</td><td>Yes</td><td>April '27</td></tr><tr><td>Community Member Seat</td><td>James Meidinger</td><td>Yes</td><td>April '28</td></tr><tr><td>Community Member Seat</td><td>Thiago Nunes</td><td>Yes</td><td>April '28</td></tr><tr><td>Civics Committee Chair</td><td>Nicolas Cerny</td><td>Yes</td><td>N/A</td></tr><tr><td>Open Source Committee Chair</td><td>Sebastian Pabon</td><td>Yes</td><td>N/A</td></tr><tr><td>Technical Steering Committee Chair</td><td>Kevin Hammond</td><td>Yes</td><td>N/A</td></tr><tr><td>Budget Committee Chair</td><td>Megan Hess</td><td>Yes</td><td>N/A</td></tr><tr><td>Membership and Community Committee Chair</td><td>Martin Musagara</td><td>Yes</td><td>N/A</td></tr><tr><td>Product Committee Chair</td><td>Samuel Leather</td><td>Yes</td><td>N/A</td></tr><tr><td>Growth and Marketing Committee Chair</td><td>Laura Mattiucci</td><td>Yes</td><td>N/A</td></tr><tr><td>Executive Director</td><td>Jack Briggs</td><td>Yes</td><td>N/A</td></tr><tr><td>Head of Product and Membership</td><td>Lorenzo Bruno</td><td>No</td><td>N/A</td></tr><tr><td>Head of Ecosystem</td><td>Larisa Mcfarlane</td><td>Yes</td><td>N/A</td></tr><tr><td>Secretary of GMC</td><td>Lara Bonasorte</td><td>No</td><td>N/A</td></tr><tr><td>Secretary of Open Source Committee</td><td>Terrence McCutcheon</td><td>No</td><td>N/A</td></tr><tr><td>Secretary of Civics Committee</td><td>Thomas Lindseth<br></td><td>No</td><td>N/A</td></tr><tr><td>Secretary of Budget Committee</td><td>Lloyd Duhon</td><td>No</td><td>N/A</td></tr><tr><td>Secretary of TSC</td><td>Bosko Majdanac</td><td>No</td><td>N/A</td></tr><tr><td>Secretary of MCC</td><td>Abhik Nag</td><td>No</td><td>N/A</td></tr></tbody></table>


---

# 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/about/committee-members.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.