Skip to content

[Proposal] 30-day bilingual community governance trial / 30天双语社区治理试点 #15

Description

@mattheliu

30-day bilingual community governance trial / 30天双语社区治理试点

中文在前,English follows.

中文

这是一个非约束性提案。它不会因为发帖、开会或合并文档而自动获得对 omdsh-devoh-my-dsh、其他项目或 DeepSeek Harness 上游的决定权;涉及具体资产的规则仍须由相应控制者确认。

提案方向:

  1. 将社区定位为公共协作层,而不是单一插件市场的管理委员会;
  2. 坚持项目自治,允许多个目录、市场、发行版和 allowlist 并存;
  3. 使用 omdsh-dev/community 作为公共参与、提案、兼容协调和会议记录入口;
  4. 先运行30天可撤回试点,只设临时主持、记录、社区维护、兼容协调和安全/CoC 联系职责;
  5. 普通可逆工作保持轻量;跨项目和高影响事项要求明确授权、回避、理由、复核和日落。

双语治理草案见 Draft PR #14
#14

请重点反馈:

  • 你是否同意“社区协调、项目自治、多市场并存”?
  • 哪些共同服务最优先:新人入口、上游兼容、安全/CoC、会议/决定记录,还是其他?
  • 试点职责、30天期限和非约束边界是否足够轻量?
  • 中英文是否存在实质语义差异?

请勿在公开回复中提交漏洞、CoC 当事人信息、secret、个人数据或账号恢复细节。

English

This is a non-binding proposal. Posting, meeting, or merging documents does not create authority over omdsh-dev, oh-my-dsh, independent projects, or upstream DeepSeek Harness. Rules affecting an asset still require confirmation by that asset's controller.

The proposal would:

  1. define the community as a shared collaboration layer, not the governing committee of one plugin marketplace;
  2. preserve project autonomy and allow multiple catalogs, markets, distributions, and allowlists;
  3. use omdsh-dev/community as the public entry point for participation, proposals, compatibility coordination, and meeting records;
  4. run a reversible 30-day trial with temporary facilitation, recording, community maintenance, compatibility, and security/conduct responsibilities;
  5. keep reversible routine work lightweight while requiring explicit authority, recusal, reasons, review, and expiry for cross-project or high-impact matters.

See Draft PR #14 for the bilingual documents:
#14

Please comment on:

  • Do you support “community coordination, project autonomy, multiple markets”?
  • Which shared services should come first: newcomer entry, upstream compatibility, security/conduct, meeting/decision records, or something else?
  • Are the temporary responsibilities, 30-day limit, and non-binding boundary lightweight enough?
  • Are there material semantic differences between the Chinese and English versions?

Do not post vulnerabilities, conduct-case identities, secrets, personal data, or account-recovery details publicly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    proposalCommunity governance proposal / 社区治理提案

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions