Skip to content

innersource-ambassador.md - Add experience from WellSky #757

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
spier merged 3 commits into from
Jan 10, 2025
Merged

innersource-ambassador.md - Add experience from WellSky #757

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
932e002
Update innersource-ambassador.md
rrrutledge Jan 9, 2025
13101a2
Merge branch 'main' into rrrutledge-patch-1
spier Jan 10, 2025
01e7804
Fix linter issue
spier Jan 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions patterns/1-initial/innersource-ambassador.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

## Problem

The InnerSource Program Office (ISPO) cannot be everywhere at once within a large, decentralized organization. Without localized support, the ISPO struggles to understand the unique challenges and needs of different departments or regions and cannot effectively promote InnerSource practices across the organization.
The InnerSource Program Office (ISPO) cannot be everywhere at once within a large, decentralized organization. Without localized support, the ISPO struggles to understand and/or fill the unique challenges and needs of different departments or regions and cannot effectively promote InnerSource practices across the organization.

## Story

Expand All @@ -18,8 +18,10 @@
## Context

- The organization is large and has multiple independent departments.
- The departments have separate, independent drivers of culture and workflow.
- An ISPO has been established to drive InnerSource adoption.
- There is a need for consistent and tailored InnerSource implementation across diverse teams.
- Departmental leadership is supportive of InnerSource.
- The ISPO is too small or disconnected to effectively influence change across all departments at the organization.
- Employees with a passion for collaboration and InnerSource principles are present within the organization.

## Forces
Expand All @@ -35,7 +37,11 @@

## Solutions

- Identify and recruit volunteer ambassadors from across the organization who are enthusiastic about InnerSource and ideally have experience with open source. They support InnerSource goals while maintaining their primary organizational roles.
- Identify and recruit at least one volunteer ambassador from each department in the organization.
- The ambassadors should be enthusiastic about InnerSource and ideally have experience with open source.

Check failure on line 41 in patterns/1-initial/innersource-ambassador.md

View workflow job for this annotation

GitHub Actions / lint 

Trailing spaces [Expected: 0 or 2; Actual: 1]

Check failure on line 41 in patterns/1-initial/innersource-ambassador.md

View workflow job for this annotation

GitHub Actions / lint 

Trailing spaces [Expected: 0 or 2; Actual: 1]
- Multiple ambassadors may be needed if there isn't a single person that has visibility and influence across the department to effectively advocate for and support InnerSource everywhere. People in the department can help to identify if one ambassador is sufficient or if multiple are needed.
- Ambassadors support and encourage InnerSource across the department while maintaining their primary organizational roles.
- Strive to have departmental leadership support (and even assist in identifying) the ambassador.
- Train ambassadors on InnerSource principles, tools, and the goals of the ISPO.
- Establish clear expectations for ambassadors, including acting as a liaison, promoting InnerSource practices, and providing feedback to the ISPO.
- Create incentives for the ambassors, e.g. making ambassador work part of the reward system of the organization and praising their work (refer to the pattern [Praise Participants](../2-structured/praise-participants.md)).
Expand All @@ -58,6 +64,7 @@
## Known Instances

- *SAP* has a concept called [Open Source Champions](https://community.sap.com/t5/open-source-blogs/sap-open-source-champions/ba-p/13539587) that seems related
- [WellSky](https://wellsky.com/) has the analogous concept of InnerSource Champions representing each business area of the company.

## Status

Expand All @@ -66,6 +73,7 @@
## Authors

- Sebastian Spier
- Russell Rutledge

## Acknowledgments

Expand Down
Loading