# (02/26/2026) Meeting Minutes ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | Term | | ------------------------ | ---------- | ---------- | ----------------- | ------------ | | Georg Link | Yes | Chair | Y | April 2026 | | Udai Solanki | Yes | 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 | | Reshma Mohan | Yes | Member | Y | October 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | Community/Other Attendees * Dan Baruka * Christian Taylor * Emmanuel Titi * Gauthier Paluku * Harun Mwangi * Musa Ridwan Itopa * Uche Obasi * Wilco van de Burgwal **Recording:** [Open Source Committee (Intersect) - 2026/02/26 - Recording](https://drive.google.com/file/d/1CXvQRcfZRg2rKlVso6IHR5Q5lbIJV2Q8/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/02/26 - Transcript](https://docs.google.com/document/d/1xcLeqbJE8u34dvdENZHAzqH0y7tNdyWVlP4pyAvnA1c/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/02/26 – Chat Transcript](https://drive.google.com/file/d/1v3VY1isub6XQabnjqQHacxFPLRRHsqWe/view?usp=sharing) ## Intros Tex: Open Source Program Manager, Intersect Staff, Open Source Committee Secretary Bernard: TBD Georg: Bitergia Jordan: TBD Reshma: OSC voting member, Founder of Reafino Sebastian: OSC, Gimbalabs, contributor, Andamio co-founder.\ Udai: OSC voting member, Founder and CEO - AIQUANT ## Agenda 02.26.26 * Developer Experience Innovation WG * POSM Tasks * MRP Application/Interview Scoring * Tooling Proposal reviews * Comms channel Discussion * Budget Questions/Sessions * MRP Andamio Recording available * Project Support Services - Milestones * Community Project Review - OSC Sponsorship * Open Forum ## Decisions/Actions **Decisions** * **Discord Commitment:** The committee agreed to continue using Discord as the primary communication tool for offline polling, with members committing to check it at least once every two days. * No Automated/Manual Summaries: The committee decided not to implement a manual or AI-generated weekly email summary to avoid adding an extra layer of workload for Terence. * Recusal on MLABS: It was decided that Jordan will recuse himself from reviewing MLABS proposals due to a conflict of interest; the remaining five voices will provide feedback. * Scope of Support Services: There was a consensus to open the "Project Support Services" to the broader Cardano ecosystem rather than limiting it strictly to Intersect-hosted projects. * Budget Session Timing: The committee agreed to meet as a group tomorrow at 15:30 UTC to finalize the budget. **Actions** * **Review Candidates:** Committee members are to open the interview and application docs to provide feedback/scoring on candidates before the next meeting. * **Tooling Review:** Members are tasked with reviewing the seven projects in the "Tooling Intake Form" list (specifically the MLABS proposals) to call for a decision in two weeks. * **Discord Polling:** Terence will continue to use Discord for offline polls, and members must respond within the given timelines to keep projects moving. * **Budget Prep:** Members who have not yet met with Terence individually for a "protected environment" budget discussion are encouraged to schedule time or bring their thoughts to tomorrow's session. * **Helios Outreach:** Bernard will reach out to the Helios project (and potentially the Plutus Playground crowd) to see if they require support through the paid open source model. * **Market Analysis:** Members (specifically Bernard and Jordan) will investigate the needs of external projects and failed Catalyst projects to see how the committee's support services can best be applied. * **Meeting Invite:** Terence to send out the calendar invitation for the budget session scheduled for tomorrow. | Topic | Discussion | Notes | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Interview Reviews | Reviewing candidate interviews for the committee. The goal is two reviews per candidate. Terence noted most have 2-3 already. | Members encouraged to spend 7-10 minutes "scrubbing" through interviews to gain familiarity with candidates. | | Application Scoring | Increasing participation in reviewing and scoring written applications to improve average scores for candidate selection. | Defined as a "lightweight effort" compared to full interview reviews. | | Tooling Proposal Progress | Reviewing funded tooling projects. Five projects were targeted for funding; the first (Peer Review Doc Management) was approved in January. | Focus is on "spending in the right places" rather than just meeting a quota. | | Tooling Intake Form | Navigation within ClickUp to find the "Tooling Intake Form" list under the Open Source Committee sidebar. | There are currently seven projects sitting in the "To-Do" column for review. | | MLABS Proposals | Specific proposals from MLABS (Plutonomicon, YTXP, Covenant Library, etc.) are up for review. | Discussion focused on whether these tools are critical and helpful to the ecosystem. | | Conflict of Interest | Jordan disclosed a conflict of interest regarding the MLABS applications. | Jordan will recuse from reviewing those specific applications; the other 5 members will handle them. | | Communication Channels | Discussion on the effectiveness of Discord. Some members (Georg, Udai) prefer email or WhatsApp and don't check Discord daily. | Terence requested members check Discord at least once every two days for offline polling. | | Communication Summary | Suggestion for Terence to send a Friday midday summary email of Discord polls and ClickUp tasks. | The committee decided against this to avoid adding "policing" work to Terence's plate. | | Budget Planning Sessions | Terence has met with some members individually but needs a collective session to refine numbers and timelines. | Consensus remains that the "Paid Open Source Model" is core and crucial. | | Budget Meeting Schedule | Coordinating a time for the full committee budget session given upcoming travel for Terence and Udai. | Meeting set for tomorrow at 15:30 UTC. | | Andamio Platform | Review of a recording regarding the Andamio platform for onboarding maintainers via tokens rather than reimbursement. | Contract is signed; members are encouraged to watch the demo recording. | | Project Support Services | Discussion on how to use the "Project Support Services" budget category (helping projects with open source practices/expertise). | Need to define eligibility criteria and target audience (Intersect vs. broader Cardano ecosystem). | | Ecosystem Outreach | Jordan and Bernard suggested reaching out to failed Catalyst projects and specific tools like Helios for support. | Bernard will contact the Helios project to gauge interest in the support services model. | | Committee Member Rewards | Udai provided an update from the steering committee regarding a new tool to track member contributions for rewards. | 50% of rewards are based on attendance; the other 50% require specific documentation of work done. | | India Hackathon | MCC is proposing a hybrid (physical/online) hackathon based in India. | Early-stage initiative; Open Source Committee members may be asked to participate later. | --- # Agent Instructions: 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/02-26-2026-meeting-minutes.md?ask= ``` 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.