> 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/10-15-2026-meeting-minutes.md).

# (10/15/2026) Meeting Minutes

## Attendees:&#x20;

| 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          | Yes        | 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

* Ian Njuguna
* Javier

**Recording:** [Open Source Committee (Intersect) - 2026/10/15 - Recording](https://drive.google.com/file/d/1nZDBkIjfroa-6e46AwjyB6QFpVcgl5XS/view?usp=sharing)

**Transcript:** [Open Source Committee (Intersect) - 2026/10/15 - Transcript](https://docs.google.com/document/d/1XteVf00rtThNiJSAIWa01yqSlKUfPB9W5V5R-whHmNM/edit?usp=sharing)

**Chat Transcript:** [Open Source Committee Meeting – 2026/10/15 – Chat Transcript](https://drive.google.com/file/d/1-B16YjcfMmCJ2E9_xBssNno44yptHshc/view?usp=sharing)

## Intros

**Bora:** TBD\
**Bernard:** OSC - voting member\
**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

## Agenda 10.15.26

* KardanoSDK
* Documents to be delivered
* Remaining 2025 Withdrawals
* OSC Budget MRP/Tooling Reallocation
* Committee Member Participation
* Maintainer Retainer Updates/Committee Eval
* MeshAI
* Open Forum

## Decisions/Actions

**Decisions**

* **Approval of MRP Excess Fund Reallocation:** Approved the reallocation of excess Maintainer Retainer Program funds (approximately 700,000 ADA) to cover deficits in other OSC budget programs, specifically prioritizing the Bug Bounty Program (passed with 4 votes in favor, 2 abstentions).
* **Maintainer Retainer Program Cohort Scope:** Agreed that no additional maintainers will be onboarded to the Maintainer Retainer Program for the remainder of the program cycle.
* **Tooling Sustainability Program Closeout and Treasury Sweep:** Approved the wind-down of the Tooling Sustainability Program by the end of 2026, agreeing not to draw down the remaining \~1.1 to 1.2 million ADA allocation and deciding to sweep any unused funds left in the wallet back to the Treasury reserve smart contract ahead of the December break.
* **Decline Funding for KardanoSDK:** Determined not to move Javier’s Cardano SDK project forward to the next step for tooling funding, advising the creator to establish organic community adoption and coordinate with existing ecosystem tools first.
*

```
<img src="/files/kOMQgKKb4DsmkfoPt4kR" alt="" height="157" width="299">
```

**Actions**

* **Terence:** Post direct links in Discord to the milestone acceptance documents, including the Developer Advocate closeout report, Security Incident Officer midterm/end-term reports, and Maintainer Retainer onboarding reports (rounds 2 and 3).
* **Terence:** Finalize and submit evidence for milestone 2.4 to reconcile the early withdrawal of tooling milestone 6.
* **Terence:** Complete and prepare final closeout documentation for the Developer Advocate Program and Security Incident Management by the following week.
* **Terence:** Clean up ClickUp milestone statuses (e.g., setting active milestones to blue, identifying overdue items) and provide one-on-one walkthroughs for members needing workflow guidance.
* **Committee Members:** Review and add feedback/comments to the Developer Advocate final report, Security Incident reports, and Maintainer Retainer onboarding documents within the coming week.
* **Sebastian:** Consolidate member workflow preferences (focused two-week task boards, email notifications with deadlines, explicit @ mentions in Discord, and direct messaging) and update ClickUp and Discord communication processes accordingly.

| Topic                                                | Discussion                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Notes                                                                                                                                                                                                                |
| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meeting Opening & Attendance                         | Terence called the Open Source Committee meeting to order for October 15, 2026, noting quorum with committee members present.                                                                                                                                                                                                                                                                                                                                                | Meeting kicked off on time; agenda moved directly to the guest speaker.                                                                                                                                              |
| Cardano SDK Presentation                             | Guest speaker Javier presented his tooling project, KardanoSDK built using Kotlin Multiplatform designed to simplify mobile application integration (creating wallets, handling transactions) for Cardano.                                                                                                                                                                                                                                                                   | Javier developed the library independently and noted difficulties in finding accessible mobile tooling.                                                                                                              |
| Cardano SDK Feedback & Adoption Criteria             | Terence, Bora, and Bernard addressed the project's ecosystem fit. Bora pointed out that multiple transaction-building libraries with multi-language bindings already exist. Bernard explained that 2026 funding priorities require demonstrated organic mass adoption rather than early-stage prototypes, citing existing initiatives like Cardano Expo.                                                                                                                     | Javier was advised to research existing ecosystem tools, connect with active mobile developers, and build organic adoption before seeking maintenance funding.                                                       |
| Milestone Documentation & Deliverables Review        | Terence urged members to review pending reports due against milestones, particularly the Developer Advocate final report, security incident reports, and Maintainer Retainer onboarding rounds 2 and 3.                                                                                                                                                                                                                                                                      | Terence will share direct document links in Discord; members asked to leave comments and complete reviews within the upcoming week.                                                                                  |
| Locating Files on Shared Drive                       | Sebastian asked for clarification on navigating committee files. Terence demonstrated the shared drive directory path (Open Source Committee Shared Drive > OSC Treasury 25/26 > Programs).                                                                                                                                                                                                                                                                                  | Specific folder paths were reviewed for Developer Advocate, Project Support, Incident Management, and Maintainer Retainer programs.                                                                                  |
| 2025 Budget Withdrawals Status                       | Terence shared the public treasury dashboard reviewing remaining 2025 allocations across the Developer Advocate travel/bug bounty budget, Maintainer Retainer tooling, and Security Incident Management.                                                                                                                                                                                                                                                                     | Travel allocations are fully drawn; mid-year and end-year incident reports are required to claim remaining milestones. Tooling milestone 6 was withdrawn early by mistake and will be reconciled using 2.4 evidence. |
| Maintainer Retainer Program (MRP) Budget Realignment | Terence explained that 800,000 ADA pulled covers onboarded maintainers for the full year (approx. 200,000 ADA/quarter). Approximately 700,000 ADA in excess funds will not be used for new cohorts due to capacity limits.                                                                                                                                                                                                                                                   | Terence proposed reallocating the excess \~700,000 ADA to underfunded programs (specifically the Bug Bounty Program) rather than leaving funds idle or forfeiting them back to the treasury.                         |
| Committee Discussion on Budget Reallocation          | Bora and Bernard voiced strong support for redirecting funds into security and bug bounties. Sebastian sought clarity on whether existing maintainers would be affected and raised questions regarding inter-committee governance procedures.                                                                                                                                                                                                                                | Terence confirmed existing maintainers remain fully funded (separate pool) and that the Bug Bounty Program was fully expended as of late July due to ADA market conversions.                                         |
| Vote: Reallocation of Excess MRP Funds to Bug Bounty | Terence launched an official committee poll to approve using excess MRP funds to cover spend across other OSC initiatives, specifically the Bug Bounty Program (BBP).                                                                                                                                                                                                                                                                                                        | Poll passed (4 Yes, 2 Abstain). Formal vote confirmed excess funds will be repurposed for security bounties.                                                                                                         |
| Committee Member Participation Challenges            | Sebastian raised concerns regarding declining participation, member departures, and the necessity for each member to dedicate a couple of hours for reviewing documentation and proposals.                                                                                                                                                                                                                                                                                   | Emphasized keeping workloads lightweight and finding practical, low-friction communication methods for member feedback.                                                                                              |
| Communication Channels & Workflow Proposals          | The committee debated how to best streamline task management: Reshma recommended an active task board filtered strictly for immediate two-week deliverables; Bernard requested email alerts with 1-week deadlines (fallback WhatsApp); Bora and 8pro favored Discord with explicit @ user tagging; Olivier noted Telegram direct messages worked well and suggested assigning individual task ownership; Pawel preferred direct email assignments for tech/security reviews. | Terence and Sebastian will synthesize feedback, focus on explicit tagging in Discord, and refine ClickUp so members only see urgent active tasks without clutter.                                                    |
| Tooling Sustainability Program Closeout              | Terence discussed the wind-down plan for the Tooling Sustainability Program ahead of year-end 2026. Roughly 1.1–1.2 million ADA remains unspent and will not be claimed. Existing wallet balances will cover outstanding approved tooling applications.                                                                                                                                                                                                                      | Formal decision reached: Any remaining unused tooling funds will be swept back to the Treasury reserve smart contract prior to the December break.                                                                   |
| Action Items & Meeting Adjournment                   | Terence committed to keeping Discord updated with active deliverables, assisting members 1-on-1 with task tracking, and finalizing closeout documentation for Developer Advocate and Security Incident Management by next week.                                                                                                                                                                                                                                              | Meeting adjourned on schedule.                                                                                                                                                                                       |


---

# 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/10-15-2026-meeting-minutes.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.
