Community Governance Suggestions 社区治理意见

[hexWars]

• Write a CONTRIBUTING guide detailing the basic development process. You can refer to: Astro's CONTRIBUTING.md.
• Hold votes for key/priority features. Consider creating a new channel on Discord or using GitHub Discussions for voting.
• For community governance, the development team can check out Astro's GOVERNANCE.md, though it doesn't need to be as detailed.
• Consider adding a Code of Conduct. You can refer to: Contributor Covenant.
• Regularly compile and sync error reports and feature suggestions from Discord into GitHub issues.
• Before creating a PR, make sure to discuss or clarify in the original issue.
• Identify some beginner-friendly issues for PR contributions, similar to Astro’s contribution guide.
• Use some i18n plugins to make translations easier to compare, such as Astro's i18n documentation.
• All PRs should be reviewed by maintainers in the order they were submitted; later PRs should be closed.
• All issues and PRs must be discussed with the submitter before they are closed.
• If there aren’t enough members, active community contributors can be invited to become maintainers (e.g., documentation maintainers or community support members).

---

• 写一份CONTRIBUTING，把基本开发流程写了，可以参考：https://github.com/withastro/astro/blob/main/CONTRIBUTING.md
• 关键/优先的功能进行投票，可以在discord里开设一个新频道/github的讨论区投票
• 关于社区治理，开发团队可以看看https://github.com/withastro/.github/blob/main/GOVERNANCE.md
• 可以考虑添加社区准则Code of Conduct，参考：https://www.contributor-covenant.org/
• disord的错误报告和功能建议，可以固定的整理同步到github的issue
• 需要在原来的issue提下沟通，或者说明后，才能进行pr
• 给出一些容易pr的issue，类似astro社区的https://github.com/withastro/astro/contribute
• 用i18n的一些插件，不然翻译的pr要找对比半天（效果类似这种：https://i18n.docs.astro.build/）
• 所有的pr，维护者按照时间顺序审核pr，将后提交的pr关闭
• 所有的issue和pr，必须说明后才关闭，不能不作回复就关闭
• 如果成员不够 ，可以邀请贡献多的社区成员成为维护者（文档维护者/社区答疑）