正體中文 | English
歡迎一起參與匿名網路社群 anoni.net 的文件、新聞導讀、遊戲與工具。這份說明適用於 anoni-net 組織底下沒有自己 CONTRIBUTING.md 的 repo，repo 有自己的說明時以那一份為準。
- 文件站：見 docs repo 的 CONTRIBUTING.md，翻譯認領、內容提案、來源建議與文件錯誤都有對應的 issue 表單
- 新聞導讀：見 news repo 的 README，寫稿流程在 AGENTS.md
- 社群首頁：見 www repo 的 README，頁面是
pages/底下的 Markdown，技術文章在pages/<語系>/articles/ - 檔案工作台：見 gears repo 的 README，設計與測試方式在 AGENTS.md。想要的功能也可以在工作台的「建議與回饋」留言
- 隱私推理遊戲：見 privacy-mystery repo 的 README，issue 與 PR 不寫案件的解答
- Vessel：見 vessel repo 的 README，入口網站與節點的開發、部署方式在 AGENTS.md。連不上或有建議時，也可以用 Vessel 的意見回覆
- 觀測工具：Tor 中繼節點觀測（Pulse）與 OONI 觀測涵蓋率（ASN Coverage）的開發方式、套件升級與部署，寫在各自的 README 與
AGENTS.md - 其他 repo：先讀各自的 README，再開 issue 說明想改什麼
文字照社群首頁的寫作風格規範寫，三個網站與各 repo 的說明文件共用這一份。文件站的檔名、PR 流程、翻譯，以及用 AI 協作工具時的做法，見貢獻者百科。
- 先搜尋有沒有相關的 issue，沒有就開一個，說明要改什麼、為什麼
- Fork repo，從預設分支開新的分支，只改跟主題相關的檔案
- 開 PR 並連回 issue。改動比較大時，可以先開 Draft PR 收集意見
- CI 的檢查通過、維護者審查之後合併
貢獻的內容依該 repo 的授權釋出，見各 repo 的 LICENSE 與 README 的授權說明。參與社群時請遵守行為準則。
發現安全漏洞時不要開公開的 issue，照組織的 SECURITY.md 私下回報，repo 有自己的 SECURITY.md 時以那一份為準。內容涉及受害者、個人資料或未公開的研究時，先看上傳機敏資訊流程。
日常討論在 Matrix，帳號與使用方式見社群自架服務。不方便公開討論的事項，寄信到 whisper@anoni.net（PGP 金鑰見聯絡頁）。
正體中文 | English
Contributions to the anoni.net docs, news briefings, games and tools are welcome. This guide applies to repositories in the anoni-net organisation that do not have their own CONTRIBUTING.md. Where a repository has one, that one applies.
- Docs: see CONTRIBUTING.md in the docs repository, which has issue forms for claiming translations, proposing content, suggesting sources and reporting errors
- News briefings: see the README in the news repository, with the writing workflow in AGENTS.md
- Community site: see the README in the www repository; pages are Markdown files under
pages/, with articles inpages/<locale>/articles/ - File Workbench: see the README in the gears repository, with design and testing notes in AGENTS.md. Feature requests are also welcome through "Suggestions & feedback" in the workbench
- Privacy Mysteries: see the README in the privacy-mystery repository; please keep case solutions out of issues and pull requests
- Vessel: see the README in the vessel repository, with development and deployment notes for the portal and nodes in AGENTS.md. If you can't connect or have a suggestion, you can also use feedback on the site
- Measurement tools: development, dependency upgrades and deployment for Tor Relay Watch (Pulse) and OONI Coverage (ASN Coverage) are covered in each repository's README and
AGENTS.md - Other repositories: read the README first, then open an issue describing what you would like to change
Write to the writing style on the community site, which the three sites and every repository's documentation share. File naming, the pull request process, translation and the use of AI tools on the docs site are in the contributor handbook.
- Search for a related issue, or open one explaining what you want to change and why
- Fork the repository, branch from the default branch, and keep changes to the topic at hand
- Open a pull request linked to the issue. For larger changes, a draft pull request is a good way to gather feedback early
- Changes are merged once CI passes and a maintainer has reviewed them
Contributions are released under the licence of the repository they go into; see each repository's LICENSE and the licence notes in its README. Please follow our code of conduct when taking part.
Do not open public issues about security vulnerabilities. Report them privately as described in the organisation's SECURITY.md, or the repository's own SECURITY.md where it has one. If your contribution involves victims, personal data or unpublished research, see our process for sharing sensitive material first.
Day-to-day discussion happens on Matrix; see our self-hosted services for accounts and usage. For matters not suited to public discussion, email whisper@anoni.net (PGP key on the contact page).