> 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/13-5-24-meeting-minutes.md).

# (13/5/24) Meeting Minutes

May 13, 2024

## Attendees:

* Ben Hart
* Erik Skogsberg
* Eystein Hansen
* Hwang Huongket
* Leonard Hegarty
* Romain Pellerin
* Sam Leathers
* Silona Bonewald

## Notes/Decision

1. A 50% quorum on meeting and online votes was proposed and seconded.
2. Core working group roles have been elected and agreed by the core members, including:
   * Co-chairs: Ben Hart (Mlab) and Leonard Hegarty (IOI)
   * Secretary: Hwang (Intersect)
   * SIG Liaison: Eystein Hansen (NBX)
   * TWG Liaison: Romain Pellerin (IOI)
3. Initial milestones covered in Miro. These milestones have yet to be ratified, but is a starting point for the group to work with. This will be continuously refined as the working group progresses through the LSM exercise with the skeleton framework. 

<figure><img src="https://lh7-us.googleusercontent.com/BkO-hNQ3HdXhAuzrq37zWGlJ6NO55Zgre9PHQs60KpAhbZPjKITtejTQpYVYj9nUtC3wzsZhpVyp05pjH4bS2pmNCgNgxTJ5Eofe23xZMRjFg_i9fKTCng1NdPxe2gMNwuAnCWIri_-eP6uM7mNMoNg" alt=""><figcaption><p>Milestone screengrab (WIP)</p></figcaption></figure>

## Action items

* [ ] Alignment meeting to be called for co-chairs, secretary and facilitator to set agenda for 20th May extended workshop
* [ ] Eystein to reach out to potential candidates and propose to working group as additional members


---

# 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/13-5-24-meeting-minutes.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.