Skip to content

Commit 3869a73

Browse files
krisfreedainkrisfreedain
authored
Merge pull request #3415 from opensearch-project/main
Push out site changes
2 parents 48c5f9c + 57d5b8c commit 3869a73

8 files changed

+561
-4
lines changed

‎_events/2024-1022-dev-triage-ml-commons.markdown

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
calendar_date: '2024-10-22'
3+
eventdate: 2024-10-22 10:30:00 -0700
4+
primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-10-22
5+
title: Development Backlog & Triage Meeting - ml-commons - 2024-10-22
6+
online: true
7+
signup:
8+
url: https://www.meetup.com/opensearch/events/302181982
9+
title: Join on Meetup
10+
11+
---
12+
13+
Join the OpenSearch ml-commons team for their next backlog & triage planning meeting.
14+
15+
(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))
16+
17+
---
18+
19+
**Join Zoom Meeting**
20+
```json
21+
https://us02web.zoom.us/j/82164218920
22+
23+
Meeting ID: 821 6421 8920
24+
Passcode: 259735
25+
26+
---
27+
28+
One tap mobile
29+
+12532050468,,82164218920# US
30+
+12532158782,,82164218920# US (Tacoma)
31+
32+
---
33+
Dial by your location
34+
• +1 253 205 0468 US
35+
• +1 253 215 8782 US (Tacoma)
36+
• +1 346 248 7799 US (Houston)
37+
• +1 669 444 9171 US
38+
• +1 669 900 9128 US (San Jose)
39+
• +1 719 359 4580 US
40+
• +1 646 558 8656 US (New York)
41+
• +1 646 931 3860 US
42+
• +1 689 278 1000 US
43+
• +1 301 715 8592 US (Washington DC)
44+
• +1 305 224 1968 US
45+
• +1 309 205 3325 US
46+
• +1 312 626 6799 US (Chicago)
47+
• +1 360 209 5623 US
48+
• +1 386 347 5053 US
49+
• +1 507 473 4847 US
50+
• +1 564 217 2000 US
51+
• 877 853 5247 US Toll-free
52+
• 888 788 0099 US Toll-free
53+
54+
Meeting ID: 821 6421 8920
55+
56+
Find your local number: https://us02web.zoom.us/u/kcboT3QOI
57+
58+
```
59+
60+
---
61+
62+
**Agenda:**
63+
64+
**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.)*
65+
66+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
67+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
68+
69+
**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)*
70+
71+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
72+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
73+
74+
**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)*
75+
76+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
77+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
78+
79+
80+
***Please see Meetup link for URL and required passcode.***
81+
82+
83+
*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.*

‎_events/2024-1101-2-18-release-meetings.markdown

+57
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
calendar_date: '2024-11-01'
3+
eventdate: 2024-11-01 09:00:00 -0700
4+
title: OpenSearch 2.18.0 Release Meetings
5+
online: true
6+
signup:
7+
url: https://chime.aws/7638980658
8+
title: Join on Chime
9+
category: development
10+
---
11+
12+
**NOTE: This is a series, ending with the release of 2.18.0 - Please read carefully**
13+
14+
Join the OpenSearch team for the open release meetings, so we can push 2.18.0 live as a community.
15+
16+
(hosts: [Rishabh Singh](https://github.com/getsaurabh02), [Peter Zhu](https://github.com/peterzhuamazon), & [Nate Boot](https://github.com/nateynateynate))
17+
18+
[Release OpenSearch and OpenSearch Dashboards 2.18.0 - Tracking through Issue 5004](https://github.com/opensearch-project/opensearch-build/issues/5004)
19+
20+
On-going release discussions in the [#releases](https://opensearch.slack.com/archives/C0561HRK961) channel on the OpenSearch Project [Slack](https://opensearch.org/slack.html) instance
21+
22+
[Release Schedule and Maintenance Policy](https://opensearch.org/releases.html)
23+
24+
**November 1st 2024 - 9AM PDT**
25+
26+
* 1st Go / No-Go voting call
27+
28+
**November 4th 2024 - 9AM PDT**
29+
30+
* 2nd Go / No-Go voting call
31+
32+
**November 5th 2024 - 2PM PDT**
33+
34+
* [Release / Post release](https://github.com/opensearch-project/opensearch-build/wiki/Releasing-the-Distribution#release) (Release day!) [Release manager, leadership team, Repository owners ]
35+
36+
* Last possible date 11/05/2024 per the [Releases schedule](https://opensearch.org/releases.html).
37+
38+
**Dial in information - valid for each meeting:**
39+
40+
**Join Meeting**
41+
42+
**Click to join the meeting: <https://chime.aws/7638980658>**
43+
44+
**Meeting ID: 7638980658**
45+
46+
A headset is recommended or you may use your computer’s microphone and speakers.
47+
48+
Call in using your phone:
49+
- United States Toll-Free (1): +1 855-552-4463
50+
- United States (1): +1 206-462-5569
51+
- International: https://chime.aws/dialinnumbers/
52+
- One-click Mobile Dial-in (United States (1)): +1 206-462-5569,,,7638980658#
53+
54+
Dial-in attendees must enter *7 to mute or unmute themselves.
55+
56+
[Download Chime](https://aws.amazon.com/chime/download)
57+
[Information about creating an account](https://aws.amazon.com/chime/getting-started)

‎_events/2024-1105-dev-triage-ml-commons.markdown

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
calendar_date: '2024-11-05'
3+
eventdate: 2024-11-05 10:30:00 -0800
4+
primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-11-05
5+
title: Development Backlog & Triage Meeting - ml-commons - 2024-11-05
6+
online: true
7+
signup:
8+
url: https://www.meetup.com/opensearch/events/304071216
9+
title: Join on Meetup
10+
11+
---
12+
13+
Join the OpenSearch ml-commons team for their next backlog & triage planning meeting.
14+
15+
(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))
16+
17+
---
18+
19+
**Join Zoom Meeting**
20+
```json
21+
https://us02web.zoom.us/j/82164218920
22+
23+
Meeting ID: 821 6421 8920
24+
Passcode: 259735
25+
26+
---
27+
28+
One tap mobile
29+
+12532050468,,82164218920# US
30+
+12532158782,,82164218920# US (Tacoma)
31+
32+
---
33+
Dial by your location
34+
• +1 253 205 0468 US
35+
• +1 253 215 8782 US (Tacoma)
36+
• +1 346 248 7799 US (Houston)
37+
• +1 669 444 9171 US
38+
• +1 669 900 9128 US (San Jose)
39+
• +1 719 359 4580 US
40+
• +1 646 558 8656 US (New York)
41+
• +1 646 931 3860 US
42+
• +1 689 278 1000 US
43+
• +1 301 715 8592 US (Washington DC)
44+
• +1 305 224 1968 US
45+
• +1 309 205 3325 US
46+
• +1 312 626 6799 US (Chicago)
47+
• +1 360 209 5623 US
48+
• +1 386 347 5053 US
49+
• +1 507 473 4847 US
50+
• +1 564 217 2000 US
51+
• 877 853 5247 US Toll-free
52+
• 888 788 0099 US Toll-free
53+
54+
Meeting ID: 821 6421 8920
55+
56+
Find your local number: https://us02web.zoom.us/u/kcboT3QOI
57+
58+
```
59+
60+
---
61+
62+
**Agenda:**
63+
64+
**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.)*
65+
66+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
67+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
68+
69+
**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)*
70+
71+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
72+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
73+
74+
**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)*
75+
76+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
77+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
78+
79+
80+
***Please see Meetup link for URL and required passcode.***
81+
82+
83+
*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.*

‎_events/2024-1119-dev-triage-ml-commons.markdown

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
calendar_date: '2024-11-19'
3+
eventdate: 2024-11-19 10:30:00 -0800
4+
primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-11-19
5+
title: Development Backlog & Triage Meeting - ml-commons - 2024-11-19
6+
online: true
7+
signup:
8+
url: https://www.meetup.com/opensearch/events/304071235
9+
title: Join on Meetup
10+
11+
---
12+
13+
Join the OpenSearch ml-commons team for their next backlog & triage planning meeting.
14+
15+
(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))
16+
17+
---
18+
19+
**Join Zoom Meeting**
20+
```json
21+
https://us02web.zoom.us/j/82164218920
22+
23+
Meeting ID: 821 6421 8920
24+
Passcode: 259735
25+
26+
---
27+
28+
One tap mobile
29+
+12532050468,,82164218920# US
30+
+12532158782,,82164218920# US (Tacoma)
31+
32+
---
33+
Dial by your location
34+
• +1 253 205 0468 US
35+
• +1 253 215 8782 US (Tacoma)
36+
• +1 346 248 7799 US (Houston)
37+
• +1 669 444 9171 US
38+
• +1 669 900 9128 US (San Jose)
39+
• +1 719 359 4580 US
40+
• +1 646 558 8656 US (New York)
41+
• +1 646 931 3860 US
42+
• +1 689 278 1000 US
43+
• +1 301 715 8592 US (Washington DC)
44+
• +1 305 224 1968 US
45+
• +1 309 205 3325 US
46+
• +1 312 626 6799 US (Chicago)
47+
• +1 360 209 5623 US
48+
• +1 386 347 5053 US
49+
• +1 507 473 4847 US
50+
• +1 564 217 2000 US
51+
• 877 853 5247 US Toll-free
52+
• 888 788 0099 US Toll-free
53+
54+
Meeting ID: 821 6421 8920
55+
56+
Find your local number: https://us02web.zoom.us/u/kcboT3QOI
57+
58+
```
59+
60+
---
61+
62+
**Agenda:**
63+
64+
**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.)*
65+
66+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
67+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
68+
69+
**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)*
70+
71+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
72+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
73+
74+
**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)*
75+
76+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
77+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
78+
79+
80+
***Please see Meetup link for URL and required passcode.***
81+
82+
83+
*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.*

‎_events/2024-1203-dev-triage-ml-commons.markdown

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
calendar_date: '2024-12-03'
3+
eventdate: 2024-12-03 10:30:00 -0800
4+
primary_title: Development Backlog & Triage Meeting - ml-commons - 2024-12-03
5+
title: Development Backlog & Triage Meeting - ml-commons - 2024-12-03
6+
online: true
7+
signup:
8+
url: https://www.meetup.com/opensearch/events/304071250
9+
title: Join on Meetup
10+
11+
---
12+
13+
Join the OpenSearch ml-commons team for their next backlog & triage planning meeting.
14+
15+
(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))
16+
17+
---
18+
19+
**Join Zoom Meeting**
20+
```json
21+
https://us02web.zoom.us/j/82164218920
22+
23+
Meeting ID: 821 6421 8920
24+
Passcode: 259735
25+
26+
---
27+
28+
One tap mobile
29+
+12532050468,,82164218920# US
30+
+12532158782,,82164218920# US (Tacoma)
31+
32+
---
33+
Dial by your location
34+
• +1 253 205 0468 US
35+
• +1 253 215 8782 US (Tacoma)
36+
• +1 346 248 7799 US (Houston)
37+
• +1 669 444 9171 US
38+
• +1 669 900 9128 US (San Jose)
39+
• +1 719 359 4580 US
40+
• +1 646 558 8656 US (New York)
41+
• +1 646 931 3860 US
42+
• +1 689 278 1000 US
43+
• +1 301 715 8592 US (Washington DC)
44+
• +1 305 224 1968 US
45+
• +1 309 205 3325 US
46+
• +1 312 626 6799 US (Chicago)
47+
• +1 360 209 5623 US
48+
• +1 386 347 5053 US
49+
• +1 507 473 4847 US
50+
• +1 564 217 2000 US
51+
• 877 853 5247 US Toll-free
52+
• 888 788 0099 US Toll-free
53+
54+
Meeting ID: 821 6421 8920
55+
56+
Find your local number: https://us02web.zoom.us/u/kcboT3QOI
57+
58+
```
59+
60+
---
61+
62+
**Agenda:**
63+
64+
**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.)*
65+
66+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
67+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
68+
69+
**Sprint backlog** *(Examine if it still reflects the work that we are committing to doing and is it in the right priority order)*
70+
71+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
72+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
73+
74+
**Backlog** *(anything we should move to sprint backlog? anything we should tag asking for help from the community?)*
75+
76+
* [Backend ml-commons](https://github.com/opensearch-project/ml-commons/issues)
77+
* [Dashboards ml-commons](https://github.com/opensearch-project/ml-commons-dashboards/issues)
78+
79+
80+
***Please see Meetup link for URL and required passcode.***
81+
82+
83+
*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.*

0 commit comments

Comments
 (0)