> For the complete documentation index, see [llms.txt](https://opensourcecommittee.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://opensourcecommittee.docs.intersectmbo.org/about/readme/osc-engagement.md).

# OSC Engagement

### Meeting Minutes:

Minutes from each meeting are transcribed via Google Meet. They are reviewed and edited to align with proper speech and the relative conversation. Once complete it is passed through Gemini and formatted in a three-column table that highlights the Topic, Notes of what was discussed, and any applicable action items.

Meeting Minutes are updated in the Active Notes file attached to the Meeting Invite and posted publicly in GitBook. (Also viewable in GitHub)

### Meeting Agenda:

The agenda is discussed and set by the Committee Chair, Vice Chair, Secretary, and OSO Rep. Once the agenda has been set, a screenshot is added to the meeting invite, and is shared in the Discord and Slack channels. Newly adopted, Each week’s agenda will also be transcribed into the Committee Space ClickUp.

### Meeting Schedule:

Open Source Committee meetings are held every other week on Thursdays:\
6am PST/ 8am CST/ 2pm UTC.

Meeting cadence is subject to change due to OSO events or National Holidays.


---

# 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://opensourcecommittee.docs.intersectmbo.org/about/readme/osc-engagement.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.