InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

[Pattern Draft] The Outreach Sandwich - Keeping contributions moving

未關閉
#537 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

:book: Type - Content Work 1-initial
主要語言
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.

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

從此 issue 中連結的 Google Doc 和 WIP Patlet 開始;將訪談筆記和現有草稿與 Outreach Sandwich 流程進行比較。完成的標準是形成一份經過審閱、可獨立使用的 pattern 草稿,其中明確說明流程、outreach 限制和圖示,並為無法存取該文件的讀者提供解決方案。

由索引模型根據 Issue 內容生成。

評估

領域
documentation
Issue 類型
文件
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。