Implement an Activity Policy
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- github
研究方向
先檢視提議的 GitHub 活動訊號與 GitHub API 的限制，接著檢查 nodejs/admin repository 目前如何維護組織成員資格。在開始工作之前，這個 issue 需要一套已決定的政策與明確的實作範圍；完成條件包括可稽核的成員資格決策日誌，以及定義好的重新加入流程。
由索引模型根據 Issue 內容生成。
描述
I'd like to recommend that we introduce an Activity Policy for organization membership to reduce the manual workload of maintaining organization membership and attempt to reduce the surface area for potential issues caused by escalated privileges.
I think we can probably be incredibly lenient in what we consider "activity". I'd consider the following "activity", in the nodejs, pkgjs, and nodejs-private orgs:
- Creating an Issue, PR, or Discussion (ex.
org:nodejs author:bnb created:>2021-01-01) - Commenting on an Issue, PR, or Discussion (ex.
org:nodejs commenter:bnb created:>2021-01-01) - Reviewing a PR (ex
org:nodejs reviewed-by:bnb created:>2021-01-01)
I would also include "reacting to an Issue, PR, or Discussion" but it doesn't seem like GitHub has an API that would surface that information. If people think of more things to check programmatically that could be added, I'm wholly onboard with that. I believe our goal should be to consume as many signals as possible, and given that we've consistently decided to centralize on GitHub I think using every available signal is a reasonable way to parse "has this person engaged with the project".
In terms of "what is the scope and approach":
- I'd recommend checking for checking the past year. I don't know of a point in history where an "active" member of the project didn't engage in some way in GitHub at one point or another within the previous 365 days.
- I'd recommend this be instant rather than moving to a temporary hold group before being released. In CommComm I pretty consistently noticed a pattern where when asked people would say yes but not return, creating an artificial inflation of the number of members despite a majority being in this limbo state.
- I'd recommend committing "decisions" in a repo, so we have an easy log that we can audit.
- This could include a snapshot of their membership, allowing us to easily reinstate that.
- I'd recommend that we take a similar approach to how some groups have implemented Emeritus, where a simple request to be re-added (perhaps after some period of renewed activity, like a week or a month?) is all that's required. Perhaps this could also be automatic.
Would love to hear thoughts on this.
- 主要語言
- JavaScript
- 星號
- 202
- 分支
- 183
- 平均合併
- 13 天 12 小時
- 30 天內合併 PR
- 2
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
nodejs/admin 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 90/100
-
tsc-agenda
難度 5/5 一週以上 新手友好度 30/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 30/100
相似的 Issue
-
bug good first issue
難度 2/5 1-3 小時 新手友好度 86/100
amponce/archive-movie-browser#354 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
saayam-for-all/webapp#1870 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
Imageomics/OpenCite#66 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 64/100
chr15m/twiiit.com#20 ·
-
documentation
難度 2/5 1-3 小時 新手友好度 88/100
antropos17/Aegis#629 ·
維護者通常 4 天內回覆