InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
[Pattern Draft] The Outreach Sandwich - Keeping contributions moving
还没有人认领这个 Issue。
- 主要语言
- HTML
- 星标
- 853
- 派生
- 206
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 2
描述
In a conversation @MaineC mentioned that @rrrutledge “has a way to follow up at just the right time, to remind me that I need to do something on my PR (contribution)”. Well, it turns out that this happens at the right time because there is a strict regimen behind this that Russ follows :)
I interviewed Russ about this, and captured some notes. [^1]
Now we are looking to turn these notes into a pattern. The first draft of that is already in the doc above.
WIP Patlet:
The communication on some external contributions threads to an InnerSource project are going stale, even though the contributor was motivated when starting the process. By using the outreach sandwich, a structured way to do the follow-up on all open contribution threads, the project maintainers manage to nurture more contributions to completion.
A little sketch that may help to understand the idea behind this pattern.
Don't mind the styling, GitHub does not allow all styling options for mermaid diagrams:
flowchart TD
subgraph checks [" "]
X(Start checks on regular cadence) --> A
A(Take next item from board) --> B
B("`**Progress Check**: Any updates on the contribution?`") -->|yes| A
B --> |no| C
C("`**Time Check**: Enough time since last outreach?`") --> |no| A
C --> |yes| D
D("`**History Check**: How many previous outreaches?`") --> |"0/1/2"| send_outreach
D --> |"3"| stop_outreach
end
subgraph send_outreach [Send Outreach]
OR1("`**Template**: Pick appropriate outreach approach`") --> OR2
OR2("`**Communication Method**: How to effectively reach the contributor?`") --> OR3
OR3("`**Send Outreach**`")
end
send_outreach --> A
subgraph stop_outreach ["Stop Outreach"]
ST1(Inform Contributor) --> ST2
ST2(Close issue/item)
end
stop_outreach --> A
style send_outreach fill:#edf6fb,stroke:#0aa8a7,stroke-width:2px
style stop_outreach fill:#edf6fb,stroke:#0aa8a7,stroke-width:2px
[^1]: If anybody reading this cannot access the doc, please let me know in the comments.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从此 issue 中链接的 Google Doc 和 WIP Patlet 开始;将访谈笔记和现有草稿与 Outreach Sandwich 流程进行比较。完成的标准是形成一份经过审阅、可独立使用的 pattern 草稿,其中明确说明流程、outreach 限制和图示,并为无法访问该文档的读者提供解决方案。
由索引模型根据 Issue 内容生成。
评估
- 领域
- documentation
- Issue 类型
- 文档
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100