Files
multica/apps/docs/content/docs/meta.ja.json
T
Bohan Jiangandmultica-agent f7abcdded3 docs: publish the community-maintained areas and their maintainers (#7249)
Until now, "community-maintained" appeared in the docs without ever
naming who maintains what, and the actual maintainers were recorded only
in Go package comments and PR threads. Users filing an issue had no way
to learn any of it.

Add a Community-maintained areas page in all four locales listing each
area, its code path, its maintainers, and the retirement rule, and make
that page the single source of truth: channels, the DingTalk and
Telegram guides, the README, and the three package doc comments now
point at it instead of restating it. Those package comments no longer
carry maintainer handles or a second copy of the policy, so ownership
changes are recorded in exactly one place.

The page is deliberately a credit-and-expectations page, not a support
directory — it asks readers to file a GitHub issue rather than page a
volunteer directly, since what we promised these maintainers is that we
would route work to them, not that they are on the hook for it. It also
avoids the term "code owner": we are not adding a GitHub CODEOWNERS
file, and that term carries a specific automated meaning there.

Both issue forms gain a required Area field so a report can be routed
without asking the reporter to read source, with the community-maintained
areas marked as such in the option list.

Co-authored-by: multica-agent <[email protected]>
2026-08-20 00:22:04 +08:00

62 lines
1.3 KiB
JSON

{
"title": "ドキュメント",
"pages": [
"---はじめに---",
"index",
"cloud-quickstart",
"concepts",
"how-multica-works",
"tutorial",
"self-host-quickstart",
"---ワークスペース---",
"workspaces",
"members-roles",
"---イシューとプロジェクト---",
"issues",
"projects",
"project-resources",
"---エージェント---",
"agents",
"agents-create",
"skills",
"squads",
"---日常のコラボレーション---",
"triggering-agents",
"assigning-issues",
"comments",
"mentioning-agents",
"chat",
"inbox",
"---ランタイムと実行---",
"tasks",
"daemon-runtimes",
"install-agent-runtime",
"providers",
"---自動化---",
"autopilots",
"---連携---",
"channels",
"lark-bot-integration",
"slack-bot-integration",
"dingtalk-bot-integration",
"telegram-bot-integration",
"github-integration",
"vcs-integration",
"---アプリ---",
"desktop-app",
"mobile-app",
"---セルフホスティング---",
"security-model",
"environment-variables",
"auth-setup",
"troubleshooting",
"---リファレンス---",
"cli",
"auth-tokens",
"---コミュニティ---",
"community-maintained",
"---開発に参加---",
"developers"
]
}