> 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/working-group/core-infrastructure-roadmap-working-group/working-group-milestones-and-meeting-schedule/28-5-24-meeting-minutes-1-6.md).

# (15/7/24) Meeting Minutes

July 15, 2024

## Attendees:

* Duncan Soutar
* Giorgio Zinetti
* Nori Nishigaya
* Silona Bonewald
* Lloyd Duhon
* Leonard Hegarty
* Douglas Ferguson
* Hwang HuongKet

## Agenda

### Action items

<table><thead><tr><th width="224">Discussion Points</th><th width="264">Notes/Action Items</th><th>Actions: Responsible/None</th></tr></thead><tbody><tr><td>Introduction &#x26; Quorum</td><td>Quorum was not present. </td><td><br></td></tr><tr><td>Approval on Agenda, Minutes, Online Votes, &#x26; Publishing Updates</td><td>Approval of minutes and discord publication was decided to be taken to Discord for asynchronous voting due to absence of quorum </td><td><br>Hwang to post poll on Discord for async voting</td></tr><tr><td>New Budget Model presented by Budget Committee Rep</td><td>Budget Committee rep shared a draft to the new budget process, and agreed to share the presentation after the Budget Committee approves the draft for the CIR-wg to review. The Budget Committee rep agreed to join a future workshop for a more detailed presentation.</td><td>Budget Committee rep to be re-invited for a Q&#x26;A session with the CIR-WG </td></tr><tr><td>Adjournment</td><td>Workshop adjourned due to absence of quorum.</td><td><br></td></tr></tbody></table>

<br>


---

# 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://productcommittee.docs.intersectmbo.org/working-group/core-infrastructure-roadmap-working-group/working-group-milestones-and-meeting-schedule/28-5-24-meeting-minutes-1-6.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.