> 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/osc-meeting-minutes/open-source-committee-meeting-minutes/2024-meeting-minutes/08-02-2024-meeting-minutes.md). # (08/02/2024) Meeting Minutes ## Attendees: * Christian Taylor (OSO Rep) [Christian Taylor](mailto:christian.taylor@intersectmbo.org) * Sandip Pandey * Ronald Span * Nicholas Clarke * Terence McCutcheon [Terence McCutcheon](mailto:terence.mccutcheon@intersectmbo.org) * Abhik Nag [Abhik Nag](mailto:abhik.nag@intersectmbo.org) * Silona Bonewald * Samuel Leathers * Seomon Register * Jaiyeola Demilade * MIxAxIM Recording: Transcript: ## Intros Christian: Head of Open Source Office, Intersect Staff Tex: Open Source Program Manager, Intersect Staff, Open Source Committee Secretary Nick: Director of Engineering at Tweag/Modus Create Sandip: Dquadrant Adam: Not Present Ronald: CEO Dquadrant, Intersect Member Daniel: Not Present Phillip: Not Present ## Agenda * Policy WG * Oracles WG * Developer Advocates * Update from OSO Team * Open Forum * Reminder of New Meeting Cadence \
| Discussion Point | Notes | Actions: Responsible / Note | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Introduction | Terence McCutcheon welcomed everyone and handed over to Christian Taylor. Christian requested members to state their affiliations in the Slack channel. | Members to state their affiliations in the Slack channel. | | Policy Piece | Christian discussed the policy draft aligning with Intersect, filling the committee seats, and the interim status duration. | Members to review the draft and discuss. Christian to share the document link for review. | | GitHub Repos and Project Roadmaps | Silona Bonewald mentioned interest from various groups in GitHub repos and kanbans. Christian supported the idea of project roadmaps on GitHub. | None specified. | | Changes in Document | Christian outlined major changes in terms, implementation method, election cycle, and candidate criteria. | Members to review the changes and provide feedback. | | Voting Mechanism | Discussion on the interim voting mechanism and possible use of a Google survey. | Develop and finalize the voting mechanism. Christian to gather and implement feedback. | | Oracles Working Group | Silona provided an update on the Oracles working group, emphasizing attendance and standardization practices. | Drive attendance and participation in the working group. | | Developer Advocate Program | Christian introduced new Developer Advocates and their roles in building a contribution ladder. | Plan a meet and greet with Developer Advocates in the next meeting. | | Project Framework and Support | Christian discussed the Project Framework, criteria for project assessment, and Project Support Services. | Draft acceptance criteria and gather feedback. Continue working on Project Support Services. | | Community Management | Christian introduced Abz as the new community manager. | None specified. | | Security Working Group | Update on the Security working group’s first meeting and their Charter. | Publish the Charter and framework on the knowledge base. | | Open Source Summit | Announcement of participation in the Open Source Summit in Vienna. | Coordinate a meetup in Vienna. Christian to follow up with interested 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://opensourcecommittee.docs.intersectmbo.org/osc-meeting-minutes/open-source-committee-meeting-minutes/2024-meeting-minutes/08-02-2024-meeting-minutes.md?ask=&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.