forked from opensearch-project/project-website
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request opensearch-project#2915 from dhrubo-os/main
triage meeting for 2024-06-04 10:30:00 -0700
- Loading branch information
Showing
1 changed file
with
83 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
--- | ||
calendar_date: '2024-06-04' | ||
eventdate: 2024-06-04 10:30:00 -0700 | ||
primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-06-04 | ||
title: Development Backlog & Triage Meeting - ml-commons - 2024-06-04 | ||
online: true | ||
signup: | ||
url: https://www.meetup.com/opensearch/events/301002144 | ||
title: Join on Meetup | ||
|
||
--- | ||
|
||
Join the OpenSearch ml-commons team for their next backlog & triage planning meeting. | ||
|
||
(hosts: [Yaliang Wu](https://github.com/ylwu-amzn), [Dhrubo Saha](https://github.com/dhrubo-os), [Jing Zhang](https://github.com/jngz-es), & [Xun Zhang](https://github.com/Zhangxunmt)) | ||
|
||
--- | ||
|
||
**Join Zoom Meeting** | ||
```json | ||
https://us02web.zoom.us/j/82164218920 | ||
|
||
Meeting ID: 821 6421 8920 | ||
Passcode: 259735 | ||
|
||
--- | ||
|
||
One tap mobile | ||
+12532050468,,82164218920# US | ||
+12532158782,,82164218920# US (Tacoma) | ||
|
||
--- | ||
Dial by your location | ||
• +1 253 205 0468 US | ||
• +1 253 215 8782 US (Tacoma) | ||
• +1 346 248 7799 US (Houston) | ||
• +1 669 444 9171 US | ||
• +1 669 900 9128 US (San Jose) | ||
• +1 719 359 4580 US | ||
• +1 646 558 8656 US (New York) | ||
• +1 646 931 3860 US | ||
• +1 689 278 1000 US | ||
• +1 301 715 8592 US (Washington DC) | ||
• +1 305 224 1968 US | ||
• +1 309 205 3325 US | ||
• +1 312 626 6799 US (Chicago) | ||
• +1 360 209 5623 US | ||
• +1 386 347 5053 US | ||
• +1 507 473 4847 US | ||
• +1 564 217 2000 US | ||
• 877 853 5247 US Toll-free | ||
• 888 788 0099 US Toll-free | ||
|
||
Meeting ID: 821 6421 8920 | ||
|
||
Find your local number: https://us02web.zoom.us/u/kcboT3QOI | ||
|
||
``` | ||
|
||
--- | ||
|
||
**Agenda:** | ||
|
||
**Triage 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.)* | ||
|
||
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues) | ||
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues) | ||
|
||
**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)* | ||
|
||
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues) | ||
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues) | ||
|
||
**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)* | ||
|
||
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues) | ||
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues) | ||
|
||
|
||
***Please see Meetup link for URL and required passcode.*** | ||
|
||
|
||
*By 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.* |