InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Add Capital One as a Known Instance for the InnerSource Ambassador

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

還沒有人認領這個 Issue。

:tiger2: patterns-in-the-wild
主要語言
HTML
星號
853
分支
206
平均合併
1 天 23 小時
30 天內合併 PR
2

描述

pattern: InnerSource Ambassadors

@spier This does a great job at capturing all of the elements for IS ambassadors.

To answer your questions, yes it's a good description of what we are doing. Some additions I would suggest are:
a) where you say "are enthusiastic about IS", I would add "and ideally have experience using open source practices".
b) add info on 'what's in it for the ambassadors'. For example, it provides opportunity and topic for ambassadors to reach out and engage beyond their immediate teams. it provides opportunity for learning, enhancing influence, problem-solving, and communication skills, opportunity to share their expertise and passion in a structured way, and to network with like-minded enthusiasts.

re: whether Capital One is an org that has implemented the pattern:
I would not list Capital One yet. What is described in the pattern is our intent, but we are not yet an example of one that has fully implemented the pattern.

Originally posted by @sallydeering1 in https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/740#issuecomment-2575442755

For extra reference also see this talk from the ISC Summit 2024:
The InnerSource Flywheel

貢獻指南

開啟貢獻指南

從這裡開始

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

研究方向

從 issue 中連結的 InnerSource Ambassadors 模式開始,並查看所引用的 InnerSource Flywheel 演講以了解背景。釐清是否應該列出 Capital One,因為討論明確表示目前不應將其視為已實作的範例;done 應是一項明確的決定,以及在獲得核准的情況下對相應模式的更新。

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

評估

領域
documentation
Issue 類型
文件
難度
2/5
預估耗時
1-3 小時
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

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

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