BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//OpenSearch - ECPv6.15.20//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-ORIGINAL-URL:https://opensearch.org
X-WR-CALDESC:Events for OpenSearch
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
DTSTART:20230101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=UTC:20240208T120000
DTEND;TZID=UTC:20240208T130000
DTSTAMP:20260526T040720
CREATED:20250105T125553Z
LAST-MODIFIED:20250105T131622Z
UID:10000071-1707393600-1707397200@opensearch.org
SUMMARY:Fluent Community Meeting
DESCRIPTION:The Fluent Community meeting is an online meetup centered around the Fluentd and Fluent Bit open source projects that are part of the Cloud Native Computing Foundation (CNCF). \nUsers who are interested in discussing the projects\, communicating with maintainers\, or are eager to learn about the technologies should join. We also discuss general observability topics for those who are looking to learn more about the subject. \nOur agenda for the meeting is an open document. If you want to add topics to the agenda please request edit permissions. \n 
URL:https://opensearch.org/event/2024-0208-fluent-community-meetup/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240213T103000
DTEND;TZID=UTC:20240213T113000
DTSTAMP:20260526T040720
CREATED:20250105T125428Z
LAST-MODIFIED:20250105T164107Z
UID:10000070-1707820200-1707823800@opensearch.org
SUMMARY:Development Backlog & Triage Meeting - ml-commons - 2024-02-13
DESCRIPTION:Join the OpenSearch ml-commons team for their next backlog & triage planning meeting. \n(hosts: Yaliang Wu\, Dhrubo Saha)\, Jing Zhang\, & Xun Zhang) \n\nJoin Zoom Meeting \n\n\nhttps://us02web.zoom.us/j/82164218920\n\nMeeting ID: 821 6421 8920\nPasscode: 259735\n\n---\n\nOne tap mobile\n+12532050468\,\,82164218920# US\n+12532158782\,\,82164218920# US (Tacoma)\n\n---\nDial by your location\n• +1 253 205 0468 US\n• +1 253 215 8782 US (Tacoma)\n• +1 346 248 7799 US (Houston)\n• +1 669 444 9171 US\n• +1 669 900 9128 US (San Jose)\n• +1 719 359 4580 US\n• +1 646 558 8656 US (New York)\n• +1 646 931 3860 US\n• +1 689 278 1000 US\n• +1 301 715 8592 US (Washington DC)\n• +1 305 224 1968 US\n• +1 309 205 3325 US\n• +1 312 626 6799 US (Chicago)\n• +1 360 209 5623 US\n• +1 386 347 5053 US\n• +1 507 473 4847 US\n• +1 564 217 2000 US\n• 877 853 5247 US Toll-free\n• 888 788 0099 US Toll-free\n\nMeeting ID: 821 6421 8920\n\nFind your local number: https://us02web.zoom.us/u/kcboT3QOI\n\n\n\n\n\nAgenda: \nTriage issues (add the triaged label once reviewed/ready. They can be also labelled as sprint backlog if we are looking to queueing them up next\, or good first issue / help wanted when appropriate.) \n\nBackend ml-commons\nDashboards ml-commons\n\nSprint backlog (Examine if it still reflects the work that we are committing to doing and is it in the right priority order) \n\nBackend ml-commons\nDashboards ml-commons\n\nBacklog (anything we should move to sprint backlog? anything we should tag asking for help from the community?) \n\nBackend ml-commons\nDashboards ml-commons\n\nPlease see Meetup link for URL and required passcode. \nBy joining the Development Backlog & Triage Meeting\, you grant OpenSearch\, and our affiliates the right to record\, film\, photograph\, and capture your voice and image during the Development Backlog & Triage Meeting (the “Recordings”). You grant to us an irrevocable\, nonexclusive\, perpetual\, worldwide\, royalty-free right and license to use\, reproduce\, modify\, distribute\, and translate\, for any purpose\, all or any part of the Recordings and Your Materials. For example\, we may distribute Recordings or snippets of Recordings via our social media outlets. \nJoin on Meetup
URL:https://opensearch.org/event/2024-0213-dev-triage-ml-commons/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240214T100000
DTEND;TZID=UTC:20240214T110000
DTSTAMP:20260526T040720
CREATED:20250105T125223Z
LAST-MODIFIED:20250105T125223Z
UID:10000068-1707904800-1707908400@opensearch.org
SUMMARY:OpenSearch Core Triage
DESCRIPTION:Join the OpenSearch community to review and triage incoming issues in the OpenSearch repository. Meetings are open-to-all and attendance is encouraged for anyone who hopes to contribute\, discuss an issue\, or learn more about the project. See Triaging on OpenSearch for more details and FAQs. \nAgenda\n\nInitial Gathering: Feel free to turn on your video and engage in informal conversation. Shortly\, a volunteer triage facilitator will begin the meeting and share their screen.\nRecord Attendees: The facilitator will request attendees to share their GitHub profile links. These links will be collected and assembled into a tag to annotate comments during the meeting.\nAnnouncements: Any announcements will be made at the beginning of the meeting.\nReview of New Issues: We start by reviewing all untriaged issues for the OpenSearch repo.\nAttendee Requests: An opportunity for any meeting member to request consideration of an issue or pull request.\nOpen Discussion: Attendees can bring up any topics not already covered by filed issues or pull requests.\n\nMeeting Links\nJoin via browser screen share: https://chime.aws/1988437365 Join via phone (US): +1-929-432-4463\,\,\,1988437365# Join via phone (US toll-free): +1-855-552-4463\,\,\,1988437365# \nJoin on Meetup
URL:https://opensearch.org/event/2024-0214-opensearch-core-triage/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240222T120000
DTEND;TZID=UTC:20240222T130000
DTSTAMP:20260526T040720
CREATED:20250105T124842Z
LAST-MODIFIED:20250105T131632Z
UID:10000066-1708603200-1708606800@opensearch.org
SUMMARY:Fluent Community Meeting
DESCRIPTION:The Fluent Community meeting is an online meetup centered around the Fluentd and Fluent Bit open source projects that are part of the Cloud Native Computing Foundation (CNCF). \nUsers who are interested in discussing the projects\, communicating with maintainers\, or are eager to learn about the technologies should join. We also discuss general observability topics for those who are looking to learn more about the subject. \nOur agenda for the meeting is an open document. If you want to add topics to the agenda please request edit permissions. \n\n\n\ncommunity\nThursday 22 February 2024 12:00pm
URL:https://opensearch.org/event/2024-0222-fluent-community-meetup/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240227T080000
DTEND;TZID=UTC:20240227T090000
DTSTAMP:20260526T040720
CREATED:20250105T124444Z
LAST-MODIFIED:20250105T124444Z
UID:10000064-1709020800-1709024400@opensearch.org
SUMMARY:OpenSearch Community Meeting - 2024-02-27
DESCRIPTION:Join us for our online community meeting. \nMeeting topics and passcode are listed in the collaborative agenda on the forum. \nFeel free to comment on the agenda before the meeting if you want to add an item or have a question. Would you like to present? Reach out on the forumn thread – we welcome community presentations. \nAfter the meeting\, we will post the chat log and any meeting notes. We welcome you to keep the conversation going on the forum. \nBy joining the OpenSearch Community Meeting\, you grant OpenSearch\, and our affiliates the right to record\, film\, photograph\, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable\, nonexclusive\, perpetual\, worldwide\, royalty-free right and license to use\, reproduce\, modify\, distribute\, and translate\, for any purpose\, all or any part of the Recordings and Your Materials. For example\, we may distribute Recordings or snippets of Recordings via our social media outlets. \nJoin on Meetup
URL:https://opensearch.org/event/2024-0227-community-meeting/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240227T103000
DTEND;TZID=UTC:20240227T113000
DTSTAMP:20260526T040720
CREATED:20250104T213808Z
LAST-MODIFIED:20250105T124605Z
UID:10000065-1709029800-1709033400@opensearch.org
SUMMARY:Development Backlog & Triage Meeting - ml-commons - 2024-02-27
DESCRIPTION:Join the OpenSearch ml-commons team for their next backlog & triage planning meeting. \n(hosts: Yaliang Wu\, Dhrubo Saha)\, Jing Zhang\, & Xun Zhang) \n\nJoin Zoom Meeting \n\n\nhttps://us02web.zoom.us/j/82164218920\n\nMeeting ID: 821 6421 8920\nPasscode: 259735\n\n---\n\nOne tap mobile\n+12532050468\,\,82164218920# US\n+12532158782\,\,82164218920# US (Tacoma)\n\n---\nDial by your location\n• +1 253 205 0468 US\n• +1 253 215 8782 US (Tacoma)\n• +1 346 248 7799 US (Houston)\n• +1 669 444 9171 US\n• +1 669 900 9128 US (San Jose)\n• +1 719 359 4580 US\n• +1 646 558 8656 US (New York)\n• +1 646 931 3860 US\n• +1 689 278 1000 US\n• +1 301 715 8592 US (Washington DC)\n• +1 305 224 1968 US\n• +1 309 205 3325 US\n• +1 312 626 6799 US (Chicago)\n• +1 360 209 5623 US\n• +1 386 347 5053 US\n• +1 507 473 4847 US\n• +1 564 217 2000 US\n• 877 853 5247 US Toll-free\n• 888 788 0099 US Toll-free\n\nMeeting ID: 821 6421 8920\n\nFind your local number: https://us02web.zoom.us/u/kcboT3QOI\n\n\n\n\n\nAgenda: \nTriage issues (add the triaged label once reviewed/ready. They can be also labelled as sprint backlog if we are looking to queueing them up next\, or good first issue / help wanted when appropriate.) \n\nBackend ml-commons\nDashboards ml-commons\n\nSprint backlog (Examine if it still reflects the work that we are committing to doing and is it in the right priority order) \n\nBackend ml-commons\nDashboards ml-commons\n\nBacklog (anything we should move to sprint backlog? anything we should tag asking for help from the community?) \n\nBackend ml-commons\nDashboards ml-commons\n\nPlease see Meetup link for URL and required passcode. \nBy joining the Development Backlog & Triage Meeting\, you grant OpenSearch\, and our affiliates the right to record\, film\, photograph\, and capture your voice and image during the Development Backlog & Triage Meeting (the “Recordings”). You grant to us an irrevocable\, nonexclusive\, perpetual\, worldwide\, royalty-free right and license to use\, reproduce\, modify\, distribute\, and translate\, for any purpose\, all or any part of the Recordings and Your Materials. For example\, we may distribute Recordings or snippets of Recordings via our social media outlets. \nJoin on Meetup
URL:https://opensearch.org/event/2024-0227-dev-triage-ml-commons/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=UTC:20240228T100000
DTEND;TZID=UTC:20240228T110000
DTSTAMP:20260526T040720
CREATED:20250104T213610Z
LAST-MODIFIED:20250104T213610Z
UID:10000057-1709114400-1709118000@opensearch.org
SUMMARY:OpenSearch Core Triage
DESCRIPTION:Join the OpenSearch community to review and triage incoming issues in the OpenSearch repository. Meetings are open-to-all and attendance is encouraged for anyone who hopes to contribute\, discuss an issue\, or learn more about the project. See Triaging on OpenSearch for more details and FAQs. \nAgenda\n\nInitial Gathering: Feel free to turn on your video and engage in informal conversation. Shortly\, a volunteer triage facilitator will begin the meeting and share their screen.\nRecord Attendees: The facilitator will request attendees to share their GitHub profile links. These links will be collected and assembled into a tag to annotate comments during the meeting.\nAnnouncements: Any announcements will be made at the beginning of the meeting.\nReview of New Issues: We start by reviewing all untriaged issues for the OpenSearch repo.\nAttendee Requests: An opportunity for any meeting member to request consideration of an issue or pull request.\nOpen Discussion: Attendees can bring up any topics not already covered by filed issues or pull requests.\n\nMeeting Links\nJoin via browser screen share: https://chime.aws/1988437365 Join via phone (US): +1-929-432-4463\,\,\,1988437365# Join via phone (US toll-free): +1-855-552-4463\,\,\,1988437365# \nJoin on Meetup
URL:https://opensearch.org/event/2024-0228-opensearch-core-triage/
CATEGORIES:Community
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
END:VCALENDAR