InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Add Capital One as a Known Instance for the InnerSource Ambassador

Open
#755 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:tiger2: patterns-in-the-wild
Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the InnerSource Ambassadors pattern linked in the issue and review the referenced InnerSource Flywheel talk for context. Resolve whether Capital One should be listed at all, since the discussion explicitly says it should not yet be treated as an implemented example; done should be a clarified decision and corresponding pattern update, if approved.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.