From 25a109822eed848720c476c76f256aa6c75f67b1 Mon Sep 17 00:00:00 2001 From: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Date: Wed, 27 Nov 2024 15:43:49 -0500 Subject: [PATCH 1/2] Apply suggestions from code review Co-authored-by: Nathan Bower Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> --- _posts/2024-11-27-driving-community-contributions.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/_posts/2024-11-27-driving-community-contributions.md b/_posts/2024-11-27-driving-community-contributions.md index d877f05ec..776714eea 100644 --- a/_posts/2024-11-27-driving-community-contributions.md +++ b/_posts/2024-11-27-driving-community-contributions.md @@ -21,16 +21,15 @@ For those unfamiliar with OpenSearch, it is a community-driven, open-source plat OpenSearch originated as a fork of Elasticsearch in early 2021 after Elastic changed its licensing to a more restrictive source-available model. Users still desired an open-source alternative, prompting AWS to release a fork. This phase of our journey was both exciting and challenging. The fork involved substantial effort: 650 pull requests, around 56,000 files, and over 4.5 million lines of code to modify. By July, we delivered a feature-complete, stable version 1.0. At that time, OpenSearch was one of the few fully open-source search and analytics engines available. Our primary focus was to launch a stable, interoperable 1.x line that met our community's needs. -With a stable product in place, 2022 was dedicated to listening and learning—--a lot of learning. As we invited and encouraged a community of users and contributors, both the OpenSearch team and our sponsors at AWS spent the year understanding how to enable a community independently. This might seem surprising, but AWS had not previously led an open-source project of OpenSearch's scope and trajectory. We had to learn the best ways to build trust with internal AWS teams and, more importantly, with external contributors and organizations. To support this, we engaged through various communication channels—forums, blog posts, and numerous requests for comments. +With a stable product in place, 2022 was dedicated to listening and learning---a lot of learning. As we invited and encouraged a community of users and contributors, both the OpenSearch team and our sponsors at AWS spent the year understanding how to enable a community independently. This might seem surprising, but AWS had not previously led an open-source project of OpenSearch's scope and trajectory. We had to learn the best ways to build trust with internal AWS teams and, more importantly, with external contributors and organizations. To support this, we engaged through various communication channels---forums, blog posts, and numerous requests for comments. In 2023, I joined AWS to lead engineering for open-source OpenSearch. I quickly realized that while OpenSearch had achieved significant success, we were still working to rebuild the trust lost when Elastic changed its license. I also saw the immense potential of our dedicated community to drive innovation and accelerate growth. -Early in 2023, the rise of generative AI placed OpenSearch at the forefront, thanks to our early innovations in k-NN algorithms as a vector database. It became crucial to invest in and enhance core search performance and vector database use cases, including hybrid search. This led to a cultural transformation within AWS, OpenSearch, and our relationship with our community, focusing on deeper innovations in the search domain. Initially, there were challenges, but the AWS team and the broader community embraced the change. Together, we pushed for more open governance and trust building. We established a leadership committee comprising diverse stakeholders to promote open and transparent governance. -And we saw results! +Early in 2023, the rise of generative AI placed OpenSearch at the forefront, thanks to our early innovations in k-NN algorithms as a vector database. It became crucial to invest in and enhance core search performance and vector database use cases, including hybrid search. This led to a cultural transformation within AWS, OpenSearch, and our relationship with our community, focusing on deeper innovations in the search domain. Initially, there were challenges, but the AWS team and the broader community embraced the change. Together, we pushed for more open governance and trust building. We established a leadership committee comprising diverse stakeholders to promote open and transparent governance. And we saw results! By the end of 2023, OpenSearch had made significant strides in: -* **Search and generative AI innovation**: We made notable advancements in search performance, hybrid search, and vector database. +* **Search and generative AI innovation**: We made notable advancements in search performance, hybrid search, and vector database functionality. * **Community growth**: Contributions from outside of AWS surged, and we added maintainers from over 25 organizations. Our user forum traffic grew to 500,000 views monthly, and [opensearch.org](http://opensearch.org/) reached over 1 million monthly visitors. * **Broad participation**: A slew of new contributors joined the effort, while long-time contributors deepened their commitments. Companies like Aryn, SAP, and Bytedance made significant contributions, while Intel drove substantial performance improvements with new codecs based on Zstandard compression. From 75f05565744a8aeab07b5e6c5dc3644806117c8b Mon Sep 17 00:00:00 2001 From: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Date: Wed, 27 Nov 2024 15:47:48 -0500 Subject: [PATCH 2/2] Apply suggestions from code review Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> --- _posts/2024-11-27-driving-community-contributions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2024-11-27-driving-community-contributions.md b/_posts/2024-11-27-driving-community-contributions.md index 776714eea..a85d16a77 100644 --- a/_posts/2024-11-27-driving-community-contributions.md +++ b/_posts/2024-11-27-driving-community-contributions.md @@ -7,8 +7,8 @@ authors: date: 2024-11-27 categories: - community -meta_keywords: -meta_description: +meta_keywords: OpenSearch Project, AWS open source, Linux Foundation, community contributions, OpenSearch Software Foundation +meta_description: Explore the OpenSearch journey from an AWS-led project to a vendor-neutral, community-driven open-source platform under the Linux Foundation. Learn about the project's growth, challenges, and future in search, analytics, and vector databases. --- When Amazon Web Services (AWS) launched the OpenSearch Project, it sought to inspire a community of contributors to help drive innovation for a strategically important open-source project. Working toward that goal called for new domain knowledge and a fresh look at company culture to help build trust across internal teams and, more importantly, with external contributors and organizations.