> 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/08-20-2026-meeting-minutes.md).
# (08/20/2026) Meeting Minutes
{% hint style="info" %}
OSC held a private meeting due to recent lack of attendance.
{% endhint %}
## 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 | No | Member | Y | October 2025 |
| Pawel Jakubas | No | 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/Transcript:** Exact transcript redacted as the meeting was Private.
## 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 8.20.26
* Open Forum
## Decisions/Actions
**Decisions**
* **Maintain Communication on Discord:** The Committee decided to maintain Discord, ClickUp, and Google Drive as the official communication and task management platforms, rejecting the proposal to create a separate Telegram group to avoid fragmenting information.
* **Adopt Weekly Task Distribution:** The Committee decided to implement a structured, distributed task strategy—assigning short, weekly deliverables (such as report reviews and survey responses) based on member expertise and availability.
* **Pause New Tooling Applications:** The Committee decided to hold processing on two new tooling applications until all previously approved projects are fully submitted, reviewed, and placed under contract.
**Actions**
* **Bora:** Draft a baseline reference list/overview of ecosystem developer tools and projects to improve committee awareness and guide future outreach and funding decisions.
* **Bora (supported by Sebastian):** Take the lead on drafting the technical content for the Tooling Milestone Report (covering Cicerium, Plutonomicon, CTL, Lambda Buffers, Mesh AI, and Cardano Node Emulator) once Terence creates the initial document structure.
* **Terence:** Post the template structure for the Tooling Milestone Report to Discord/Drive so Bora and Sebastian can begin drafting.
* **Terence:** Follow up regarding Q2 tasks, and ping the Developer Advocates by Monday/Tuesday if their task updates are not moved into the review column.
* **Terence:** Close the Maintainer Retainer Program application intake later in the week and prepare a 3-month summary report for the program.
* **Committee Members (All):** Review the Midyear Report, Security Officer report, Developer Advocates report, and Round 2/3 Maintainer Interview reports posted in Discord.
* **Committee Members (All):** Access the KPI Framework Survey draft provided in Discord and contribute answers.
* **Committee Members (All):** Provide feedback via Discord regarding whether the OSC should support or pass on the Regulatory Evidence Portal proposal.
| Topic | Discussion | Notes |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Meeting Structure & Participation | Terence noted that the meeting was held as a closed OSC session. The committee discussed low participation levels, calendar conflicts, and missing quorum (down to 8 members after Dominic stepped down). | Terence emphasized the critical need for documented votes and proof of decision for milestone reporting and future budget approvals. |
| Ecosystem Tooling Awareness & Guardrails | Terence requested that Bora create a baseline overview of developer tooling and ecosystem projects to help the committee make more informed funding decisions and conduct better outreach. | Bora agreed to draft a generic, baseline document tracking tools and projects across the ecosystem. |
| Aiken & Plutus Integration | Terence highlighted that over 50% of onboarded maintainers prefer Aiken or Rust over Plutus, noting that barriers between Aiken and Plutus have significantly reduced over the past two years. | The committee continues to support diverse language maintainers while maintaining a core focus on protecting the Haskell/Plutus codebase. |
| Midyear & Interview Reports Overview | Terence updated the group on several key documentation packages: the Midyear Report, Developer Advocates progress, Security Officer report, and the Round 2/3 Maintainer Interview reports. | Documents are posted in Discord for review. Developer Advocates requested about a week to transition their Q2 tasks to the review column. |
| Committee Communication Channels | Olivier suggested creating a Telegram group for quick announcements. Terence and Bora cautioned against fragmenting communication outside Discord, ClickUp, and Google Drive, as it risks losing context and project archives. | The committee agreed to stick to Discord as the primary communication hub, using ClickUp and Google Drive for task-specific tracking. |
| Task Distribution Strategy | Sebastian proposed setting up a weekly activity task list distributed among members based on expertise, utilizing members' 1–2 available hours per week more effectively. | Tasks and reports will be packaged and assigned out to simplify member contributions. |
| Maintainer Retainer Program | Terence provided an update stating the retainer program is nearly fully closed, with only two applications from the GovTool remaining to be processed. | A summary presentation/report will be compiled after maintainers reach their 3-month mark. |
| Tooling Applications & Mesh AI | Terence reported holding two new tooling applications to finalize existing contracts. The Mesh AI team expressed confusion over filling out an detailed Scope of Work (Phase 3) prior to receiving funds. | Terence clarified that initial approval was conceptual and that specific milestones and scope must be formally detailed before grant execution. |
| Regulatory Evidence Portal & Proposals | Sebastian shared his perspective that funding the Regulatory Evidence Portal may fall outside the OSC's direct scope and requested input from other committee members. | Further discussions on whether to support or abandon the proposal will take place in Discord. |
| Program Framework & Structural Improvements | Terence outlined necessary structural changes for future program iterations: requiring explicit developer experience expectations, defining grant payment terms (ADA via Intersect), and establishing predefined milestone project boards. | Program updates should be executed as holistic program overhauls between cycles rather than minor piecemeal edits. |
| Committee Member Responsibilities | Terence and Bora discussed restructuring committee onboarding so that incoming members own and lead specific programs rather than taking a passive role. | Aligning committee roles with individual ownership will strengthen program management, reporting, and budget justification. |
| KPI Framework Survey | Sebastian pointed out an incoming survey from the Product/Tech Steering Committee regarding the KPI framework draft that requires OSC input. | Committee members are encouraged to review the draft link in Discord and contribute answers. |
| Tooling Milestone Report Draft | Terence requested assistance drafting the upcoming Tooling Milestone report covering Cicerium, Plutonomicon, CTL, Lambda Buffers, Mesh AI, and Cardano Node Emulator. | Terence will set up a structured document template, and Bora will take the lead on drafting the technical content with Sebastian's support. |
| Developer Advocates Follow-Up | Olivier inquired about the timeline for closing the Developer Advocate report given pending submissions from Harun. | Terence confirmed direct outreach was conducted; advocates requested about one week to submit their final task updates. |
---
# 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/08-20-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.