# Operations & Project Health Meeting - 2024-04-18 **URL:** \ **Category:** Community\ **Tags:** proj-health-agenda\ **Created:** [April 18, 2024, 4:53pm UTC](https://forum.opensearch.org/t/operations-project-health-meeting-2024-04-18/18928 "2024-04-18T16:53:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![peternied](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/peternied/32/3515_2.png) [@peternied](https://forum.opensearch.org/u/peternied)\ **Post date:** [April 18, 2024, 4:53pm UTC](https://forum.opensearch.org/t/operations-project-health-meeting-2024-04-18/18928/1 "2024-04-18T16:53:07Z")
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, April 18, 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. [Zoom Meeting link](https://us02web.zoom.us/j/88927478240) Meeting ID: **889 2747 8240** Passcode: **760208** [Meetup link](https://www.meetup.com/opensearch/events/mjfcltygcgbgb/) ======== _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._ ---
**Author:** ![peternied](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/peternied/32/3515_2.png) [@peternied](https://forum.opensearch.org/u/peternied)\ **Post date:** [April 18, 2024, 4:57pm UTC](https://forum.opensearch.org/t/operations-project-health-meeting-2024-04-18/18928/2 "2024-04-18T16:57:06Z")
# Meeting Minutes: ## Wins/Misses ### Wins: - Client Releases (Java & Ruby) - High OpenSearch Core Maintainer participation - [[MAINTAINERS] [Action Required] Your help reviewing changes and issues in opensearch-project/OpenSearch · Issue #12970 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/12970) - Improved Jenkins worker spec to improve test stability ### Misses: - API Breaking changes v1 check needs a v2 version ## Repo of the Week: Documentation ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/e/e688e2a461d8de00e3df19ed15f510d41adcdfee.jpeg) - Issues: Originally issues were being assigned to writer, issue were sitting around for a while. Made a process change to switch the assigner to the person that files the issue either developer or community members - not docs maintainers. - Seeing 45 pull requests, seems reasonable. Workflow is typically a week or two. - Gaps around documentation, for example [Update links to documentation in rest-api-spec by cwperks · Pull Request #13043 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/pull/13043) - Contribution volume has gone up over time ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/afbeb0e2e51ac7ebd4a7c1de3457d5359fbe16b1.png) - Added first external maintainer, meet in a conference and asked then to contribute more. - Q: Is there anything going well that you don’t see metrics on? - Like more metrics on pull requests - Maybe tool [GitHub - peternied/contribution-rate](https://github.com/peternied/contribution-rate) can be used to capture some of these? @peternied will follow up with @heatherhalter - Only a couple of maintainers are performing PR reviews, going to create a new channel in the OpenSearch slack. - Review process: Starts with tech review, documentation review by writer, then editorial review. - Seeing bottlenecks around documentation review step, looking to open this up more broadly. - Tech vs Doc review staging can create complexity, need to tag folks in. - Opening up training for writing standards, maybe have a certification process - is that what a maintainer? - In the past 6 months asking for contributions has helped increased the contribution rate. - Documentation team process improvements by @peterzhu, makes deploying documentation to all versions much easier (19 backport targets and growing) . GitHub App in development to help improve backporting automation. - @craigperkins Back and forth with docs team - speedy and useful - @dblock OpenSearch API specification recent changes request for review [GitHub - opensearch-project/opensearch-api-specification: API specification for OpenSearch](https://github.com/opensearch-project/opensearch-api-specification) - There are many sub issues per plugin for documentation [[FEATURE] Add specs for `security` namespace · Issue #233 · opensearch-project/opensearch-api-specification · GitHub](https://github.com/opensearch-project/opensearch-api-specification/issues/233) - @Hasini Plugin templates were update to include more specific, more examples ## RFC Discussion - @reta looking for feedback on [[RFC] Reconsider the breaking changes check policy · Issue #13275 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/13275) ## Open Discussion - @danwiddis Looking for feedback on fixing [[BUG] The RestController always consumes content when handling real HTTP requests · Issue #13011 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/13011) ## Wheel Spin - SQL