> 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/05-28-2026-meeting-minutes.md).

# (05/28/2026) Meeting Minutes

## Attendees:&#x20;

| Name                     | Attendance | Role       | Voting Seat (Y/N) | Term            |
| ------------------------ | ---------- | ---------- | ----------------- | --------------- |
| Vacant                   | No         | Chair      | Y                 | April 2026      |
| Vacant                   | No         | Vice Chair | Y                 | October 2026    |
| Terence ‘Tex’ McCutcheon | Yes        | Secretary  | N                 | N/A             |
| Bernard Sibanda          | Yes        | Member     | Y                 | October 2026    |
| Jordan Hill              | Yes        | Member     | Y                 | October 2026    |
| Sebastian Pabon          | Yes        | Member     | Y                 | October 2026    |
| Udai Solanki             | No         | Member     | Y                 | October 2026    |
| Reshma Mohan             | Yes        | Member     | Y                 | October 2026    |
| Pawel Jakubas            | Yes        | Member     | Y                 | April 2026 (2y) |
| Olivier Mwatsimulamo     | Yes        | Member     | Y                 | April 2026 (2y) |
| Bora Oben                | Yes        | Member     | Y                 | April 2026 (2y) |
| Dominik Hinkleman        | Yes        | Member     | Y                 | April 2026 (2y) |
| Kambale Mechack Elie     | Yes        | Member     | Y                 | April 2026 (2y) |

Community/Other Attendees

* Dan Baruka
* Emmanuel Titi
* Harun Mwangi
* Luke Mahoney
* Seun Gibri
* Uche Obasi

**Recording:** [Open Source Committee (Intersect) - 2026/05/28 - Recording](https://drive.google.com/file/d/1OZPv4N0VvrIUcnGBqqHIObcoSTZXDDbS/view?usp=sharing)

**Transcript:** [Open Source Committee (Intersect) - 2026/05/28 - Transcript](https://docs.google.com/document/d/1CFkFK_sUtIxau7c2kfHQZPuNkz-a63lKwbM0UJ2yVds/edit?usp=sharing)

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

## Intros

**Bora:** TBD\
**Bernard:** OSC - voting member\
**Dominik:** OSC comittee member. Part of the company Inferara\
**Jordan:** TBD\
**Kambale:** TBD\
**Olivier:** TBD\
**Pawel:** OSC member, Cardano Foundation\
**Reshma:** OSC voting member\
**Sebastian:** OSC, Gimbalabs, contributor, Andamio co-founder.\
**Tex:** Open Source Program Manager, Intersect Staff, Open Source Committee Secretary\
**Udai:** TBD

## Agenda 5.28.26

* Developer Advocate Check In
* Continued OSC Onboarding
* Open Forum

## Decisions/Actions

**Decisions**

* **Polling Platform:** The committee decided to use Discord rather than Google Meet for official polling and decision tracking because it offers better long-term traceability.

**Actions**

* **All Committee Members:** Input scores and rationales into the Main Retainer Program (MRP) Round 2 scoring sheet to prepare for upcoming interviews.
* **All Committee Members:** Review the 2026 Budget Proposal Comments document in Discord and log responses as suggestions by the end of the week.
* **All Committee Members:** Navigate to the Intersect voting portal to submit applications for the Chair/Vice Chair roles, or prepare to vote once the window opens in one week.
* **All Committee Members:** Maintain Discord open in the background to ensure responses to critical notifications are made within a 48-hour window.
* **Reshma:** Update the MRP Round 2 scoring sheet with direct repository links for each applicant to streamline the review process.
* **Luke (MLabs):** Smooth out and submit the comprehensive scope package, technical rationale, and community adopter list for the Lambda Buffers Band 2 upgrade request by tomorrow.
* **Terence:** Launch a Discord poll regarding whether to return the Accelerator program funds to the treasury while maintaining support for project services.
* **Terence:** Post the Discord vote/poll regarding MLabs' request to elevate Lambda Buffers from Band 3 to Band 2 once the scoping data is received.
* **Terence:** Propose dates on Discord for an upcoming X Space to market and defend the open source committee budget proposal.

| Topic                                      | Discussion                                                                                                                                                                                                            | Notes                                                                                                                                                                                                                                 |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Welcome and Attendance                  | Terence opened the meeting, checking for stuck participants and noting missing members (Bernard, Olivier, and Jordan). Bora sent word he would be late. Bernard joined shortly after.                                 | Attendees were reminded to drop their names, affiliations, and conflict of interest disclosures in the chat at the start of every meeting.                                                                                            |
| 2. Drive Overview & Transparency           | Terence shared his screen to walk through the Open Source Committee (OSC) Google Drive structure, emphasizing a "transparency first" policy for shared information.                                                   | Committee members have "contributor" edit access. Terence advised using comments/suggestions in Word docs and direct input in designated columns for Sheets.                                                                          |
| 3. Drive Folder Structure & Working Groups | Terence explained the segregation between the OSC folder and the Developer Advocate workspace. He highlighted past and active working groups, including Tooling, DevX, and the DevX Innovation Working Group.         | The DevX Innovation Working Group meets monthly on the last Wednesday. Two off-cycle feedback sessions are planned for late June to gather direct developer feedback.                                                                 |
| 4. Archive and Active Notes Sizing         | Terence detailed how meeting records, transcripts, and notes files are managed within the drive, explaining the rationale behind document sizing.                                                                     | Source files from Google Meet go to YouTube and the drive. The "active notes" document is kept at the top level and capped at 200–300 pages (covering 12–18 months) before archiving.                                                 |
| 5. OSC Strategy & Budget History           | The repository for the OSC Strategy and older foundational documents was reviewed. Terence also pointed out the 2025 budget folder containing last year's proposals.                                                  | Strategy documents are relatively old but will serve as the baseline when new revisions are required. No budget reviews have been executed under the 2025 structure this year.                                                        |
| 6. 2026 Budget Proposal Comments           | Terence highlighted the active "OSC budget proposal 2026 comments" document in Discord. Dominik clarified a labeling discrepancy on the page (marked 2026 to 2027).                                                   | Members are urged to leave input as suggestions. Terence will provide responses by the end of the week based on available committee feedback.                                                                                         |
| 7. Signed Contracts & Milestones           | The committee reviewed the "signed contracts" folder, which acts as a ledger for agreements with Intersect and partners (e.g., Cerium).                                                                               | This folder serves as a check-and-balance resource. Members are encouraged to audit it and flag any missing milestone acceptance forms or change requests.                                                                            |
| 8. Program Status & Fund Returns           | Terence reviewed the status of the 6 active treasury programs. Travel/events is closing post-summit. Code Forest and Summer of Code funds are slated to return to the treasury.                                       | A conflict exists regarding the Accelerator program withdrawal deadline (September). Terence proposed returning Accelerator funds while keeping project support active.                                                               |
| 9. Polling Preferences                     | Terence asked the committee whether they preferred voting via Google Meet polls or via Discord for tracking ongoing decisions.                                                                                        | Dominik and Reshma expressed a preference for Discord due to better traceability. Terence agreed to post the Accelerator program poll on Discord.                                                                                     |
| 10. MRP Round 2 Applications               | Reshma requested all OSC members input their scores and rationales into the Main Retainer Program (MRP) Round 2 scoring sheet to prepare for interviews next week.                                                    | Sebastian agreed. Dominik requested that direct links to the applicant repositories be added to the sheet to prevent evaluating the wrong codebases; Reshma agreed to update.                                                         |
| 11. ClickUp Workflow Checklist             | Terence provided a brief refresher on ClickUp, demonstrating how it serves as a duplicate checklist for agenda subtasks and milestone tracking (e.g., Mainter Retainer Program M3).                                   | Members can add subtasks or use the comment section to tag Terence (@text or @Terence) for direct email notifications.                                                                                                                |
| 12. Developer Advocate Updates             | Emmanuel reported on a recent virtual workshop linked to the Open Source Summit and upcoming local sessions in Nairobi. Uche shared details on a successful physical meetup for the DA satellite event at the Summit. | Emmanuel noted that local unrest in Nairobi forced a last-minute pivot from a physical event to an online session for safety, which Terence fully supported.                                                                          |
| 13. MLabs Proposal: Plutonomicon CTL       | Terence announced that MLabs' Plutonomicon CTL tool was approved for Band 1 funding ($15,000–$35,000) at a final proposal rate of $30,000 across two milestones.                                                      | The milestone breakdown details will be posted to Discord for final committee review and comment before formalization.                                                                                                                |
| 14. MLabs Proposal: Lambda Buffers         | Luke (MLabs) discussed Lambda Buffers, explaining they had to reject the original Band 3 ($2,000–$5,000) approval because the scope/code generation complexities require a higher baseline.                           | Luke requested a shift to Band 2 ($5,000–$15,000) to implement a language-agnostic "covenant" approach. He will submit a smoothed-out scope document by tomorrow. Bora asked about KPIs; Luke will share their adopter tracking list. |
| 15. Committee Chair Elections              | Terence announced that the application phase for the OSC Chair and Vice Chair elections opened via the Intersect voting portal. Applications close in one week, followed immediately by voting.                       | Only OSC members can apply or vote. The highest vote-getter becomes Chair; the second highest becomes Vice Chair. Previous consensus favored Sebastian for Chair and Kali (8pro) for Vice Chair.                                      |
| 16. Roles, Marketing, and Communication    | Terence reviewed the Chair/Vice Chair roles and responsibilities document, noting the Chair's added financial sign-off duties. He proposed hosting an X Space in the next two weeks to market the budget proposal.    | Members were asked to suggest X Space dates in Discord and to keep Discord active in the background for time-sensitive notifications.                                                                                                 |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/05-28-2026-meeting-minutes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
