[Pattern Idea] Maintainer Apprentice
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 文件
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- github, markdown
研究方向
先從 issue #670 和連結的已知實例 #669 開始，接著檢視 issue 中描述的 CODEOWNERS 與自訂 repository 角色脈絡。完整的模式應完成尚未完成的 Resulting Context 區段，並清楚記錄 maintainer-apprentice 問題、取捨、解決方案與結果。
由索引模型根據 Issue 內容生成。
描述
Title
Maintainer Apprentice
Patlet / Summary
A user wants to work their way into becoming an Approver/Maintainer on an InnerSource repository while being given enough permissions to prove their contributions.
Problem
Sometimes a repository may want to "onboard" maintainers without giving them full write access. This means they are added to a repository to provide content/changes and able to "approve" other changes but not merge them. This could be a form of onboarding or internship on the way to approver or maintainer roles.
Context
From @spier in #669
...our idea with the lower section of the CODEOWNERS file was, that those folks doing the translation work might sort of be "maintainer apprentice", and through their involvement in the project become maintainers eventually
In this particular situation the user was in the CODEOWNERS file but did not have write permissions on the repository. This caused GitHub to label the CODEOWNERS file as having errors.
Forces
What could make this problem difficult?
- the permissions structure in the organization or repository is not present to solve this
Tradeoff(s):
- Knowing a "maintainer apprentice" is given enough permissions to contribute and approve but not merge changes.
Solutions
Any of the following:
- Make sure all reviewers/approvers/maintainers of repositories have write permissions
- Accepting that not all reviewers/approvers/maintainers of repositories have write permissions until earned
- Custom repository or organization roles (if the software allows it) (e.g, Custom Repository Roles)
Resulting Context
What is the situation after the problem has been solved?
The original context is changed indirectly by way of the solution.
Often this section can include discussion of the next possible Patterns/problems introduced.
This section can be short in content - the solution may not introduce new problems or change much context.
Known Instances (optional)
#669
Status
Initial
Author(s) (optional)
@spier
@jmeridth
- 主要語言
- HTML
- 星號
- 853
- 分支
- 206
- 平均合併
- 1 天 23 小時
- 30 天內合併 PR
- 2
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
InnerSourceCommons/InnerSourcePatterns 的其他 Issue
-
Monthly Metrics: Contributors 2026-09-01..2026-09-30可能已有人在做 @spier 於 1 天前認領。 未關閉community metrics
InnerSourceCommons/InnerSourcePatterns#941 · 已指派 1 人 ·
-
Monthly Metrics: New Issues + New Pull Requests 2026-09-01..2026-09-30可能已有人在做 @spier 於 1 天前認領。 未關閉community metrics
InnerSourceCommons/InnerSourcePatterns#940 · 已指派 1 人 ·
-
Monthly Metrics: Contributors 2026-08-01..2026-08-31可能重新可做 @spier 於 31 天前認領，目前沒有進行中的 PR。 未關閉community metrics
InnerSourceCommons/InnerSourcePatterns#935 · 已指派 1 人 ·
-
Monthly Metrics: New Issues + New Pull Requests 2026-08-01..2026-08-31可能重新可做 @spier 於 31 天前認領，目前沒有進行中的 PR。 未關閉community metrics
InnerSourceCommons/InnerSourcePatterns#934 · 已指派 1 人 ·
-
Monthly Metrics: Contributors 2026-07-01..2026-07-31可能重新可做 @spier 於 62 天前認領，目前沒有進行中的 PR。 未關閉community metrics
InnerSourceCommons/InnerSourcePatterns#922 · 已指派 1 人 ·
查看 InnerSourceCommons/InnerSourcePatterns 的全部 Issue
相似的 Issue
-
area:docs good first issue P3
難度 2/5 1-3 小時 新手友好度 88/100
uttrflow/uttrflow-swift#3445 ·
維護者通常 1 天內回覆
-
adr
難度 2/5 1-3 小時 新手友好度 72/100
kristofdegrave/homeassistant-smart-charging#1607 ·
維護者通常 1 天內回覆
-
Feature
難度 1/5 1 小時以內 新手友好度 65/100
Narezzurri/OpenVPN-Config-Manager#95 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
doc good first issue help wanted
難度 2/5 1-3 小時 新手友好度 68/100
collective/icalendar#1865 · 2 則留言 ·
維護者通常 1 天內回覆