> 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-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/09-03-2026-meeting-minutes.md).
# (09/03/2026) Meeting Minutes
## Attendees:
| Name | Attendance | Role | Voting Seat (Y/N) | Term |
| ------------------------ | ---------- | ---------- | ----------------- | --------------- |
| Sebastian Pabon | Yes | Chair | Y | October 2025 |
| Kambale Mechack Elie | Yes | Vice Chair | Y | April 2026 (2y) |
| Terence ‘Tex’ McCutcheon | Yes | Secretary | N | N/A |
| Bernard Sibanda | No | Member | Y | October 2025 |
| Jordan Hill | No | Member | Y | October 2025 |
| Udai Solanki | No | Member | Y | October 2025 |
| Reshma Mohan | Yes | Member | Y | October 2025 |
| Pawel Jakubas | Yes | Member | Y | April 2026 (2y) |
| Olivier Mwatsimulamo | Yes | Member | Y | April 2026 (2y) |
| Bora Oben | Yes | Member | Y | April 2026 (2y) |
Community/Other Attendees
* N/A
**Recording:** [Open Source Committee (Intersect) - 2026/09/03 - Recording](https://drive.google.com/file/d/19kKSeWirNCCci0PyRFm-wRNypkHZvq8r/view?usp=sharing)
**Transcript:** [Open Source Committee (Intersect) - 2026/09/03 - Transcript](https://docs.google.com/document/d/1-38lXRMpj0k60Y5rWRMWCill5DAniiqz4AWretvEK8Q/edit?usp=sharing)
**Chat Transcript:** [Open Source Committee Meeting – 2026/09/03 – Chat Transcript](https://drive.google.com/file/d/1-H-9UJXi5PqMw8ra-QbWPSoOmYJhfwvD/view?usp=sharing)
## Intros
**Bora:** TBD\
**Bernard:** OSC - voting member\
**Jordan:** TBD\
**Kambale:** OSC Vice chair\
**Olivier:** Goma Hub Member, Milestone Reviewer-Project Catalyst, MCC and OSC\
**Pawel:** Member OSC, CF\
**Reshma:** OSC voting member\
**Sebastian:** OSC chair. Andamio co-founder.\
**Tex:** Open Source Program Manager, Intersect, OSC Secretary, Committee Member Advocate\
**Udai:** Member OSC, AIQUANT Technologies
## Agenda 9.03.26
* Open Forum
## Decisions/Actions
**Decisions**
* **Approval of Accelerator Program for Reimbursment:** Approved using the Accelerator Program budget to reimburse expenses for incident management and travel/events (6 votes Yes, 1 vote Abstain).
* **Approval of Project Support Services Funding:** Approved using Project Support Services to cover the Intersect OSO X premium account, the Crypto EQ Vantage report, and bug bounty reimbursements/outstanding rewards (6 votes Yes, 1 vote Abstain).
* **Approval of Statement of Work (SOW) Direction:** Approved proceeding via the Statement of Work proposition for funding allocations (6 votes Yes, 1 vote Abstain).
*
```
```
* **Scope Refinement for Strategic Pillars:** Decided to narrow the committee’s primary focus in the strategic survey to Infrastructure & Research Excellence and Community & Ecosystem Growth, explicitly removing Adoption & Utility and Treasury & Network Economics to keep the committee's scope clear.
* **KPI Alignment & Survey Responses:** Decided to rate the relevance of top-level ecosystem KPIs low (rating of 2) for the committee's direct scope, while agreeing to propose committee-specific sub-KPIs (such as active maintainer retention and healthy open-source projects) reported on a quarterly basis.
**Actions**
* **Submit Approved Propositions:** Terence to submit the approved poll propositions through the official channels to access funds and process reimbursements.
* **Upload Governance & SOW Documents:** Terence to get CTL, Lambda buffers, and the node emulator documents uploaded to the site and linked back for review once signed.
* **Document Adjustments:** Terence to copy over and format the committee's input on strategic pillars and sub-KPIs directly into the survey document using suggestion mode.
* **Update Assignment Tracking:** Terence to update internal task lists to correctly reflect member contributions (such as Sebastian’s work on the maintainer program and security report).
* **Maintainer Program Closeout:** 8pro to focus on resolving remaining gaps in the maintainer program and developer advocate closeout documentation.
* **Community Engagement:** Committee members without assigned tasks to review open documents in the Discord channel and ping Terence with their availability.
| Topic | Discussion | Notes |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Committee Administration & Polls | Terence reminded committee members (Rashma and Pawel) to complete their votes on three active Discord polls needed to reach quorum. Terence confirmed he will continue facilitating meetings following discussions with Sebastian. | Discord poll votes are required from members who have not yet voted. |
| Open Source Funding & SOW Updates | Bora requested an update regarding the open task for the first five funded projects, specifically noting a missing Statement of Work (SOW) for Mesh AI tooling. Terence confirmed the Mesh AI team has not yet submitted an SOW despite recent contact. | Node emulator contract is moving to the signature phase. Node emulator, CTL, and Lambda buffers documents will be uploaded once finalized. |
| Member Participation & Check-ins | Terence led an open check-in to assess member engagement and identify blockers across open source committee (OSC) initiatives. | Members were encouraged to communicate in Discord or chat if unable to speak during calls. |
| Developer Advocacy & Workstream Tracking | Olivier provided updates on the developer advocate closeout report and suggested implementing dedicated workstreams to improve task tracking and member accountability. | Workstream structure like the MCC framework proposed to improve tracking for upcoming quarters. |
| Report Contributions & Work Alignment | Sebastian and Pawel highlighted their recent work on the maintainer retainer program, the security program final report, and the bug bounty survey. | Project assignments and contributor names will be updated on internal tracking documents. |
| Maintainer Program Closeout Challenges | 8pro reported that collecting final reports for the developer advocate closeout is challenging because several contributors' contracts have expired. | 8pro will focus efforts on completing the maintainer program closeout and addressing remaining documentation gaps. |
| Discord Poll Results & Budget Allocations | Terence reviewed the final results for the three Discord polls, all passing with 6 Yes votes and 1 Abstention. Funding routes were approved for the Accelerator Program and Project Support Services. | Funds will cover incident management, travel/events overspend, bug bounty rewards, Intersect OSO X premium accounts, and Crypto EQ Vantage reports. |
| Strategic Pillars Alignment | The committee reviewed and updated its selection of strategic pillars for an internal survey, focusing on Infrastructure & Research Excellence as well as Community & Ecosystem Growth. | Adoption & Utility was removed from the primary pillar selection to keep committee scope clearly defined. |
| KPI Relevance & On-Chain Activity | The committee discussed top-level ecosystem KPIs (transactions, active wallets, TVL). Terence noted that while OSC workflows (e.g., Maintainer Retainer credentials) generate on-chain transactions, these metrics are secondary to core infrastructure goals. | Committee agreed that top-level transaction KPIs act as a byproduct rather than the primary driver of OSC initiatives. |
| Proposed Sub-KPIs & Survey Finalization | Terence and the committee finalized responses for the KPI survey, proposing custom sub-KPIs including active maintainer retention, healthy open source projects, and contributor retention metrics. | Committee agreed to report sub-KPIs on a quarterly basis and expressed willingness to participate in a follow-up discussion. |
---
# 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-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/09-03-2026-meeting-minutes.md?ask=&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.