Skip to content

Add Capital One as a Known Instance for the InnerSource Ambassador #755

Open
@spier

Description

@spier

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 #740 (comment)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    🐅 patterns-in-the-wildInnerSource patterns that were spotted in the wild. We can extract Known Instances and new patterns.

    Type

    No type

    Projects

    Status

    Waiting for Author

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions