Add author bios pics

Signed-off-by: Fanit Kolchina <[email protected]>

Author: kolchfa-aws

_community_members/bburkholder.md

@@ -41,7 +41,7 @@ permalink: '/community/members/bryan-burkholder.html'
 # At this time, only conference_speaker, and author are defined.
 personas:
   - conference_speaker
-#  - author
+  - author
 
 # Array of conference IDs that the member is a speaker.
 conference_id:
@@ -62,3 +62,5 @@ conference_id:
 #  url: https://mastodon.social/@mastodonusername
 #  name: mastodonusername
 ---
+
+**Bryan Burkholder** is a Staff Software Engineer at Slack, focused on improving observability adoption across the engineering organization. Recently, this work has centered around developing Astra, an open-source log search and analytics engine that can handle petabyte scale in a cost-effective manner.

_community_members/jhandler.md

@@ -25,5 +25,4 @@ conference_id:
 redirect_from: '/authors/jhandler/'
 ---
 
-Jon is a principal solutions architect at AWS based in Palo Alto, CA. Jon works on the OpenSearch Project, providing help and guidance to a broad range of customers who have search workloads that they want to move to the AWS Cloud. Prior to joining AWS, Jon’s career as a software developer included four years of coding a large-scale eCommerce search engine. Jon holds a Bachelor of Arts from the University of Pennsylvania and a Master of Science and PhD in computer science and artificial intelligence from Northwestern University.
-
+**Jon Handler** is Director of Solutions Architecture at AWS, working with the OpenSearch Project and providing help and guidance to a broad range of OpenSearch users. Prior to joining AWS, he worked on a large-scale e-commerce search engine. Jon holds a Master of Science and PhD in computer science and artificial intelligence from Northwestern University.

_community_members/pallp.md

@@ -26,4 +26,4 @@ permalink: '/community/members/pallavi-priyadarshini.html'
 redirect_from: '/authors/pallp/'
 ---
 
-**Pallavi Priyadarshini** is a Senior Engineering Manager at AWS leading the development of high-performing and scalable search and security technologies for the OpenSearch Project and Amazon OpenSearch Service.
+**Pallavi Priyadarshini** is a Senior Engineering Manager at the OpenSearch Project leading the development of high-performing and scalable technologies for search, security, releases, and dashboards.

_community_members/yupeng.md

@@ -0,0 +1,23 @@
+---
+short_name: yupeng
+name: Yupeng Fu
+photo: "/assets/media/community/members/yupeng.png"
+title: 'OpenSearch Community Member: Yupeng Fu'
+primary_title: Yupeng Fu
+breadcrumbs:
+  icon: community
+  items:
+    - title: Community
+      url: /community/index.html
+    - title: Members
+      url: /community/members/index.html
+    - title: 'Yupeng Fu's Profile'
+      url: '/community/members/yupeng-fu.html'
+job_title_and_company: 'Principal Software Engineer at Uber'
+personas:
+  - author
+permalink: '/community/members/yupeng-fu.html'
+redirect_from: '/authors/yupeng/'
+---
+
+**Yupeng Fu** is a Principal Software Engineer on Uber's SSD (Storage, Search and Data) team. He leads several teams building scalable, reliable, and performant search and streaming platforms.

_posts/2024-09-12-opensearch-project-roadmap-2024-2025.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title:  OpenSearch Project Roadmap 2024&endash;2025
+title:  OpenSearch Project Roadmap 2024–2025
 authors:
 - pallp
 - bburkholder
@@ -9,7 +9,8 @@ authors:
 date: 2024-09-12
 categories:
   - community-updates
-excerpt: OpenSearch is a rapidly growing open-source product suite comprising a search engine, an ingestion system, language clients, and a user interface for analytics. OpenSearch contributors and maintainers are innovating in all these areas at a fast pace. To steer the project's development effectively, we have revamped the project roadmap to provide better transparency into both short- and long-term enhancements. In this blog post, we are excited to share the new theme-based, community-driven OpenSearch Project Roadmap for 2024–2025.
+excerpt: OpenSearch is a rapidly growing open-source product suite comprising a search engine, an ingestion system, language clients, and a user interface for analytics. OpenSearch contributors and maintainers are innovating in all these areas at a fast pace. To steer the project's development effectively, we have revamped the project roadmap to provide better transparency into both short- and long-term enhancements. In this blog post, we are excited to share the new theme-based, community-driven OpenSearch Project Roadmap for 2024–2025.
+featured_blog_post: true 
 additional_author_info: We sincerely appreciate the contributions to this blog from Yupeng Fu (Uber), Karthikeyan Ramasamy (Uber), Shuyi Z. (Uber), Shubham Gupta (Uber), George Luong (Slack/Salesforce), Austin Lee (Aryn), Andriy Redko (Aiven), Yuncheng Lu (ByteDance), Tianjin Li (Cohere), and AWS contributors (Anandhi Bumstead, Carl Meadows, Michael Froh, Shweta Thareja, Saurabh Singh, Kunal Khatua, Andrew Ross, Sean Zheng, Anirudha Jadhav, Gopala Krishna Ambareesh, Yan Zeng, Huan Jiang, Vamshi Vijay Nakkirtha, Craig Perkins, Peter Zhu, Joshua Bright, David Venable, Bukhtawar Khan, Prabhakar Sithanandam, Ranjith Ramachandra, Sorabh Hamirwasia, Charlie Yang, Rohit Wali, Peng Huo, and Fanit Kolchina). 
 meta_keywords: OpenSearch roadmap, open source search, vector database, generative AI, observability, log analytics, security analytics, cloud native architecture, OpenSearch performance optimization
 meta_description:  Explore the OpenSearch Project's roadmap for 2024-2025 and learn how the community is driving the project forward to make it the preferred open-source solution for search, analytics, and generative AI applications.
@@ -130,7 +131,7 @@ The OpenSearch Project continues to enhance its observability and security analy
 
 **Next-generation snapshots for remote-backed clusters**: [Snapshots v2](https://github.com/opensearch-project/OpenSearch/issues/15057) aims to enhance the scalability of snapshots for remote-backed clusters and reduce dependence on per-shard state updates in the cluster manager. The new snapshots rely on a timestamp-based pinning strategy, where instead of resolving shard-level files at snapshot time, the timestamp for the snapshot is pinned and the resolution is deferred until restore time. This approach makes the snapshot process much faster, allowing snapshot operations to finish within a couple of minutes, even for larger clusters, while significantly reducing the computational load associated with data backup. Timestamp pinning serves as the fundamental building block for future features, such as [Point-In-Time-Restore (PITR)](https://github.com/opensearch-project/OpenSearch/issues/1147).
 
-**Scaling admin APIs**: For large cluster configurations, cluster manager nodes become scaling bottlenecks as multiple admin APIs obtain the cluster state from the active cluster manager node, even if the latest state is present locally or present in a remote store. With the ongoing optimizations, the coordinator node can [serve the admin APIs without relaying the request](https://github.com/opensearch-project/OpenSearch/pull/12252/) to the cluster manager node in most cases. Also, for APIs like CAT Shards and CAT Snapshotos, the response size increases as the cluster expands to 100K shards or more. We plan to introduce [pagination](https://github.com/opensearch-project/OpenSearch/issues/14258) and [cancellation](https://github.com/opensearch-project/OpenSearch/issues/13908) for these APIs to ensure that they continue to operate efficiently regardless of the metadata size. We are implementing multiple optimizations to the Stats and Cluster APIs that will eliminate redundant processing and perform [pre-aggregation](https://github.com/opensearch-project/OpenSearch/pull/14426) on the data node before responding to the coordinator node receiving the user request.
+**Scaling admin APIs**: For large cluster configurations, cluster manager nodes become scaling bottlenecks as multiple admin APIs obtain the cluster state from the active cluster manager node, even if the latest state is present locally or present in a remote store. With the ongoing optimizations, the coordinator node can [serve the admin APIs without relaying the request](https://github.com/opensearch-project/OpenSearch/pull/12252/) to the cluster manager node in most cases. Also, for APIs like CAT Shards and CAT Snapshots, the response size increases as the cluster expands to 100K shards or more. We plan to introduce [pagination](https://github.com/opensearch-project/OpenSearch/issues/14258) and [cancellation](https://github.com/opensearch-project/OpenSearch/issues/13908) for these APIs to ensure that they continue to operate efficiently regardless of the metadata size. We are implementing multiple optimizations to the Stats and Cluster APIs that will eliminate redundant processing and perform [pre-aggregation](https://github.com/opensearch-project/OpenSearch/pull/14426) on the data node before responding to the coordinator node receiving the user request.
 
 ### Roadmap Theme 6: Stability, Availability, and Resiliency