This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4ad9493c1c8 [doc] Reorganize community contribution guide (#3974)
4ad9493c1c8 is described below
commit 4ad9493c1c809252772f75444482ab6f338788d2
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Fri Jul 10 17:32:02 2026 +0800
[doc] Reorganize community contribution guide (#3974)
## Summary
- merge the old contribution, contributor guide, and Doris Future pages
into a single MDX contribution guide
- add aligned contribution path cards, benefits, and tabbed
participation guides in English and Chinese
- update community navigation and related links to point to the new
guide
- simplify several community doc page titles
## Validation
- git diff --check
- yarn docs:links:changed
Note: local Docusaurus build was not run.
---
community/doris-future.md | 65 ---
community/feedback.md | 2 +-
community/how-to-contribute/contribute-doc.md | 2 +-
community/how-to-contribute/contribute-to-doris.md | 107 -----
.../how-to-contribute/contribute-to-doris.mdx | 463 +++++++++++++++++++++
community/how-to-contribute/contributor-guide.md | 150 -------
community/how-to-contribute/pull-request.md | 2 +-
community/join-community.md | 10 +-
community/security.md | 2 +-
community/subscribe-mail-list.md | 2 +-
community/team.md | 4 +-
.../current/doris-future.md | 65 ---
.../current/feedback.md | 2 +-
.../current/how-to-contribute/contribute-doc.md | 2 +-
.../how-to-contribute/contribute-to-doris.md | 107 -----
.../how-to-contribute/contribute-to-doris.mdx | 463 +++++++++++++++++++++
.../current/how-to-contribute/contributor-guide.md | 150 -------
.../current/how-to-contribute/pull-request.md | 2 +-
.../current/join-community.md | 10 +-
.../current/security.md | 2 +-
.../current/subscribe-mail-list.md | 2 +-
.../current/team.md | 4 +-
sidebarsCommunity.json | 2 -
23 files changed, 956 insertions(+), 664 deletions(-)
diff --git a/community/doris-future.md b/community/doris-future.md
deleted file mode 100644
index 11ec2fc65b4..00000000000
--- a/community/doris-future.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Developer Growth Program
-language: en
-description: Apache Doris growth program for new developers, with mentors
guiding first-time contributions through `doris-future` tagged tasks.
-keywords:
- - Apache Doris
- - Developer Growth Program
- - doris-future
- - First-time contribution
- - Mentorship
- - First contribution
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- Knowledge type: Program introduction -->
-<!-- Applicable scenario: New developers making their first code contribution
to Doris -->
-
-## Introduction
-
-Doris Future Plan is a growth program offered by the Apache Doris community
for new developers. Its goal is to help more developers get started with Doris
kernel development quickly. The community welcomes developers interested in
OLAP, database kernels, and distributed systems.
-
-## How to Participate
-
-<!-- Knowledge type: Procedure -->
-
-New developers can join through the following steps:
-
-1. Open the [GitHub Issue](https://github.com/apache/doris/issues) page of the
Doris community.
-2. Filter tasks labeled with `doris-future`. Each task is annotated with:
- - Required skills (such as C++ or Java).
- - Difficulty level.
-3. Comment on the task you are interested in, and discuss task details with
the assigned mentor.
-4. If you lack machine resources locally, the community can provide
development machines to help.
-
-If you run into any difficulty during participation, send an email to
`[email protected]` describing the problem, and the community will do its
best to help.
-
-## Mentorship
-
-<!-- Knowledge type: Rules and conventions -->
-
-Every `doris-future` task is assigned a mentor for follow-up. The support a
mentor provides includes:
-
-| Support item | Description |
-|--------|------|
-| Task walkthrough | Explains the goal, background, and implementation details
of the task |
-| Guidance on approach | Provides concrete implementation ideas and related
knowledge points |
-| Code review | Reviews code and offers improvement suggestions to raise
engineering quality |
diff --git a/community/feedback.md b/community/feedback.md
index aad14201b27..429dea0063d 100644
--- a/community/feedback.md
+++ b/community/feedback.md
@@ -1,5 +1,5 @@
---
-title: Report Issues to Apache Doris
+title: Report Issues
language: en
description: "Official channels for reporting bugs or sending suggestions to
Apache Doris: mailing list and GitHub Issue, with writing tips for high-quality
issue reports."
keywords:
diff --git a/community/how-to-contribute/contribute-doc.md
b/community/how-to-contribute/contribute-doc.md
index 6f866febbc3..4d843240353 100644
--- a/community/how-to-contribute/contribute-doc.md
+++ b/community/how-to-contribute/contribute-doc.md
@@ -40,7 +40,7 @@ Whether you are working on historical versions or the latest
version of the docu
For the PR submission workflow, you can also refer to:
-- [Contribute to Doris](./contribute-to-doris)
+- [Community Contribution Guide](./contribute-to-doris.mdx)
- [Pull Request Guide](./pull-request)
:::
diff --git a/community/how-to-contribute/contribute-to-doris.md
b/community/how-to-contribute/contribute-to-doris.md
deleted file mode 100644
index d4f98dbc78d..00000000000
--- a/community/how-to-contribute/contribute-to-doris.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: Contributing to Apache Doris
-language: en
-description: How to contribute code, documentation, and bug fixes to Apache
Doris. An overview for getting started with community contributions.
-keywords:
- - Apache Doris
- - contribute code
- - contribute documentation
- - submit PR
- - bug fix
- - community participation
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- Knowledge type: Overview -->
-<!-- Applicable scenario: First-time learning how to contribute to Apache
Doris -->
-
-Thank you for your interest in the Apache Doris project. The community
welcomes participation in any form, including suggestions, opinions (including
criticism), comments, and contributions of code and documentation.
-
-There are many ways to participate in the Doris project: code implementation,
test writing, process and tooling improvements, documentation refinement, and
more. Every contribution is recognized, and the community will add you to the
contributor list. Once your contributions reach a certain level, you also have
the opportunity to become an Apache Committer, receive an Apache email address,
and be listed in the [Apache Committer
list](http://people.apache.org/committer-index.html).
-
-For any questions, you can reach the community through the following channels:
WeChat, Slack, and the mailing list. The community will respond promptly.
-
-## Getting Started
-
-<!-- Knowledge type: Steps -->
-
-When you first arrive at the Doris community, you can establish contact in the
following ways:
-
-1. Follow the Doris [GitHub repository](https://github.com/apache/doris).
-2. Subscribe to the [mailing list](../subscribe-mail-list) to keep up with
development activity.
-3. Join the Doris WeChat group (add WeChat ID `morningman-cmy` with the note
"Join Doris Group").
-4. Join the Doris [Slack](https://doris.apache.org/slack) channel.
-
-Through these channels, you can stay up to date with Doris development and
share your views on topics you care about.
-
-## Doris Code and Documentation
-
-<!-- Knowledge type: Project structure -->
-
-As shown in the [GitHub](https://github.com/apache/doris) repository, the
Apache Doris core codebase mainly consists of the Frontend (FE), Backend (BE),
and Broker (for reading external storage such as HDFS). The documentation
includes the official website, the GitHub Wiki, and the runtime online help
manual. Details for each component are as follows:
-
-| Component | Description | Language |
-|---------|---------|---------|
-| [Frontend daemon (FE)](https://github.com/apache/doris) | Consists of the
query coordinator and the metadata manager | Java |
-| [Backend daemon (BE)](https://github.com/apache/doris) | Handles data
storage and query fragment execution | C++ |
-| [Broker](https://github.com/apache/doris) | Reads HDFS data into Doris |
Java |
-| [Website](https://github.com/apache/doris-website) | The official Doris
website | Markdown |
-| [Manager](https://github.com/apache/doris-manager) | Doris Manager | Java |
-| [Flink Connector](https://github.com/apache/doris-flink-connector) | Doris
Flink Connector | Java |
-| [Spark Connector](https://github.com/apache/doris-spark-connector) | Doris
Spark Connector | Java |
-| Doris runtime Help documentation | The online help manual available when
running Doris | Markdown |
-
-## Improving Documentation
-
-Documentation is the main entry point for learning about Apache Doris, and it
is one of the areas where the community most needs help.
-
-Reading the documentation deepens your understanding of Doris and covers
features and technical details. If you find any problems in the documentation,
please contact the community.
-
-If you would like to improve documentation quality (including correcting page
addresses, fixing links, and writing better introductory documents), the
community very much welcomes your contributions.
-
-Most Doris documentation is written in Markdown, and you can submit changes
directly in the [apache/doris-website](https://github.com/apache/doris-website)
repository. Related guides:
-
-- To submit documentation changes, see the [Documentation Contribution
Guide](https://doris.apache.org/zh-CN/community/how-to-contribute/contribute-doc).
-- To submit code changes, see the [Code Submission
Guide](https://doris.apache.org/zh-CN/community/how-to-contribute/pull-request).
-
-## Reporting Bugs or Issues
-
-<!-- Applicable scenario: Reporting bugs / fixing issues -->
-
-If you find a bug or issue, there are two ways to handle it:
-
-1. **Report the issue**: submit a new issue through GitHub
[Issues](https://github.com/apache/doris/issues/new/choose). Community members
will address it on a regular basis.
-2. **Fix it yourself**: read and analyze the source code to fix it yourself,
then submit a [Pull Request](./pull-request).
-
-> Tip: Before you start fixing, it is recommended to talk to the community
first to confirm whether someone is already working on the same issue.
-
-## Modifying Code and Submitting a PR
-
-<!-- Knowledge type: Steps -->
-
-The basic workflow for contributing code:
-
-1. Download the code, compile it, and deploy and run it to verify that the
behavior matches expectations (see the [Compilation
Documentation](https://doris.apache.org/zh-CN/docs/install/source-install/compilation-with-docker/)
for reference).
-2. Fork the `apache/doris` repository to your own account on GitHub.
-3. Create a separate branch for your changes, and add the original repository
as `upstream`.
-4. Submit a PR. For detailed steps, see the [Pull Request
Guide](./pull-request).
-
-Whether you are fixing a bug or adding a new feature, the community very much
welcomes your contributions.
diff --git a/community/how-to-contribute/contribute-to-doris.mdx
b/community/how-to-contribute/contribute-to-doris.mdx
new file mode 100644
index 00000000000..7fc760b8619
--- /dev/null
+++ b/community/how-to-contribute/contribute-to-doris.mdx
@@ -0,0 +1,463 @@
+---
+title: Community Contribution Guide
+language: en
+description: Learn how to contribute to Apache Doris through code development,
content creation, and community outreach.
+keywords:
+ - Apache Doris
+ - community contribution
+ - code development
+ - content creation
+ - community outreach
+ - Contributor
+ - Committer
+ - PMC
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<style>{`
+.contribution-path-grid {
+ display: grid;
+ grid-template-columns: repeat(3, minmax(0, 1fr));
+ grid-template-rows: auto auto 1fr auto auto;
+ gap: 16px;
+ margin: 24px 0;
+}
+
+.contribution-path-card {
+ display: grid;
+ grid-row: span 5;
+ grid-template-rows: subgrid;
+ gap: 12px;
+ min-height: 100%;
+ padding: 20px;
+ border: 1px solid var(--ifm-color-emphasis-200);
+ border-radius: 8px;
+ background: var(--ifm-background-surface-color);
+ color: var(--ifm-font-color-base);
+ text-decoration: none;
+}
+
+.contribution-benefits-card {
+ grid-column: 1 / -1;
+ padding: 20px;
+ border: 1px solid var(--ifm-color-emphasis-200);
+ border-radius: 8px;
+ background: var(--ifm-background-surface-color);
+}
+
+.contribution-path-card:hover {
+ border-color: var(--ifm-color-primary);
+ color: var(--ifm-font-color-base);
+ text-decoration: none;
+}
+
+.contribution-path-card h3,
+.contribution-benefits-card h3 {
+ margin: 0;
+ font-size: 1.15rem;
+}
+
+.contribution-path-card p,
+.contribution-benefits-card p {
+ margin: 0;
+}
+
+.contribution-path-card ul,
+.contribution-benefits-card ul {
+ margin: 0;
+ padding-left: 20px;
+}
+
+.contribution-path-card strong,
+.contribution-benefits-card strong {
+ color: var(--ifm-color-primary);
+}
+
+.contribution-benefits-list {
+ columns: 2;
+ column-gap: 32px;
+ margin-top: 12px;
+}
+
+.contribution-card-benefit {
+ align-self: start;
+}
+
+.contribution-next-step {
+ align-self: end;
+ color: var(--ifm-color-primary);
+ font-weight: 600;
+}
+
+@media (max-width: 996px) {
+ .contribution-path-grid {
+ grid-template-columns: 1fr;
+ }
+
+ .contribution-benefits-list {
+ columns: 1;
+ }
+}
+`}</style>
+
+Apache Doris welcomes developers, users, technical writers, speakers, and
community organizers from around the world. You can contribute through code
development, content creation, or community outreach. Each path helps the
project grow and gives contributors a public record of open source
collaboration.
+
+<div className="contribution-path-grid">
+ <a className="contribution-path-card"
href="?path=developer#community-participation-guide">
+ <h3>Code development</h3>
+ <p><strong>Best for:</strong> contributors who want to work directly on
Doris engineering.</p>
+ <ul>
+ <li>Fix bugs and build new features.</li>
+ <li>Improve performance, stability, or observability.</li>
+ <li>Add unit tests, regression tests, and integration tests.</li>
+ <li>Improve build, CI, release, development tooling, and engineering
workflows.</li>
+ <li>Review PRs, and add technical docs, user docs, or examples.</li>
+ </ul>
+ <p className="contribution-card-benefit"><strong>Once your contribution is
merged, you become an Apache Doris Contributor.</strong></p>
+ <span className="contribution-next-step">Read the Guide -></span>
+ </a>
+ <a className="contribution-path-card"
href="?path=content#community-participation-guide">
+ <h3>Content creation</h3>
+ <p><strong>Best for:</strong> contributors who know Doris use cases and
want to share practical experience.</p>
+ <ul>
+ <li>Write technical blogs and production case studies.</li>
+ <li>Create getting started tutorials and best practices.</li>
+ <li>Record videos about features, deployment, tuning, or
troubleshooting.</li>
+ <li>Speak at meetups, webinars, and conferences.</li>
+ <li>Translate docs, blogs, event materials, or video subtitles.</li>
+ </ul>
+ <p className="contribution-card-benefit"><strong>High quality content
contributions receive community swag as a thank you.</strong></p>
+ <span className="contribution-next-step">Read the Guide -></span>
+ </a>
+ <a className="contribution-path-card"
href="?path=community#community-participation-guide">
+ <h3>Community outreach</h3>
+ <p><strong>Best for:</strong> contributors who understand user needs and
enjoy working with people.</p>
+ <ul>
+ <li>Answer questions on Slack, GitHub, and mailing lists.</li>
+ <li>Help new users find the right docs, examples, and community
channels.</li>
+ <li>Organize online or offline meetups, workshops, office hours, or user
talks.</li>
+ <li>Invite users to share production practices and migration
stories.</li>
+ <li>Collect user feedback and move it into public community
channels.</li>
+ </ul>
+ <p className="contribution-card-benefit"><strong>Active community
participants receive community swag as a thank you.</strong></p>
+ <span className="contribution-next-step">Read the Guide -></span>
+ </a>
+ <div className="contribution-benefits-card">
+ <h3>Benefits</h3>
+ <p>Depending on the type, quality, and consistency of your contributions,
you may receive:</p>
+ <ul className="contribution-benefits-list">
+ <li>Public recognition in Apache Doris community channels.</li>
+ <li>Acknowledgment in contributor lists, community thanks, or event
recaps.</li>
+ <li>Opportunities to publish content on the Apache Doris website, blog,
social channels, or video channels.</li>
+ <li>Opportunities to speak at community events.</li>
+ <li>More chances to talk with Maintainers, Committers, PMC members, and
experienced users.</li>
+ <li>Priority access to selected meetups, webinars, conference topics, or
other community programs.</li>
+ <li>A public record of technical contribution and personal impact.</li>
+ <li>Community swag, keepsakes, or special gifts.</li>
+ </ul>
+ <p>For members who contribute technical work consistently and at a high
level, the community may invite them to become <strong>Apache Doris Committers
or PMC members</strong> through the Apache governance process. Doris Summit
also selects <strong>Outstanding Community Heroes</strong> each year to thank
users, developers, and community advocates who made notable contributions.</p>
+ </div>
+</div>
+
+## Community Participation Guide
+
+The sections below explain how to get started on each path.
+
+:::tip Tip
+This guide may change as community processes evolve. Join the [Apache Doris
Slack community](https://doris.apache.org/slack) for the latest updates.
+:::
+
+<Tabs groupId="contribution-path" queryString="path">
+<TabItem value="developer" label="Code development guide" default>
+
+### Where to find tasks
+
+You can find contribution opportunities in these places:
+
+- Slack: ask questions, start a discussion, confirm context, or find the right
person to talk to.
+- [Apache Doris GitHub Issues](https://github.com/apache/doris/issues): good
for bugs, feature requests, improvement ideas, and open tasks.
+- [Apache Doris GitHub
Discussions](https://github.com/apache/doris/discussions): good for technical
discussions, usage questions, and design proposals.
+- Roadmap: good for longer term technical work. You can usually find it in a
pinned Issue on the GitHub Issues page.
+- Existing PRs: good for review, testing, validation, or helping move a change
forward.
+
+New contributors can start with small, focused tasks: fix docs, add tests, fix
a simple bug, reproduce an Issue, improve an error message, or clean up an
example. For larger features or behavior changes, start a discussion in the
Apache Doris Slack `#dev` channel and ask Core Maintainers for context.
+
+### Code contribution expectations
+
+Before you submit code, try to do the following:
+
+- Fork the `apache/doris` repository and create a separate branch from the
latest main branch.
+- Keep each PR focused on one clear problem. Avoid mixing unrelated changes in
one PR.
+- Use a PR title and description that explain the goal, scope, and validation.
+- Link the related Issue, Discussion, or mailing list thread.
+- Add the necessary unit tests, regression tests, or manual validation steps.
+- Update the docs if the change affects user behavior, configuration, SQL
semantics, error messages, or compatibility.
+- Call out compatibility, performance, stability, or behavior risks in the PR
description.
+
+A good PR usually includes:
+
+- Background: why the change is needed.
+- Approach: what changed and why.
+- Tests: which tests or validation steps were run, and what happened.
+- Risks: whether the change affects compatibility, performance, stability, or
user behavior.
+- Docs: whether docs are needed, and where they were updated.
+
+The community supports using AI to help with coding, debugging, and review,
but contributors must follow these rules:
+
+- Use capable models for development, debugging, and review. Do not rely on
low quality generated code for important changes.
+- You are responsible for the code you submit. The community does not accept
AI-generated code without a human owner.
+
+### Standard merge flow
+
+Code changes usually go through this process:
+
+1. The contributor opens a Pull Request.
+2. A Committer or someone with higher permissions triggers CI and AI Review.
You can ask for help in the Slack `#dev` channel.
+3. The contributor fixes build, test, or format issues reported by CI and
review. AI feedback is also part of the review process. Apply useful
suggestions, and explain in the PR when a suggestion does not apply.
+4. The contributor rebases on the latest main branch and resolves conflicts
when needed.
+5. All required CI checks pass.
+6. A Reviewer approves the PR.
+7. A Committer completes the merge.
+
+Required CI checks must pass before a PR can be merged. Non-required checks do
not block the merge.
+
+### How to move review forward
+
+Contributors should actively move their own PRs forward instead of waiting for
Reviewers. The Apache Doris contribution guide also encourages contributors to
act as the Moderator for their own PRs and help carry the PR from submission to
merge.
+
+Recommended practices:
+
+- Give Reviewers enough context in the PR description.
+- Share the PR link in the Slack `#dev` channel and ask for Reviewers.
+- Reply to Review comments promptly.
+- Mark resolved items as resolved after you address them.
+- Give technical reasons when you disagree with a comment.
+- Rebase regularly to avoid long running conflicts.
+- If a PR has stalled, politely ping the relevant Reviewers in the PR.
+- If you are not sure who should review the PR, ask in Slack for help finding
the right module owner.
+
+Ways to find suitable Reviewers:
+
+- Look at recently merged PRs in the same module.
+- Check the commit history of the related files.
+- Check GitHub suggested Reviewers or CODEOWNERS, if available.
+- Ask in Slack for help finding a suitable Reviewer, but bring important
technical conclusions back to GitHub or the mailing list.
+
+</TabItem>
+<TabItem value="content" label="Content creation guide">
+
+### What to submit and where
+
+#### Blog posts
+
+Good topics include:
+
+- Deep dives into Doris features.
+- Query optimization, load optimization, operations tuning, and
troubleshooting.
+- Lakehouse, real-time data warehouse, log analytics, user behavior analytics,
and other practical scenarios.
+- Migration experience from Elasticsearch, ClickHouse, Hive, Trino, or other
systems to Doris.
+- Production troubleshooting and performance tuning write-ups.
+- New release capability overviews and usage advice.
+
+How to submit:
+
+- Start a discussion in the Slack `#dev` channel.
+- Submit a Markdown file to the `/blog` directory in the
`apache/doris-website` repository. Doris Maintainers can help if needed.
+
+#### Case studies
+
+Good case studies include:
+
+- The business background of the company or team.
+- Why the team chose Apache Doris.
+- System architecture and data flow.
+- Data scale, query patterns, and performance goals.
+- Problems found during migration or rollout.
+- Results, benefits, and lessons learned after going live.
+
+How to submit:
+
+- If the content includes company names, business data, or architecture
diagrams, get internal approval first or remove sensitive information.
+- Start a discussion in the Slack `#dev` channel. The community can help edit,
translate, or publish the case study.
+
+#### Tutorials
+
+Good tutorial topics include:
+
+- Getting started.
+- Deployment and upgrade.
+- Data loading.
+- Query tuning.
+- Materialized views.
+- Inverted indexes.
+- Compute-storage separation.
+- Lakehouse queries.
+- Log analytics and observability scenarios.
+
+How to submit:
+
+- Start a discussion in the Slack `#dev` channel.
+- General content that will stay accurate over time usually belongs in the
official docs.
+- Practical, scenario-based, or version-specific content usually works better
as a blog post.
+- Example code, scripts, and configuration should be reproducible when
possible.
+
+#### Videos
+
+Good video topics include:
+
+- One-to-five-minute feature demos.
+- Installation and deployment walkthroughs.
+- Best practice explainers.
+- Scenario based demos.
+- Meetup or webinar recordings.
+- User interviews or case study talks.
+
+How to submit:
+
+- Start a discussion in the Slack `#dev` channel.
+- Confirm the topic, script, or outline with the community first.
+- After the video is ready, the community can help publish it to YouTube,
Bilibili, or other official video channels.
+- If the video includes company names, customer names, performance data, or
internal system screenshots, get approval first or remove sensitive information.
+
+#### Talks
+
+Good formats include:
+
+- Meetup talks.
+- Webinar talks.
+- Conference talks.
+- Release feature introductions.
+- Contributor onboarding sessions.
+- User story sessions.
+
+How to submit:
+
+- Start a discussion in the Slack `#dev` channel.
+- Share the topic, abstract, target audience, language, expected length, and
speaker information with the community.
+- The community can help refine the topic, review the technical content,
promote the session, and support the registration page. Funding or venue
support may also be possible when needed.
+
+#### Translations
+
+Good translation work includes:
+
+- Official docs.
+- Blog posts.
+- Event recaps.
+- Video subtitles.
+- Tutorials and best practices.
+
+How to submit:
+
+- Submit documentation translations through a PR to `apache/doris-website`.
+- For blog or event translations, confirm the target page and publishing
channel with the community first.
+- Keep the technical meaning accurate. Do not change the meaning for marketing
language.
+
+### Publishing channels
+
+Depending on the content type and review result, content may be published
through:
+
+- Apache Doris official website.
+- Apache Doris official blog.
+- Apache Doris Medium.
+- Apache Doris YouTube.
+- Apache Doris LinkedIn.
+- Apache Doris X/Twitter.
+- Apache Doris Slack.
+- Community newsletters, event recaps, or release topic pages.
+
+Content usually needs a technical accuracy review before publication. Content
that includes performance data, commercial case studies, customer names, or
company information also needs authorization.
+
+</TabItem>
+<TabItem value="community" label="Community outreach guide">
+
+### Ways to participate
+
+Community contributors can join or organize activities such as:
+
+- Online meetup: topic-based online sharing for global users.
+- Offline meetup: in-person discussions for a city or region.
+- Webinar: online sessions about a feature, scenario, or release.
+- Workshop: hands-on sessions for deployment, loading, tuning, or case
practice.
+- Office hour: recurring Q&A sessions for user questions.
+- User story session: production practice talks from real users.
+- Release introduction: sessions about new features and upgrade advice.
+- Contributor onboarding: sessions that help new contributors understand the
codebase, process, and community workflow.
+- Local community event: localized events for a specific language or region.
+- Hackathon or contribution sprint: focused contribution work on Issues, docs,
tests, or tools.
+
+### How to propose an event
+
+Event organizers should prepare:
+
+- Event topic.
+- Target audience.
+- Event format.
+- Event language.
+- Time and time zone.
+- Speaker or host.
+- Expected length.
+- Support needed from the community.
+- Promotion plan.
+- Whether the event will produce slides, a recording, a blog post, or a recap.
+
+Start the discussion in the Slack `#dev` channel first. This lets more
community members participate and keeps the process open, which is how Apache
communities are expected to work.
+
+### Support from the community
+
+Depending on the event type, event quality, and available resources, the
community may help with:
+
+- Promotion through official media channels.
+- Topic planning.
+- Speaker recommendations.
+- Technical review for slides or demos.
+- Registration page or event page support.
+- Recording and replay distribution.
+- Social media promotion.
+- Community swag.
+- Limited event budget, such as venue, materials, refreshments, or basic
operations costs.
+- Event recap publication.
+
+Funding, gifts, travel, venues, and sponsorship support can be discussed with
the community. Event organizers should explain the budget use, expected impact,
and deliverables in advance.
+
+</TabItem>
+</Tabs>
+
+## Community Code of Conduct
+
+All contributors should follow these principles:
+
+- Respect others and keep communication professional, friendly, and
constructive.
+- Keep important technical discussions and community decisions in public
channels whenever possible.
+- Stay open to code review, documentation review, and content review.
+- If you disagree with review feedback, explain your technical reasoning
clearly.
+- Avoid making community decisions privately when they should be discussed in
public.
+- Submit original content, or clearly cite sources for quoted or referenced
material.
+- Avoid exaggerated, unverifiable, or misleading performance and business
claims.
+- Add tests for code changes whenever possible.
+- Update docs when a change affects user-visible behavior.
+- Do not disclose user privacy, sensitive customer information, or company
confidential information.
+- Follow responsible disclosure for security issues. Do not publish details in
public channels before the issue is handled.
+- Respect Apache community values and the ASF Code of Conduct.
+
+Contributors participate as members of an open source community. If you
represent a company in some activities, say so when it matters. The
contribution itself should still follow Apache's open and transparent way of
working, where contribution matters.
diff --git a/community/how-to-contribute/contributor-guide.md
b/community/how-to-contribute/contributor-guide.md
deleted file mode 100644
index 8370bd9e55e..00000000000
--- a/community/how-to-contribute/contributor-guide.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: Contributor Growth Path
-language: en
-description: "Apache Doris contributor growth path: standards for moving from
Contributor to Committer / PMC, plus Code Review and PR rules."
-keywords:
- - Apache Doris
- - Contributor
- - Committer
- - PMC
- - Code Review
- - Pull Request rules
- - Community roles
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Contributor Growth Path
-
-<!-- Knowledge type: Rules and conventions -->
-<!-- Applicable scenario: Understanding community roles / Code Review / PR
merge rules -->
-
-This document describes the role structure in the Apache Doris community, and
the path for growing from Contributor into Committer and PMC.
-
-## Community Roles
-
-In Apache projects, developers fall into three roles:
-
-| Role | Definition | How It Is Granted |
-|------|------------|-------------------|
-| **Contributor** | Once code is officially merged into the repository, the
developer automatically becomes a Contributor to that project | Submit code and
have it merged |
-| **Committer** | Has merge permission on the code repository | Nominated and
elected by a vote of the PMC (Project Management Committee) |
-| **PMC Member** | A member of the Project Management Committee, with voting
rights on major project decisions such as releases | Nominated and elected by a
vote of the PMC |
-
-Different roles carry different rights and responsibilities, but promotion
does not have strict quantitative criteria. What matters more is sustained
investment in the community and the influence built there.
-
-## Contributor Newcomer Guide
-
-### Subscribe to the Public Mailing Lists
-
-<!-- Knowledge type: Procedure -->
-
-Subscribe to the `[email protected]` and `[email protected]`
mailing lists by sending an email to `[email protected]` and
`[email protected]` respectively.
-
-The `commits` mailing list is especially important, because all GitHub Issue
and PR activity is automatically forwarded to it.
-
-For detailed subscription steps, see [Subscribe to Mailing
Lists](../subscribe-mail-list).
-
-## Code Review Guide
-
-<!-- Knowledge type: Rules and conventions -->
-<!-- Applicable scenario: Performing Code Review -->
-
-1. Always hold reviews to a high standard. This is how the overall quality of
the product is maintained.
-
-2. Changes to user-facing interfaces or to the overall architecture need to be
fully discussed in the community. You can start the discussion on the mailing
list or on an Issue. Changes to user-facing interfaces include adding new SQL
functions, adding new HTTP endpoints, or adding new features. This keeps the
product consistent.
-
-3. **Test coverage**: New logic must be covered by corresponding tests. For
existing legacy code where adding tests is difficult, use your judgment.
-
-4. **Documentation**: New features must come with documentation, otherwise
they cannot be merged. English documentation is required, and Chinese
documentation is recommended in addition.
-
-5. **Code readability**: If a Reviewer finds the code logic unclear, the
Reviewer can ask the Contributor to explain it and to add sufficient comments
in the code.
-
-6. Try to give a clear conclusion at the end of your comment: approval, or
change request. For minor issues, leaving a comment alone is fine.
-
-7. If you have already looked at the code and think it is fine, but want
others to confirm as well, you can leave a `+1 Comment`.
-
-8. Respect each other and learn from each other. Keep a polite tone in your
comments, and give reasons when you make suggestions.
-
-## Pull Request Guide
-
-<!-- Knowledge type: Rules and conventions -->
-<!-- Applicable scenario: Submitting a PR / driving a PR to merge -->
-
-### The Three Roles in a PR
-
-Merging a PR involves three roles:
-
-| Role | Responsibility |
-|------|----------------|
-| **Contributor** | The author who submits the PR |
-| **Reviewer** | The person who leaves code-level comments on the PR |
-| **Moderator** | The coordinator for merging the PR. Responsible for setting
relevant labels on the PR, driving Reviewers to comment, driving the author to
make changes, and merging the PR |
-
-In a specific PR, one person may play several roles. For example, a PR
submitted by a Contributor makes that person both the Contributor and the
Moderator of the PR.
-
-### PR Merge Rules
-
-| Rule | Requirement |
-|------|-------------|
-| Minimum `+1` count for a normal PR | At least 1 `+1` from **a Committer
other than the author** |
-| Minimum `+1` count for interface-level or architectural changes | At least
**3 `+1`s** |
-| Waiting time after the first `+1` | **At least one working day**, to give
other community members time to review |
-| Regression tests | **Must all pass** |
-| Comment replies | The Moderator must confirm that all comments have been
replied to |
-| Merge method | Always use **"Squash and merge"** |
-
-### Key Points for PR Collaboration
-
-1. A Contributor can assign a PR to themselves to act as the Moderator for the
whole PR, taking on the work of driving it forward. After self-assignment,
other Contributors know that the PR has someone responsible for it.
-
-2. **Contributors are encouraged to act as the Moderator of their own PRs.**
-
-3. Reviewers need to perform code-level reviews. Refer to the Code Review
Guide above.
-
-4. Once a Reviewer has commented on a PR, the Reviewer needs to continue
following up on subsequent changes to that PR. It is not acceptable to leave a
comment and then ignore the Contributor's follow-up replies.
-
-5. When different Reviewers disagree about a change, try to resolve it through
discussion. If discussion cannot resolve it, send an email to
`[email protected]` to call a vote, and follow the rule that the minority
defers to the majority.
-
-### Admission Check for New External Dependencies
-
-<!-- Knowledge type: Rules and conventions -->
-
-**Be especially careful when adding new external dependencies.** Before
introducing a new library, the following questions must be answered:
-
-- What functionality does the new external library provide? Can existing
libraries provide this functionality (possibly with some effort)?
-- Is the external library maintained by an active community of contributors?
-- What are the license terms of the new library?
-- Will the library be added to a base module? This affects other parts of the
Doris codebase. Take Java as an example: if the new library introduces many
transitive dependencies, you may run into unexpected class-conflict issues that
are hard to catch in testing, because they depend on the order in which
libraries are loaded at runtime.
-
-## From Contributor to Committer / PMC
-
-<!-- Knowledge type: Rules and conventions -->
-<!-- Applicable scenario: Promotion to Committer / PMC -->
-
-There are no strict quantitative criteria for becoming a Committer or PMC
Member. The PMC weighs a contributor's performance across the following areas:
-
-- **Code contributions**: Continuously submit high-quality PRs and participate
in the development of core modules.
-- **Code Review**: Actively review other people's PRs and help improve the
code quality of the community.
-- **Community participation**: Answer user questions on the mailing list,
Issues, and Slack, and take part in design discussions.
-- **Documentation and evangelism**: Write documentation and blog posts, and
share Doris at conferences.
-- **Influence**: Independently drive the evolution of important features or
modules.
-
-For detailed promotion criteria, refer to the Apache Doris official Wiki:
[Guidance for committer
promotion](https://cwiki.apache.org/confluence/display/DORIS/Guidance+for+committer+promotion).
diff --git a/community/how-to-contribute/pull-request.md
b/community/how-to-contribute/pull-request.md
index eef36a408d2..2542270bee9 100644
--- a/community/how-to-contribute/pull-request.md
+++ b/community/how-to-contribute/pull-request.md
@@ -1,5 +1,5 @@
---
-title: Code Submission Guide (Pull Request)
+title: Pull Request
language: en
description: "Complete workflow for submitting an Apache Doris Pull Request:
fork, branch, resolve conflicts, and submit the PR."
keywords:
diff --git a/community/join-community.md b/community/join-community.md
index 8c6b7eae245..c5224b223ee 100644
--- a/community/join-community.md
+++ b/community/join-community.md
@@ -1,5 +1,5 @@
---
-title: Join the Apache Doris Community
+title: Join the Community
language: en
description: "How to join the Apache Doris community: official entry points
and links for Slack, GitHub, mailing lists, Twitter, LinkedIn, YouTube, and
Bilibili."
keywords:
@@ -38,6 +38,12 @@ under the License.
[Apache Doris](https://github.com/apache/doris) is an open source real-time
data warehouse project maintained by users and developers worldwide. In June
2022, it graduated from the Apache Incubator and became an Apache Top-Level
Project (TLP). This page lists the official communication channels of the
community so that you can pick the one that best fits your habits to join
discussions and follow updates.
+:::tip Want to contribute to the community?
+
+If you want to contribute to Apache Doris through code development, content
creation, or community outreach, start with the [Community Contribution
Guide](how-to-contribute/contribute-to-doris.mdx).
+
+:::
+
## Overview of Official Community Channels
The purpose and use case of each channel is as follows:
@@ -57,7 +63,7 @@ The purpose and use case of each channel is as follows:
<!-- Knowledge type: Scenario routing -->
- **To ask quick questions or join daily discussions**: join
[Slack](https://doris.apache.org/slack).
-- **To report bugs or submit code**: visit
[GitHub](https://github.com/apache/doris), and refer to [Feedback](feedback)
and the [Contributor Guide](how-to-contribute/contributor-guide).
+- **To report bugs or submit code**: visit
[GitHub](https://github.com/apache/doris), and refer to [Feedback](feedback)
and the [Community Contribution
Guide](how-to-contribute/contribute-to-doris.mdx).
- **To follow community decisions and release announcements**: [subscribe to
the mailing list](subscribe-mail-list).
- **To see user cases and technical insights**: follow
[Twitter](https://twitter.com/doris_apache) and
[LinkedIn](https://www.linkedin.com/company/doris-apache/).
- **To watch Meetup and technical sharing recordings**: visit
[YouTube](https://www.youtube.com/hashtag/apachedoris) or
[Bilibili](https://space.bilibili.com/362350065).
diff --git a/community/security.md b/community/security.md
index 14efd4c1355..733a00fa6db 100644
--- a/community/security.md
+++ b/community/security.md
@@ -1,5 +1,5 @@
---
-title: Apache Doris Security Vulnerability Disclosure
+title: Security Vulnerability Disclosure
language: en
description: "How to report security vulnerabilities to Apache Doris: contact
the ASF Security Team via [email protected] and follow the official
responsible disclosure process."
keywords:
diff --git a/community/subscribe-mail-list.md b/community/subscribe-mail-list.md
index cddfe109de3..83d6b71565a 100644
--- a/community/subscribe-mail-list.md
+++ b/community/subscribe-mail-list.md
@@ -1,5 +1,5 @@
---
-title: Subscribe to the Apache Doris Mailing List
+title: Subscribe to Mailing List
language: en
description: Complete your Apache Doris dev mailing list subscription in 5
steps. Includes a confirmation email example, how to start a discussion, and
the unsubscribe address.
keywords:
diff --git a/community/team.md b/community/team.md
index 6d8ee458aa5..27cd7ae76f8 100644
--- a/community/team.md
+++ b/community/team.md
@@ -1,5 +1,5 @@
---
-title: Apache Doris Team and Community Roles
+title: Team and Community Roles
language: en
description: Introduction to Apache Doris community roles (PMC / Committer /
Contributor), with entry points to the official Apache members list and the
contributor list.
keywords:
@@ -46,7 +46,7 @@ Apache Doris is developed and maintained by contributors
distributed around the
| **Committer** | Active contributors with commit access to the code
repository, responsible for reviewing and merging code, documentation, issues,
and PRs |
| **Contributor** | All contributors who participate in the community through
PRs, issues, documentation, evangelism, Q&A, and other forms of contribution |
-If you want to learn about the path from Contributor to Committer or PMC, see
the [Contributor Growth Path](how-to-contribute/contributor-guide).
+If you want to learn about the path from Contributor to Committer or PMC, see
the [Community Contribution Guide](how-to-contribute/contribute-to-doris.mdx).
## Latest Members List
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/doris-future.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/doris-future.md
deleted file mode 100644
index e3cc3581152..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/doris-future.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: 开发者成长计划
-language: zh-CN
-description: Apache Doris 新手开发者成长计划，通过 `doris-future` 标签任务由导师带教完成首次贡献。
-keywords:
- - Apache Doris
- - 开发者成长计划
- - doris-future
- - 新手贡献
- - 导师制
- - 首次贡献
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- 知识类型: 计划介绍 -->
-<!-- 适用场景: 新手开发者首次为 Doris 贡献代码 -->
-
-## 简介
-
-Doris Future Plan 是 Apache Doris 社区面向新手开发者的成长计划，目标是让更多开发者快速上手 Doris 内核开发。社区欢迎对
OLAP、数据库内核、分布式系统有兴趣的开发者加入。
-
-## 参与方式
-
-<!-- 知识类型: 操作步骤 -->
-
-新手开发者可以按以下步骤加入：
-
-1. 打开 Doris 社区的 [GitHub Issue](https://github.com/apache/doris/issues) 页面。
-2. 筛选带有 `doris-future` 标签的任务。每个任务都会标注：
- - 所需技能（如 C++、Java）。
- - 难度等级。
-3. 在感兴趣的任务下方评论，并与对应导师沟通任务细节。
-4. 若本地缺少机器资源，社区可以提供开发机协助。
-
-如果在参与过程中遇到任何困难，请发送邮件至 `[email protected]` 描述问题，社区会尽力协助解决。
-
-## 导师机制
-
-<!-- 知识类型: 规则规范 -->
-
-每个 `doris-future` 任务都会安排导师跟进，导师提供的支持包括：
-
-| 支持项 | 说明 |
-|--------|------|
-| 任务讲解 | 介绍任务的目标、背景原理与实现细节 |
-| 思路引导 | 给出具体实现思路以及相关知识点 |
-| 代码 Review | 评审代码并提出优化建议，提升工程代码水平 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/feedback.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/feedback.md
index 67e742969d3..1b2aef6fc49 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/feedback.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/feedback.md
@@ -1,5 +1,5 @@
---
-title: 向 Apache Doris 反馈问题
+title: 反馈问题
language: zh-CN
description: 向 Apache Doris 反馈 Bug 或建议的官方渠道：邮件列表与 GitHub Issue，附高质量问题反馈的写作要点。
keywords:
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-doc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-doc.md
index 0072252f6fb..d39369d5652 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-doc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-doc.md
@@ -40,7 +40,7 @@ under the License.
PR 提交流程还可以参考：
-- [为 Doris 做贡献](./contribute-to-doris)
+- [Apache Doris 社区参与指南](./contribute-to-doris.mdx)
- [代码提交指南](./pull-request)
:::
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.md
deleted file mode 100644
index 491273793de..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: 贡献 Apache Doris
-language: zh-CN
-description: 如何为 Apache Doris 贡献代码、文档与 Bug 修复，社区贡献入门总览。
-keywords:
- - Apache Doris
- - 贡献代码
- - 贡献文档
- - 提交 PR
- - Bug 修复
- - 社区参与
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<!-- 知识类型: 概述 -->
-<!-- 适用场景: 初次了解如何为 Apache Doris 做贡献 -->
-
-非常感谢您对 Apache Doris 项目感兴趣。社区欢迎您以任何形式参与，包括建议、意见（含批评）、评论以及代码与文档贡献。
-
-参与 Doris
项目的方式有很多种：代码实现、测试编写、流程工具改进、文档完善等。任何贡献都会被认可，社区会将您加入贡献者列表。当贡献积累到一定程度后，您还有机会成为
Apache Committer，获得 Apache 邮箱并被收录到 [Apache Committer
列表](http://people.apache.org/committer-index.html)。
-
-任何问题都可以通过下列渠道联系社区：微信、Slack、邮件列表，社区会及时解答。
-
-## 初次接触
-
-<!-- 知识类型: 操作步骤 -->
-
-初次来到 Doris 社区，建议按以下方式建立联系：
-
-1. 关注 Doris [GitHub 代码库](https://github.com/apache/doris)。
-2. 订阅 [邮件列表](../subscribe-mail-list)，了解开发动态。
-3. 加入 Doris 微信群（添加微信号 `morningman-cmy`，备注「加入 Doris 群」）。
-4. 加入 Doris [Slack](https://doris.apache.org/slack) 频道。
-
-通过以上渠道，您可以及时跟进 Doris 开发动态，并就关注的话题发表意见。
-
-## Doris 的代码与文档
-
-<!-- 知识类型: 项目结构 -->
-
-如 [GitHub](https://github.com/apache/doris) 仓库所示，Apache Doris 的核心代码库主要包含
Frontend (FE)、Backend (BE) 和 Broker（用于读取 HDFS 等外部存储）。文档包括官方网站、GitHub Wiki
以及运行时在线帮助手册。各组件详情如下：
-
-| 组件名称 | 组件描述 | 相关语言 |
-|---------|---------|---------|
-| [Frontend daemon (FE)](https://github.com/apache/doris) | 由查询协调器与元数据管理器组成 |
Java |
-| [Backend daemon (BE)](https://github.com/apache/doris) | 负责数据存储与查询片段执行 | C++
|
-| [Broker](https://github.com/apache/doris) | 读取 HDFS 数据到 Doris | Java |
-| [Website](https://github.com/apache/doris-website) | Doris 官方网站 | Markdown |
-| [Manager](https://github.com/apache/doris-manager) | Doris Manager | Java |
-| [Flink Connector](https://github.com/apache/doris-flink-connector) | Doris
Flink Connector | Java |
-| [Spark Connector](https://github.com/apache/doris-spark-connector) | Doris
Spark Connector | Java |
-| Doris 运行时 Help 文档 | 运行 Doris 时的在线帮助手册 | Markdown |
-
-## 改进文档
-
-文档是了解 Apache Doris 最主要的入口，也是社区最需要帮助的方向之一。
-
-浏览文档可以加深对 Doris 的理解，覆盖功能与技术细节。如果发现文档有问题，请联系社区。
-
-如果您希望改进文档质量（包括修订页面地址、更正链接、撰写更优秀的入门文档），社区都非常欢迎。
-
-Doris 文档大多以 Markdown 编写，可以直接在
[apache/doris-website](https://github.com/apache/doris-website) 仓库中提交变更。相关指南如下：
-
-- 提交文档变更，请参阅
[文档贡献指南](https://doris.apache.org/zh-CN/community/how-to-contribute/contribute-doc)。
-- 提交代码变更，请参阅
[代码提交指南](https://doris.apache.org/zh-CN/community/how-to-contribute/pull-request)。
-
-## 发现 Bug 或问题
-
-<!-- 适用场景: 报告 Bug / 修复问题 -->
-
-如果发现 Bug 或问题，处理方式有两种：
-
-1. **报告问题**：通过 GitHub
[Issues](https://github.com/apache/doris/issues/new/choose) 提交新的
Issue，社区会有同学定期处理。
-2. **自行修复**：阅读并分析源码自行修复，然后提交 [Pull Request](./pull-request)。
-
-> 提示：开始修复前，建议先与社区交流，确认是否已有人在处理同样的问题。
-
-## 修改代码并提交 PR
-
-<!-- 知识类型: 操作步骤 -->
-
-参与代码贡献的基本流程：
-
-1. 下载代码、编译并部署运行，确认行为是否与预期一致（可参考
[编译文档](https://doris.apache.org/zh-CN/docs/install/source-install/compilation-with-docker/)）。
-2. 在 GitHub 上 Fork `apache/doris` 仓库到自己的账号下。
-3. 为修改创建独立分支，并将原仓库添加为 `upstream`。
-4. 提交 PR。详细步骤请参考 [Pull Request 指南](./pull-request)。
-
-无论是修复 Bug 还是新增 Feature，社区都非常欢迎您的贡献。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
new file mode 100644
index 00000000000..a2b7d0b0d64
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
@@ -0,0 +1,463 @@
+---
+title: 社区参与指南
+language: zh-CN
+description: Apache Doris 社区参与指南，帮助贡献者通过代码开发、内容创作和社区布道参与社区共建。
+keywords:
+ - Apache Doris
+ - 社区参与
+ - 代码开发
+ - 内容创作
+ - 社区布道
+ - Contributor
+ - Committer
+ - PMC
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<style>{`
+.contribution-path-grid {
+ display: grid;
+ grid-template-columns: repeat(3, minmax(0, 1fr));
+ grid-template-rows: auto auto 1fr auto auto;
+ gap: 16px;
+ margin: 24px 0;
+}
+
+.contribution-path-card {
+ display: grid;
+ grid-row: span 5;
+ grid-template-rows: subgrid;
+ gap: 12px;
+ min-height: 100%;
+ padding: 20px;
+ border: 1px solid var(--ifm-color-emphasis-200);
+ border-radius: 8px;
+ background: var(--ifm-background-surface-color);
+ color: var(--ifm-font-color-base);
+ text-decoration: none;
+}
+
+.contribution-benefits-card {
+ grid-column: 1 / -1;
+ padding: 20px;
+ border: 1px solid var(--ifm-color-emphasis-200);
+ border-radius: 8px;
+ background: var(--ifm-background-surface-color);
+}
+
+.contribution-path-card:hover {
+ border-color: var(--ifm-color-primary);
+ color: var(--ifm-font-color-base);
+ text-decoration: none;
+}
+
+.contribution-path-card h3,
+.contribution-benefits-card h3 {
+ margin: 0;
+ font-size: 1.15rem;
+}
+
+.contribution-path-card p,
+.contribution-benefits-card p {
+ margin: 0;
+}
+
+.contribution-path-card ul,
+.contribution-benefits-card ul {
+ margin: 0;
+ padding-left: 20px;
+}
+
+.contribution-path-card strong,
+.contribution-benefits-card strong {
+ color: var(--ifm-color-primary);
+}
+
+.contribution-benefits-list {
+ columns: 2;
+ column-gap: 32px;
+ margin-top: 12px;
+}
+
+.contribution-card-benefit {
+ align-self: start;
+}
+
+.contribution-next-step {
+ align-self: end;
+ color: var(--ifm-color-primary);
+ font-weight: 600;
+}
+
+@media (max-width: 996px) {
+ .contribution-path-grid {
+ grid-template-columns: 1fr;
+ }
+
+ .contribution-benefits-list {
+ columns: 1;
+ }
+}
+`}</style>
+
+Apache Doris 欢迎全球开发者、用户、技术作者、讲师和社区组织者参与共建。你可以通过代码开发、内容创作或社区布道参与 Apache
Doris。每一种参与方式都能帮助项目成长，也能帮助贡献者积累技术影响力、社区声誉和开源协作经验。
+
+<div className="contribution-path-grid">
+ <a className="contribution-path-card" href="?path=developer#社区参与指南">
+ <h3>代码开发</h3>
+ <p><strong>适合：</strong>希望直接参与 Doris 技术建设的贡献者。</p>
+ <ul>
+ <li>修复 Bug，开发新功能。</li>
+ <li>优化性能、稳定性或可观测性。</li>
+ <li>补充单元测试、回归测试和集成测试。</li>
+ <li>改进构建、CI、发布、开发工具和工程效率。</li>
+ <li>Review PR，补充技术文档、用户文档或示例。</li>
+ </ul>
+ <p className="contribution-card-benefit"><strong>贡献一经合入，你会自动成为 Apache
Doris 的 Contributor。</strong></p>
+ <span className="contribution-next-step">阅读指南 -></span>
+ </a>
+ <a className="contribution-path-card" href="?path=content#社区参与指南">
+ <h3>内容创作</h3>
+ <p><strong>适合：</strong>熟悉 Doris 使用场景，愿意分享实践经验的贡献者。</p>
+ <ul>
+ <li>撰写技术博客和生产环境案例。</li>
+ <li>编写入门教程和最佳实践。</li>
+ <li>录制功能演示、安装部署、调优排障等视频。</li>
+ <li>参与 meetup、webinar、conference 演讲。</li>
+ <li>翻译文档、博客、活动材料或视频字幕。</li>
+ </ul>
+ <p
className="contribution-card-benefit"><strong>优秀创作内容将会获得社区周边纪念品。</strong></p>
+ <span className="contribution-next-step">阅读指南 -></span>
+ </a>
+ <a className="contribution-path-card" href="?path=community#社区参与指南">
+ <h3>社区布道</h3>
+ <p><strong>适合：</strong>熟悉用户场景，擅长沟通协作的贡献者。</p>
+ <ul>
+ <li>在 Slack、GitHub、mailing list 中回答问题。</li>
+ <li>帮助新用户找到正确的文档、示例和社区入口。</li>
+ <li>组织线上或线下 meetup、workshop、office hour 或用户分享。</li>
+ <li>邀请用户分享生产实践和迁移经验。</li>
+ <li>收集用户反馈，并引导到公开渠道沉淀。</li>
+ </ul>
+ <p
className="contribution-card-benefit"><strong>活跃参与者将会获得社区周边纪念品。</strong></p>
+ <span className="contribution-next-step">阅读指南 -></span>
+ </a>
+ <div className="contribution-benefits-card">
+ <h3>权利与收益</h3>
+ <p>根据贡献类型、贡献质量和持续性，贡献者可能获得以下权益：</p>
+ <ul className="contribution-benefits-list">
+ <li>在 Apache Doris 社区渠道获得公开认可。</li>
+ <li>被纳入贡献者列表、社区鸣谢或活动 recap。</li>
+ <li>在 Apache Doris 官方网站、博客、社交媒体或视频渠道发布内容。</li>
+ <li>获得社区活动演讲机会。</li>
+ <li>与 Maintainer、Committer、PMC member 和其他资深用户进行更深入的技术交流。</li>
+ <li>优先参与部分社区活动、meetup、webinar 或 conference 议题。</li>
+ <li>通过开源贡献积累公开技术声誉和个人影响力。</li>
+ <li>获得社区周边、纪念品或特别礼品。</li>
+ </ul>
+ <p>对于长期、稳定、高质量参与技术贡献的成员，社区会根据 Apache 治理流程，邀请其成为 <strong>Apache Doris
Committer 或 PMC member</strong>。Doris Summit 每年也会评选 <strong>Outstanding
Community Hero</strong>，感谢为社区做出突出贡献的用户、开发者和布道师。</p>
+ </div>
+</div>
+
+## 社区参与指南
+
+根据不同的参与路径，社区提供了对应的参与指南。
+
+:::tip 提示
+指南内容可能会随社区流程调整而变化。欢迎加入 [Apache Doris Slack 社群](https://doris.apache.org/slack)
获取实时动态。
+:::
+
+<Tabs groupId="contribution-path" queryString="path">
+<TabItem value="developer" label="代码开发参与指南" default>
+
+### 在哪里领取任务
+
+贡献者可以从以下渠道寻找任务：
+
+- Slack：直接询问或发起讨论、确认上下文和找到合适的沟通对象。
+- [Apache Doris GitHub Issues](https://github.com/apache/doris/issues)：适合查找
Bug、Feature Request、优化建议和待处理问题。
+- [Apache Doris GitHub
Discussions](https://github.com/apache/doris/discussions)：适合参与技术讨论、使用讨论和方案讨论。
+- Roadmap：适合寻找中长期技术方向，通常可以在 GitHub Issue 页面的置顶 Issue 中查看。
+- 现有 PR：适合参与 Review、补充测试、验证问题或帮助推进合入。
+
+新贡献者可以优先从小范围任务开始，例如修正文档、补充测试、修复简单 Bug、复现 Issue、完善错误信息或优化示例。对于较大的功能或行为变更，建议先在
Apache Doris Slack 的 `#dev` 频道中发起讨论，寻求 Core Maintainers 的帮助。
+
+### 提交代码的规范
+
+提交代码前，贡献者应尽量做到：
+
+- Fork `apache/doris` 仓库，并基于最新主分支创建独立开发分支。
+- 每个 PR 聚焦一个明确问题，避免把多个无关修改放在同一个 PR 中。
+- PR 标题和描述清楚说明修改目的、影响范围和验证方式。
+- 关联对应的 Issue、Discussion 或 mailing list 讨论。
+- 补充必要的单元测试、回归测试或手工验证步骤。
+- 如果变更影响用户行为、配置、SQL 语义、错误信息或兼容性，需要同步更新文档。
+- 如果存在兼容性风险、性能风险或行为变化，需要在 PR 描述中明确说明。
+
+一个高质量 PR 通常应该包含：
+
+- 背景：为什么需要这个修改。
+- 方案：具体改了什么，为什么这样改。
+- 测试：执行了哪些测试，结果是什么。
+- 风险：是否影响兼容性、性能、稳定性或用户行为。
+- 文档：是否需要更新文档，已经在哪里更新。
+
+社区鼓励使用 AI 辅助编码、调试和 Review，但请遵循以下准则：
+
+- 使用能力较强的模型进行开发、调试和 Review，避免使用低质量模型生成关键代码。
+- 开发者要对代码负最终责任。社区不接受完全由 AI 提交且无人负责的代码。
+
+### 代码合入的标准流程
+
+代码合入通常会经过以下步骤：
+
+1. 贡献者提交 Pull Request。
+2. 具有 Committer 身份或更高权限的社区成员触发 CI 和 AI Review。你可以在 Slack `#dev` 频道寻求帮助。
+3. 贡献者根据 CI 和 Review 结果修复编译、测试或格式问题。AI 反馈也需要作为 Review
流程的一部分处理。对于合理建议，应修改代码；对于不适用的建议，应在 PR 中说明原因。
+4. 必要时，贡献者需要 rebase 最新主分支并解决冲突。
+5. Required CI checks 全部通过。
+6. Reviewer 给出 approval。
+7. Committer 完成最终合入。
+
+CI 中 required checks 必须通过后，PR 才能进入合入阶段。非 required checks 不阻塞合入。
+
+### 如何推进 Review
+
+贡献者应主动推动自己的 PR，而不是只等待 Reviewer 处理。Apache Doris 官方贡献者指南也鼓励贡献者担任自己 PR 的
Moderator，负责推动 PR 从提交到合入。
+
+推荐做法包括：
+
+- 在 PR 描述中提供足够上下文，降低 Reviewer 理解成本。
+- 在 Slack `#dev` 频道发布 PR 链接寻求 Reviewer。
+- 及时回复 Review 评论。
+- 对已经修改的问题标记为 resolved。
+- 对有争议的问题给出技术理由，而不是只表达结论。
+- 定期同步最新主分支，避免长期冲突。
+- 如果 PR 长时间没有进展，可以礼貌地在 PR 中 ping 相关 Reviewer。
+- 如果不确定谁适合 Review，可以在 Slack 中请求帮助定位模块负责人。
+
+寻找合适 Reviewer 的方式包括：
+
+- 查看同一模块最近合入的 PR。
+- 查看相关文件的历史提交记录。
+- 查看 GitHub 推荐 Reviewer 或 CODEOWNERS（如适用）。
+- 在 Slack 中请求帮助定位合适的 Reviewer，但重要技术结论应回到 GitHub 或 mailing list 中沉淀。
+
+</TabItem>
+<TabItem value="content" label="内容创作参与指南">
+
+### 可以提交哪些内容，在哪里提交
+
+#### 博客
+
+适合内容包括：
+
+- Doris 功能深度解析。
+- 查询优化、导入优化、运维调优实践。
+- Lakehouse、实时数仓、日志分析、用户行为分析等场景实践。
+- 从 Elasticsearch、ClickHouse、Hive、Trino 等系统迁移到 Doris 的经验。
+- 生产环境问题排查和性能优化复盘。
+- 新版本能力解读和使用建议。
+
+提交方式：
+
+- 在 Slack `#dev` 频道发起讨论沟通。
+- 将 Markdown 文件提交到 `apache/doris-website` 仓库的 `/blog` 目录。必要时，可以寻求 Doris
Maintainer 的帮助。
+
+#### 案例
+
+适合内容包括：
+
+- 公司或团队的业务背景。
+- 为什么选择 Apache Doris。
+- 系统架构和数据链路。
+- 数据规模、查询模式和性能目标。
+- 迁移或落地过程中遇到的问题。
+- 上线后的效果、收益和经验。
+
+提交方式：
+
+- 如果涉及公司名称、业务数据或架构图，需要先完成公司内部审批，或自行隐去敏感信息。
+- 在 Slack `#dev` 频道发起讨论沟通。社区可协助润色、翻译或发布。
+
+#### 教程
+
+适合内容包括：
+
+- 快速上手。
+- 部署和升级。
+- 数据导入。
+- 查询调优。
+- 物化视图使用。
+- 倒排索引使用。
+- 存算分离实践。
+- 湖仓查询实践。
+- 日志分析和可观测性场景。
+
+提交方式：
+
+- 在 Slack `#dev` 频道发起讨论沟通。
+- 通用、长期有效的内容适合提交到官方文档。
+- 偏实践、场景化、版本相关的内容适合提交为 blog。
+- 示例代码、脚本和配置应尽量保证可复现。
+
+#### 视频
+
+适合内容包括：
+
+- 1 到 5 分钟功能演示。
+- 安装部署 walkthrough。
+- 最佳实践讲解。
+- 场景化 demo。
+- Meetup 或 webinar 录像。
+- 用户访谈或案例分享。
+
+提交方式：
+
+- 在 Slack `#dev` 频道发起讨论沟通。
+- 先通过社区渠道确认选题、讲稿或大纲。
+- 完成后可由社区协助发布到 YouTube、Bilibili 或其他官方视频渠道。
+- 如果视频包含公司名称、客户名称、性能数据或内部系统截图，需要提前确认授权或自行隐去敏感信息。
+
+#### 演讲
+
+适合形式包括：
+
+- Meetup 分享。
+- Webinar 分享。
+- Conference talk。
+- Release feature introduction。
+- Contributor onboarding session。
+- User story session。
+
+提交方式：
+
+- 在 Slack `#dev` 频道发起讨论沟通。
+- 向社区提交议题、摘要、目标受众、语言、预计时长和讲师信息。
+- 社区可协助做议题打磨、技术校对、宣传和报名页面支持。必要时，也可以提供资金、场地等支持。
+
+#### 翻译
+
+适合内容包括：
+
+- 官方文档翻译。
+- 博客翻译。
+- 活动 recap 翻译。
+- 视频字幕翻译。
+- 教程和最佳实践翻译。
+
+提交方式：
+
+- 文档类翻译可以通过 `apache/doris-website` 提交 PR。
+- 博客或活动内容翻译可以先与社区确认目标页面和发布渠道。
+- 翻译应保留技术准确性，不应为了营销表达改变原意。
+
+### 内容完成后的发布渠道
+
+根据内容类型和审核结果，内容可以发布到：
+
+- Apache Doris 官方网站。
+- Apache Doris 官方博客。
+- Apache Doris Medium。
+- Apache Doris YouTube。
+- Apache Doris LinkedIn。
+- Apache Doris X/Twitter。
+- Apache Doris Slack。
+- 社区 newsletter、活动 recap 或版本专题页面。
+
+内容发布前通常需要完成技术准确性 Review。涉及性能数据、商业案例、客户名称或公司信息的内容，还需要完成授权确认。
+
+</TabItem>
+<TabItem value="community" label="社区布道参与指南">
+
+### 可以参与哪些形式的活动
+
+社区贡献者可以参与或组织以下活动：
+
+- Online meetup：面向全球用户的线上主题分享。
+- Offline meetup：面向特定城市或区域的线下交流。
+- Webinar：围绕具体功能、场景或版本能力做线上讲解。
+- Workshop：带用户完成部署、导入、调优或案例实践。
+- Office hour：定期开放答疑，帮助用户解决使用问题。
+- User story session：邀请真实用户分享生产环境实践。
+- Release introduction：围绕新版本介绍重点功能和升级建议。
+- Contributor onboarding：帮助新贡献者理解代码、流程和社区协作方式。
+- Local community event：面向特定语言或区域用户的本地化活动。
+- Hackathon 或 contribution sprint：围绕 Issue、文档、测试或工具集中贡献。
+
+### 如何发起活动
+
+活动发起人应准备以下信息：
+
+- 活动主题。
+- 目标受众。
+- 活动形式。
+- 活动语言。
+- 时间和时区。
+- 讲师或主持人。
+- 预计时长。
+- 需要社区提供的支持。
+- 宣传计划。
+- 活动后是否产出 slides、录像、博客或 recap。
+
+建议先在 Slack `#dev` 频道发起讨论。这样可以让更多成员参与，也符合 Apache 社区公开透明的协作方式。
+
+### 社区可以提供哪些支持
+
+根据活动类型、活动质量和社区资源情况，社区可以提供以下支持：
+
+- 官方媒体渠道宣传。
+- 活动议题策划。
+- 讲师推荐。
+- Slides 或 demo 技术 Review。
+- 报名页或活动页支持。
+- 活动录像和回放分发。
+- 社交媒体传播。
+- 社区周边支持。
+- 有限的活动预算支持，例如场地、物料、茶歇或基础运营费用。
+- 活动后 recap 发布支持。
+
+关于资金、礼品、差旅、场地和赞助支持，可与社区共同协商。活动发起人需要提前说明预算用途、预期效果和交付内容。
+
+</TabItem>
+</Tabs>
+
+## 社区行为准则
+
+所有贡献者都应遵守以下原则：
+
+- 尊重他人，保持专业、友善、建设性的沟通方式。
+- 重要技术讨论和社区决策应尽量在公开渠道进行。
+- 对代码 Review、文档 Review 和内容 Review 保持开放态度。
+- 如果不同意 Review 意见，应给出清晰的技术理由。
+- 避免在私下完成本应公开讨论的社区决策。
+- 提交原创内容，或为引用内容明确标注来源。
+- 避免夸大、无法验证或带有误导性的性能和商业表述。
+- 代码变更应尽量补充测试。
+- 用户可见行为变化应同步更新文档。
+- 不公开用户隐私、客户敏感信息和公司机密。
+- 安全问题应遵循负责任披露流程，不应在公开渠道提前披露细节。
+- 尊重 Apache 社区价值观和 ASF Code of Conduct。
+
+贡献者以开源社区成员身份参与协作。如果贡献者代表公司参与某些活动，建议在必要时说明公司背景，但具体贡献仍应遵循 Apache
社区公开、透明、基于贡献的协作方式。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contributor-guide.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contributor-guide.md
deleted file mode 100644
index 45831bdfb91..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contributor-guide.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: 贡献者成长路径
-language: zh-CN
-description: Apache Doris 贡献者成长路径：从 Contributor 到 Committer / PMC 的标准、Code
Review 与 PR 规则。
-keywords:
- - Apache Doris
- - Contributor
- - Committer
- - PMC
- - Code Review
- - Pull Request 规则
- - 社区角色
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# 贡献者成长路径
-
-<!-- 知识类型: 规则规范 -->
-<!-- 适用场景: 了解社区角色 / Code Review / PR 合入规则 -->
-
-本文介绍 Apache Doris 社区的角色划分，以及从 Contributor 一路成长为 Committer、PMC 的路径。
-
-## 社区角色
-
-在 Apache 项目中，开发者有三种角色：
-
-| 角色 | 定义 | 产生方式 |
-|------|------|---------|
-| **Contributor** | 代码正式合入代码库后，开发者自动成为该项目的 Contributor | 提交代码并合入 |
-| **Committer** | 拥有代码仓库的合入权限 | 由 PMC（项目管理委员会）经过投票推举产生 |
-| **PMC Member** | 项目管理委员会成员，对项目重大决策（如版本发布等）有投票权 | 由 PMC 经过投票推举产生 |
-
-不同角色拥有不同的权利和义务，但晋升并没有严格的量化条件，更看重在社区的持续投入与影响力。
-
-## Contributor 新人指南
-
-### 订阅公共邮件列表
-
-<!-- 知识类型: 操作步骤 -->
-
-请订阅 `[email protected]` 与 `[email protected]` 邮件列表，通过分别发送邮件到
`[email protected]`、`[email protected]` 完成订阅。
-
-`commits` 邮件列表非常重要，因为所有的 GitHub Issue、PR 提交都会自动发往该列表。
-
-订阅步骤详见 [订阅邮件列表](../subscribe-mail-list)。
-
-## Code Review 指南
-
-<!-- 知识类型: 规则规范 -->
-<!-- 适用场景: 进行 Code Review -->
-
-1. 始终保持较高的标准来进行 Review，这样才能更好地保证整个产品的质量。
-
-2. 对于用户接口类、整体架构方面的修改，需要在社区进行充分地讨论，可以在邮件组发起，也可以在 Issue 上发起。用户接口的改变包括支持新的 SQL
函数、支持新的 HTTP 接口、支持新的功能等。这样能够保证产品的一致性。
-
-3. **测试覆盖**：新增的逻辑需要有对应的测试来覆盖。对于已有老代码不好增加测试的可以酌情考虑。
-
-4. **文档**：新增加的功能必须要有文档来说明，否则不允许合入。必须要有英文文档，最好同时有中文文档。
-
-5. **代码可读性**：如果 Reviewer 对代码逻辑不清晰，可以要求 Contributor 解释这段逻辑，并在代码里写充分的注释。
-
-6. 尽量在评论的结尾给出明确的结论：是同意，还是要 change request。如果是小问题，可以只留评论。
-
-7. 如果你已经看过了代码，觉得没有问题，但希望其他同学再确认下，可以留下 `+1 Comment`。
-
-8. 互相尊重，互相学习。在评论时保持礼貌口吻，提建议尽量给出理由。
-
-## Pull Request 指南
-
-<!-- 知识类型: 规则规范 -->
-<!-- 适用场景: 提交 PR / 推动 PR 合入 -->
-
-### PR 涉及的三种角色
-
-一个 PR 合入需要三种角色的参与：
-
-| 角色 | 职责 |
-|------|------|
-| **Contributor** | PR 的提交者 |
-| **Reviewer** | 对 PR 进行代码级评论的人 |
-| **Moderator** | PR 合入的协调者，负责给 PR 设定相关标签、推动 Reviewer 评论、推动作者修改、合入 PR 等 |
-
-在一个具体的 PR 中，一个人可能充当不同的角色，比如 Contributor 自己提交的 PR，既是 Contributor，又是这个 PR 的
Moderator。
-
-### PR 合入规则
-
-| 规则 | 要求 |
-|------|------|
-| 普通 PR 最低 `+1` 数 | 至少 1 个**非作者外的 Committer `+1`** |
-| 接口类、整体架构修改的最低 `+1` 数 | 至少 **3 个 `+1`** |
-| 首个 `+1` 后等待时间 | **至少一个工作日**，等待社区其他同学 Review |
-| 回归测试 | **必须全部通过** |
-| 评论回复 | Moderator 需确认所有评论都已回复 |
-| 合入方式 | 统一使用 **「Squash and merge」** |
-
-### PR 协作要点
-
-1. Contributor 可以把一个 PR 分配给自己作为整个 PR 的 Moderator，负责后续 PR 的推动工作。分配给自己之后，其他的
Contributor 就知道这个 PR 有相关人负责了。
-
-2. **鼓励 Contributor 作为自己 PR 的 Moderator**。
-
-3. Reviewer 需要进行代码级的 Review，可参考上文的 Code Review 指南。
-
-4. Reviewer 一旦评论了某个 PR 之后，需要持续跟进这个 PR 的后续改动，不鼓励评论了之后就不再管 Contributor 的后续回复。
-
-5. 当不同的 Reviewer 对一个修改有争议时，可以尝试讨论解决。如果讨论没有办法解决，可以在 `[email protected]`
中发邮件投票解决，采取少数服从多数的原则。
-
-### 新增外部依赖的准入检查
-
-<!-- 知识类型: 规则规范 -->
-
-**新增外部依赖时要格外谨慎**。在引入新库前，需要回答以下问题：
-
-- 新增的外部库提供了什么功能？现有的库能否提供此功能（可能需要一些努力）？
-- 外部库是否由活跃的贡献者社区维护？
-- 新增库的许可条款是什么？
-- 是否将库添加到基础模块？这将影响 Doris 代码库的其他部分。以 Java
为例，如果新库引入了大量传递依赖项，那么可能会遇到类冲突的意外问题，这些问题很难通过测试发现，因为这取决于运行时加载库的顺序。
-
-## 从 Contributor 到 Committer / PMC
-
-<!-- 知识类型: 规则规范 -->
-<!-- 适用场景: 晋升 Committer / PMC -->
-
-成为 Committer 或 PMC Member 并没有严格的量化条件，PMC 会综合考量贡献者在以下方面的表现：
-
-- **代码贡献**：持续提交高质量的 PR，参与核心模块的开发。
-- **Code Review**：积极参与他人 PR 的 Review，帮助提升社区代码质量。
-- **社区参与**：在邮件列表、Issue、Slack 上回答用户问题，参与设计讨论。
-- **文档与布道**：撰写文档、博客，在大会上分享 Doris。
-- **影响力**：能够独立推动重要功能或模块的演进。
-
-详细的晋升标准请参考 Apache Doris 官方 Wiki：[Guidance for committer
promotion](https://cwiki.apache.org/confluence/display/DORIS/Guidance+for+committer+promotion)。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/pull-request.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/pull-request.md
index e99f51ffd94..57f705b3137 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/pull-request.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/pull-request.md
@@ -1,5 +1,5 @@
---
-title: 代码提交指南（Pull Request）
+title: 代码提交指南
language: zh-CN
description: Apache Doris Pull Request 提交完整流程：Fork、分支、解决冲突、提交 PR。
keywords:
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/join-community.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/join-community.md
index f0d75f71507..85020be0ac3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/join-community.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/join-community.md
@@ -1,5 +1,5 @@
---
-title: 加入 Apache Doris 社区
+title: 加入社区
language: zh-CN
description: 如何加入 Apache Doris
社区：Slack、GitHub、邮件列表、Twitter、LinkedIn、YouTube、Bilibili 的官方入口与链接。
keywords:
@@ -38,6 +38,12 @@ under the License.
[Apache Doris](https://github.com/apache/doris)
是一个由全球用户与开发者共同维护的开源实时数据仓库项目，2022 年 6 月从 Apache 孵化器毕业，正式成为 Apache 顶级项目（Top-Level
Project, TLP）。本页汇总社区的官方沟通渠道，方便你按使用习惯选择最合适的方式参与讨论、获取动态。
+:::tip 想参与社区贡献？
+
+如果你希望通过代码开发、内容创作或社区布道参与 Apache Doris，请先阅读 [Community Contribution
Guide](how-to-contribute/contribute-to-doris.mdx)。
+
+:::
+
## 官方社区渠道一览
不同渠道的定位与使用场景如下：
@@ -57,7 +63,7 @@ under the License.
<!-- 知识类型: 场景分流 -->
- **想快速提问或参与日常讨论**：加入 [Slack](https://doris.apache.org/slack)。
-- **想报告 Bug 或提交代码**：访问 [GitHub](https://github.com/apache/doris)，参考
[问题反馈](feedback) 与 [贡献者指南](how-to-contribute/contributor-guide)。
+- **想报告 Bug 或提交代码**：访问 [GitHub](https://github.com/apache/doris)，参考
[问题反馈](feedback) 与 [社区参与指南](how-to-contribute/contribute-to-doris.mdx)。
- **想跟进社区决策与版本发布**：[订阅邮件列表](subscribe-mail-list)。
- **想看用户案例与技术见解**：关注 [Twitter](https://twitter.com/doris_apache) 与
[LinkedIn](https://www.linkedin.com/company/doris-apache/)。
- **想回看 Meetup 与技术分享**：访问
[YouTube](https://www.youtube.com/hashtag/apachedoris) 或
[Bilibili](https://space.bilibili.com/362350065)。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
index 76ec1d569c1..310abdb0927 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
@@ -1,5 +1,5 @@
---
-title: Apache Doris 安全漏洞披露
+title: 安全漏洞披露
language: zh-CN
description: 如何向 Apache Doris 报告安全漏洞：通过 [email protected] 联系 ASF
安全团队，遵循官方负责任披露流程。
keywords:
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/subscribe-mail-list.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/subscribe-mail-list.md
index 02835421b8b..513e67d4eab 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/subscribe-mail-list.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/subscribe-mail-list.md
@@ -1,5 +1,5 @@
---
-title: 订阅 Apache Doris 邮件列表
+title: 订阅邮件列表
language: zh-CN
description: 5 步完成 Apache Doris dev 邮件列表订阅，附确认邮件示例、发起讨论方法与退订邮件地址。
keywords:
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/team.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/team.md
index 208c53a5a72..b356646ed76 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/team.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/team.md
@@ -1,5 +1,5 @@
---
-title: Apache Doris 团队与社区角色
+title: 团队与社区角色
language: zh-CN
description: Apache Doris 社区角色（PMC / Committer / Contributor）介绍，以及 Apache
官方成员名单与贡献者列表入口。
keywords:
@@ -46,7 +46,7 @@ Apache Doris 由分布在全球各地的贡献者共同开发与维护，遵循
| **Committer** | 拥有代码仓库提交权限的活跃贡献者，负责代码、文档、Issue 与 PR 的审阅与合入 |
| **Contributor** | 通过 PR、Issue、文档、布道、答疑等方式参与社区的所有贡献者 |
-如果你希望了解从 Contributor 成长为 Committer / PMC 的路径，请参阅
[贡献者成长路径](how-to-contribute/contributor-guide)。
+如果你希望了解从 Contributor 成长为 Committer / PMC 的路径，请参阅
[社区参与指南](how-to-contribute/contribute-to-doris.mdx)。
## 最新成员名单
diff --git a/sidebarsCommunity.json b/sidebarsCommunity.json
index 82983e2c1f9..130a9eded39 100644
--- a/sidebarsCommunity.json
+++ b/sidebarsCommunity.json
@@ -17,8 +17,6 @@
"label": "How to Contribute",
"items": [
"how-to-contribute/contribute-to-doris",
- "how-to-contribute/contributor-guide",
- "doris-future",
"how-to-contribute/pull-request",
{
"type": "category",
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
