OpenViking is growing into a larger open-source project. To make it easier for contributors to know where to ask questions, who reviews which area, and how to get involved, this issue serves as a maintainer map and contribution entry.

随着 OpenViking 持续发展，我们希望让贡献者更容易知道：问题该找谁、PR 由谁 review、以及如何开始参与贡献。因此，这个 issue 同时作为模块找人地图和贡献入口。

Contributor-Facing Module Map / 面向贡献者的模块地图

If you are not sure where your question, issue, or PR belongs, start with this table.

如果你还不确定你的问题、issue 或 PR 属于哪一块，可以先看这张表。

If you still cannot determine the right area, please mention one of the cross-module maintainers below.

如果你仍然无法判断该归到哪个模块，可以直接 @ 下方的跨模块维护支持成员。

Maintainer Routing Map / 面向维护者的路由表

This table is more detailed and mainly used for routing issues, PRs, and design questions.

这张表粒度更细，主要用于路由 issue、PR 和设计问题。

For areas that do not yet have a clearly assigned owner, cross-module maintainers will help route the request first.

对于尚未明确稳定 owner 的子域，先由跨模块维护支持成员协助路由。

Cross-Module Maintainers / 跨模块维护支持

• @MaojiaSheng
• @qin-ctx
• @zhoujh01

Cross-module maintainers help with issue routing, cross-cutting design questions, and fallback review support.

跨模块维护支持成员主要负责 issue 路由、跨模块设计问题，以及 owner 忙碌时的补位 review。

How To Get Help / 如何获得帮助

• If you are opening an issue, please mention the affected module if you already know it.

• If you are not sure which module it belongs to, describe the use case and affected behavior first.

• If you want to work on an issue, leave a comment before starting, especially for cross-module work.

• If your PR spans multiple areas, please call out the main affected domain in the description.

• 如果你要提 issue，且已经知道受影响模块，请在描述里写明。

• 如果你暂时无法判断模块归属，优先描述场景和受影响行为。

• 如果你想认领某个 issue，建议先留言说明，尤其是跨模块问题。

• 如果你的 PR 涉及多个模块，请在描述中明确主要影响域。

Contribution Entry / 贡献入口

We will use a few standard labels to make contribution entry clearer:

我们希望通过一组标准标签，让贡献入口更清晰：

• good first issue: newcomer-friendly tasks with clear scope and acceptance criteria

• help wanted: tasks that need contributors familiar with the codebase or review style

• needs-design: issues that need maintainer clarification before implementation

• needs-review: PRs waiting for the first review round

• good first issue：适合新贡献者的任务，范围清晰、验收标准明确

• help wanted：需要熟悉仓库或 review 风格后再参与的问题

• needs-design：需要先由维护者澄清设计边界的问题

• needs-review：等待首轮 review 的 PR

Contributor Growth Path / 贡献成长路径

We want contribution growth to be visible and practical:

我们希望贡献成长路径是可见的、可执行的：

New Contributor

• Start from good first issue

• Get familiar with the repository through small fixes, docs, tests, or scoped changes

• 从 good first issue 开始

• 通过小范围修复、文档、测试或边界清晰的改动熟悉仓库

Active Contributor

• Has one or more merged contributions

• Can start picking up help wanted issues in a familiar area

• 已经有一个或多个合入贡献

• 可以开始认领熟悉模块下的 help wanted

Module Contributor

• Contributes repeatedly in the same subarea

• Starts helping with issue triage, reproduction, docs, or review comments

• 在某个子域持续贡献

• 开始参与 issue 分流、问题复现、文档补充或 review 建议

Backup Reviewer Candidate

• Has a stable contribution record in one subarea

• Can help with first-pass review, routing, and contributor support

• 在某个子域形成持续稳定的贡献记录

• 可以参与首轮 review、问题路由和贡献者支持

Recognition & Incentives / 激励与认可

• External contributors will be credited in release notes.

• First merged PRs and high-impact community contributions can be highlighted in periodic community updates.

• Active contributors may be invited to join mentorship, issue co-ownership, or community sharing opportunities.

• We want contribution paths to be visible, so that contributors can see how they grow from first contribution to long-term collaboration.

• Instead of maintaining a "recent standout contributors" list in this issue, we prefer to recognize them in release notes or periodic community updates so the maintainer map stays stable.

• 外部贡献者会在 release notes 中获得署名感谢。

• 首次合入 PR 和有影响力的社区贡献，可以在周期性社区更新中重点致谢。

• 持续活跃的贡献者，可以优先获得 mentor 配对、issue 共管或社区分享机会。

• 我们希望把贡献路径做得更可见，让大家能明确看到从首个贡献到长期协作的成长过程。

• 相比在这个 issue 中长期维护“最近突出的贡献者”名单，我们更倾向于在 release notes 或周期性社区更新中致谢，这样模块地图本身会更稳定。

Response Expectations / 响应预期

• Issues should ideally receive a first response within 48 hours.

• PRs should ideally receive a first review within 3 days.

• If the primary contact is temporarily unavailable, a cross-module maintainer should help route or respond.

• Issue 理想情况下应在 48 小时内获得首次响应。

• PR 理想情况下应在 3 天内获得首次 review。

• 如果 primary contact 暂时无法响应，跨模块维护支持成员应协助路由或补位回复。