# April 14, 2025 ISC Meeting ## Agenda * Meeting Introduction * Intersect Committee Elections - Progress Update * Intersect Operational Budget Proposal 2025 * Update from Business Function and Committees (If Any) * AOB & Meeting Close ## Attendees | Name | Attendance | Role | Voting Seat (Y/N) | | ---------------------------------------------------- | ---------- | ----------------------------------------- | ----------------- | | [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N | | Jack Briggs | No | Director of Ecosystem | Y | | Lawrence Clark | No | Head of Operations | Y | | Nick Cook | Yes | Head of Membership & Community Hubs | Y | | YUTA | Yes | Community Member Seat | Y | | Phil Lewis | Yes | Community Member Seat | Y | | Thiago Nunes | No | Interim Community Member Seat | Y | | Pedro Lucas | Yes | OSC Chair | Y | | Samuel Leathers | No | Product Chair | Y | | Darlington Welsh | Yes | MCC Chair | Y | | Prof. Steven | Yes | Chair of Board of Directors and CBC Chair | Y | | Kevin Hammond | Yes | TSC Chair | Y | | Seomon | No | GMC Chair | Y | | Jose Miguel De Gamboa | No | CCC Chair | Y | | Christian Taylor | No | Head of OSO | N | | Lorenzo Bruno | No | Head of Product | N | | [Matt Davis](mailto:matt.davis@intersectmbo.org) | Yes | Head of Tech Operation | N | | Duncan Soutar | Yes | Secretary of TSC | N | | Lloyd Duhon | No | Secretary of Budget Committee | N | | Larisa Mcfarlane | No | Secretary of CCC | N | | Terence McCutcheon | Yes | Secretary of OSC | N | **Additional Attendees:** * Valeria Devaux - Observer * Kyle Solomon - Co-Chair of Product Committee * Jonathan Kelly - Observer ## Key Outcomes & Discussions ### **1. Committee Elections Update** Update shared on the ongoing Intersect committee elections. * A strong candidate turnout was noted, with 118 individuals running for committee positions. * Voting will open on Wednesday and run through May 7th, with results to be announced on May 12th. * Members are strongly encouraged to participate in the voting process. ### **2. Budget Proposal Submissions** * Intersect Operational Budget Proposal is in the final review, and will be submitted by end of week. * Several committees, including the TSC, have submitted their budget proposals. * The TSC’s proposal was highlighted as comprehensive, covering maintenance, priority areas, and operational expenses. * Questions arose regarding the expected scope and detail of budget proposals. * **Reminder:** Committees should submit proposals via the designated portal. ### **3. Board Meeting & Petition Response** * The group discussed the upcoming special members meeting in response to a recent petition. * It was clarified that this will be a board meeting, with petitioners invited to participate—a compromise reached after internal discussions. * The board reaffirmed its commitment to transparency, member engagement, and addressing governance concerns raised in the petition. ### **4. Committee Concerns & Feedback** * Concerns were expressed about how recent budget process changes may affect committee autonomy and member engagement. * Members emphasized the need for clear accountability and more robust governance structures. * There was also discussion around improving communication between the board and the wider membership. ### **5. Other Business & Coordination** * Participants highlighted the importance of better coordination between committees and working groups to minimize duplication of efforts. * A request was made for greater oversight from the ISC to ensure alignment and maintain quality across activities. --- # 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://steeringcommittee.docs.intersectmbo.org/committee-meeting-notes/2025-meeting-notes/april-22-2025-isc-meeting/april-14-2025-isc-meeting.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.