# Working Group Milestones and meeting schedule {% hint style="info" %} This page is written on behalf of the Core Infrastructure Roadmap working group, the information contained is subject to change and amendment by the working group at any time. {% endhint %} The Core Infrastructure Roadmap working group's mission is to foster a transparent, inclusive, and adaptable core infrastructure roadmap for the decentralized development of Cardano as an open-source blockchain and maintain its competitiveness. To fulfill this mission, the working group has set several goals that needs to be looked into, namely Vocabulary & Definitions, Communication Plan, The Process, and Vision. As this is an iterative process, the schedule below will be subject to change according to the evolving needs of the working group. *** ## Key Milestones The working group has outlined several key milestones to be achieved up to October. These milestones serve as initial benchmarks to guide the group's progress towards their goals. As the group advances, these milestones will be further refined and become more concrete.

90 day milestone plan

These milestones provide a structured framework for the group to follow, ensuring that efforts are coordinated and focused on achieving the set goals. Regular reviews and adjustments will ensure that the group remains on track and can adapt to any emerging challenges or opportunities. ## Outline Meeting Schedule To assure success and velocity of the working group, a simple ethos has been devised. Every session starts and ends with a defined outcome that contributes to the overall process. For example, one outcome of the first session would be to take one item to the working group, e.g. log-structured merge-tree (LSM tree), and challenge if the item is defined enough to be considered, compared and sorted.
IDDateAgendaLocation
122 April 2024Minutes/Write up can be found hereVirtual
229 Apr 2024Minutes/Write up can be found hereVirtual
37 May 2024Minutes/Write up can be found hereVirtual
413 May 2024Minutes/Write up can be found hereVirtual
520 May 2024Minutes/Write up can be found hereVirtual
628 May 2024Minutes/Write up can be found hereVirtual
73 June 2024Minutes/Write up can be found hereVirtual
810 June 2024Minutes/Write up can be found hereVirtual
917 June 2024Minutes/Write up can be found hereVirtual
1025 June 2024Minutes/Write up can be found hereVirtual
111 July 2024Minutes/Write up can be found hereVirtual
128 July 2024Minutes/Write up can be found hereVirtual
1315 July 2024Minutes/Write up can be found hereVirtual
1422 July 2024Minutes/Write up can be found hereVirtual
1529 July 2024Minutes/Write up can be found hereVirtual
165 Aug 2024Minutes/Write up can be found hereVirtual
1712 Aug 2024Minutes/Write up can be found hereVirtual
1819 Aug 2024Minutes/Write up can be found hereVirtual
1927 Aug 2024Minutes/Write up can be found hereVirtual
202 Sept 2024Minutes/Write up can be found hereVirtual
219 Sept 2024Minutes/Write up can be found hereVirtual
2216 Sept 2024Minutes/Write up can be found hereVirtual
2323 Sept 2024Minutes/Write up can be found hereVirtual
2430 Sept 2024Minutes/Write up can be found hereVirtual
257 Oct 2024Minutes/Write up can be found hereVirtual
2614 Oct 2024Minutes/Write up can be found hereVirtual
2721 Oct 2024Minutes/Write up can be found hereVirtual
2828 Oct 2024Minutes/Write up to be approvedVirtual
294 Nov 2024Meeting scheduled for 1400 - 1600 UTCVirtual
3011 Nov 2024Meeting scheduled for 1400 - 1500 UTCVirtual
*The schedule, date and agenda of each session is subject to change based on the progress and priority set within the working group.* --- # Agent Instructions: 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://committees.docs.intersectmbo.org/intersect-product-committee/working-group/core-infrastructure-roadmap-working-group/working-group-milestones-and-meeting-schedule.md?ask= ``` 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.