Triager log/How to become a triager
未關閉
還沒有人認領這個 Issue。
topic-triage
type-feature
- 主要語言
- Python
- 星號
- 2.1k
- 分支
- 1k
- 平均合併
- 2 天 12 小時
- 30 天內合併 PR
- 12
描述
Currently we have:
- a developer log
- an how to become a core developer pages
As far as I know, there is no equivalent to the developer log for triagers, and there is a section about becoming triagers.
I think we should:
- Add a triager log (possibly generated by the file proposed in #848)
- Add a link to the "becoming a core dev" page to the "becoming triager" section, or move both to the same page
- Improve the documentation on how to become a triager, including steps such as
- making an official announcement on Discourse
- adding the new triager to the triagers team on GitHub
- reclaiming the GitHub mannequin
- join the Discord server
- Add links between the developer/triager logs and the "becoming *" section and the other way around
貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
研究方向
先閱讀 issue 中連結的 developer log、core developer 和 triaging 頁面，然後查看 #848 中提議的檔案。完成的標準是 triager log 存在、becoming-triager guidance 涵蓋列出的 onboarding 步驟，且相關頁面彼此連結。
由索引模型根據 Issue 內容生成。
評估
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100