InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Add Capital One as a Known Instance for the InnerSource Ambassador
还没有人认领这个 Issue。
- 主要语言
- 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
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 issue 中链接的 InnerSource Ambassadors 模式开始,并查看所引用的 InnerSource Flywheel 演讲以了解背景。确定是否应该列出 Capital One,因为讨论明确表示目前不应将其视为已实施的示例;done 应为一项明确的决定,以及在获批的情况下对相应模式的更新。
由索引模型根据 Issue 内容生成。
评估
- 领域
- documentation
- Issue 类型
- 文档
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100