> For the complete documentation index, see [llms.txt](https://productcommittee.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://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/20th-february-2025-5.md).

# 6th May 2025

The session was run in the related [miro board](https://miro.com/app/board/uXjVKro_lxs=/). 

📽️ The meeting recording can be found [here](https://drive.google.com/file/d/1gAe5J_A6wbWcBgdgxb3LrUGe5V__S3Yp/view?usp=sharing).

## Participants

| Name                 | Role        | Attendance |
| -------------------- | ----------- | ---------- |
| Lorenzo Bruno        | Secretary   | Yes        |
| Samuel Leathers      | Chair       | Yes        |
| Kyle Solomon         | Vice-Chair  | Yes        |
| Carlos Lopez De Lara | Voting Seat | No         |
| Alexandre Maaza      | Voting Seat | Yes        |
| James Meidinger      | Voting Seat | Yes        |
| Christian Schmitz    | Voting Seat | No         |
| Tegegne Tefera       | Voting Seat | No         |
| Giorgio Zinetti      | Voting Seat | No         |
| Tomas Garro          | SME         | Yes        |
| Jess Fields          | SME         | Yes        |
| Juan Sierra          | SME         | No         |
| Seun Gbiri           | Observer    | Yes        |
| Simo Simovic         | Observer    | Yes        |
| Thiago Nunes         | Observer    | Yes        |

## Agenda

* Review previous actions and updates
  * newly elected committee members update
* Budget request review
  * review community comments and Hydra feedback
* Product research initiative – review and approve nine research initiatives
* Discuss creation of a Business Development coordination body with X characteristic to function
* Review KPI feedback from the Technical Steering Committee – review proposed changes against current status – agree feedback for TSC

## Updates

* **Review previous actions and updates**
  * **Newly elected committee members update**
    * The Secretary provided an update on the Product Committee election results and outlined onboarding plans for newly elected members.
* **Budget request review**
  * **Review community comments and Hydra feedback**
    * The Committee reviewed community comments received on the Product Committee budget proposal and discussed plans for proposal promotion and community engagement during the feedback period.
* **Product research initiative**
  * **Review and approve nine research initiatives**
    * Tomas Garro presented the draft RFP framework for the nine approved research initiative areas and the Committee discussed scope, evaluation criteria, budgeting considerations and proposal submission requirements.
* **Discuss creation of a Business Development coordination body with X characteristic to function**
  * No discussion for this topic was held. The item remained on the agenda as a reminder for a future session.
* **Review KPI feedback from the Technical Steering Committee**
  * **Review proposed changes against current status**
    * No discussion for this topic was held. The item remained on the agenda for a future session.
  * **Agree feedback for TSC**
    * No discussion for this topic was held.

## Outcomes & Recommendations

The Committee agreed to move review and approval of the research initiative RFPs to an asynchronous process so that all current and newly elected members could provide feedback before publication.


---

# 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://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/20th-february-2025-5.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.