Strengthen the OpenSearch project by addressing maintenance and health opportunities that can enable more contributions.
Scope: Health is a broad spectrum that includes security, developer experience, maintainer experience, quality and usability standards, documentation, community wellness and safety.
Date: Thurs, March 21, 2024 Time: 09:00 AM PT (UTC -7)
Agenda setting:
This is a bi-weekly meeting with topics nominated publicly or spilled from the previous meeting.
If you have a topic you would like discussed, please comment below
At the end, if there is time, we can discuss other topics.
======== By 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.
OpenSearchCon Europe - announced - CfP is still open so please get your submissions in
Dashboards custom pkg manager - improvements made to all plugin/javascript - now can use different client versions in packaging and maintain compatibility
Storage team now has public meetings
Misses
RC date miss for 2.13 due to flaky tests/infrastructure
9 attendees. An increase over last meeting, but we still have an exercise to work towards better attendance. Kris/Bill/Barani action item(s)
Advertise on Slack (Bill)
Community Meetings (Kris)
Outlook invites to known attendees that should be here (Barani/Kris)
David Tippett has moved on - we’ll miss him
OpenSearch GitHub org - if someone leaves Amazon, there is an audit script that removes them from org. Barani & Henri Y working to get rid of this / improve this process
Metrics discussion
Not yet accessible publicly, but Barani is working on this
based on inputs from the GH APIs for OpenSearch Project org
Neural Search repo/team report
Seen a spike in issues, but that was tied to upcoming release
New features, how to better communicate with the community
8 ‘Untriaged’ for over a month. Maintainers stated this should have been changed to under-review or more appropriate
Overall, feels that maintainers are doing well with their efforts on PR/Issues/Triage
Side discussion came up about ‘active’ maintainers
popular topic across the project lately
can we get / do we need to get more maintainers to do this triage work on a consistent basis
should we email / follow up with lists of maintainers to see if still want to remain active?
Rich Bowen - this is not a yes/no answer, we’re all human and have things come up in life - should be more of a ‘yes I’m still here and can do more, yes I’m still here but don’t have time currently, no I’ve left for other things, etc’ – this is something for the project to think through
also from Rich - this is still seen as an Amazon project, possibly with a class system, have definitely made huge progress, but keep working on it.
Client repos so really well with their follow up - dB is a great example; gets back to someone that submitted a bug with a request to create a test case that displays how bug surfaces - need to ensure this request is made in a timely manner (dB also does this well)
Issue:
Andriy pointed out that it seems flaky tests have gotten worse
now we have more of them
not trending the right way
Barani writing a PR – open to comments
Lukas - ticket in storage repo working through ways to improve things
remote storage is just really complex. Not sure if this can / should be part of our tests - makes for a very challenging integration test - not sure how to improve this yet
Wheel spin:
Anamoly Detection is up next meeting
Action items
Bill / Barani / Kris
Continue work on more attendees - notify Slack - Meeting invites - announce on Community Meetings