Skip to content

Add Aerospace Corporation as Known Instance for InnerSource Hackathon#899

Open
rrrutledge wants to merge 6 commits intoInnerSourceCommons:mainfrom
rrrutledge:add-aerospace-known-instance
Open

Add Aerospace Corporation as Known Instance for InnerSource Hackathon#899
rrrutledge wants to merge 6 commits intoInnerSourceCommons:mainfrom
rrrutledge:add-aerospace-known-instance

Conversation

@rrrutledge
Copy link
Copy Markdown
Contributor

@rrrutledge rrrutledge commented Apr 6, 2026

Summary

  • Adds The Aerospace Corporation as a second Known Instance for the InnerSource Hackathon pattern
  • Enhances the pattern content to meet Level 2 (Structured) requirements:
    • Rewrite patlet to two-sentence problem/solution format
    • Restructure Solution with Preparation, Participation, and Event Format subsections
    • Add Related Patterns section (Start as an Experiment, Praise Participants, InnerSource Portal, Dedicated Community Leader, Gig Marketplace)
    • Add context about contract-based organizations
    • Fix grammar and address Vale spelling flags (upskilling -> skill development, OKRs -> objectives, curation -> preparation, kanban -> task board, deprioritizing -> putting it off, contribfest -> contribution festival)
    • Update status to Structured

About the Known Instance

The Aerospace Corporation is an FFRDC (Federally Funded Research and Development Center) where developers charge time to government contracts. This makes InnerSource adoption especially challenging — if it's not part of the funded tasking, it doesn't happen.

Their software best practices team organized a hybrid contribution festival (virtual + in-person in El Segundo, CA) with these results:

  • 31 participants across 21 departments
  • 15 tickets closed during or shortly after the event
  • A developer contributed a feature back to an internal library instead of forking it — directly solving the "fork storm" problem
  • 2/3 of participants had never heard of InnerSource before
  • 100% of survey respondents agreed InnerSource would positively impact development
  • Documentation site traffic nearly doubled in the following month

Source: Kickstarting InnerSource with a Contribfest (InnerSource Commons Summit 2024 talk by Tren Baumgarten and Caroline Jones)

Test plan

  • Verify the YouTube link resolves correctly
  • Review the Known Instance description for accuracy against the source talk
  • Verify Vale spelling/style checks pass
  • Verify markdownlint checks pass

Note: After this PR merges, #900 will move the file from 1-initial to 2-structured and add it to the Mind Map.

🤖 Generated with Claude Code

…thon

Add detailed Known Instance based on their InnerSource contribfest
presented at InnerSource Commons Summit 2024 by Tren Baumgarten and
Caroline Jones. Their experience validates the pattern in a
contract-based organization (FFRDC) with 31 participants across 21
departments, 15 tickets closed, and strong post-event engagement.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…athon pattern

Add The Aerospace Corporation as a second Known Instance based on their
InnerSource contribution festival presented at InnerSource Commons
Summit 2024 by Tren Baumgarten and Caroline Jones.

Also enhance the pattern content to meet Level 2 (Structured) requirements:
- Rewrite patlet to two-sentence problem/solution format
- Restructure Solution with Preparation, Participation, and Event Format sections
- Add Related Patterns section
- Add context about contract-based organizations
- Fix grammar and address Vale spelling issues
- Update status to Structured

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rrrutledge rrrutledge force-pushed the add-aerospace-known-instance branch from 788a7d2 to ac6b2a4 Compare April 7, 2026 02:25

* IKEA (Ingka Group)
* **IKEA** (Ingka Group)
* **The Aerospace Corporation** organized an internal InnerSource contribution festival inspired by open source contribution festivals at conferences like KubeCon/CloudNativeCon. Aerospace is a Federally Funded Research and Development Center (FFRDC) where developers charge time to government contracts, making InnerSource adoption especially challenging because work not embedded in funded tasking does not happen. The event was organized by a software best practices team and held as a hybrid event (virtual and in-person in El Segundo, California). They secured dedicated funding so that all 31 participants across 21 departments could charge their time to the event. Tasks were prepared with project maintainers, documented with clear definitions of done and impact statements, and organized on task boards. At least one maintainer from every participating project was available for Q&A throughout the day. During and shortly after the event, 15 tickets were closed. Notably, one developer used the event to contribute a feature he needed back to an internal library rather than forking it — a direct demonstration of InnerSource solving the "fork storm" problem the company had been experiencing. Two-thirds of participants had never heard of InnerSource before the event, yet 100% of survey respondents agreed that InnerSource would have a positive impact on development and wanted to participate in a future event. Traffic to the company's internal documentation site nearly doubled in the month following the event. See: [Kickstarting InnerSource with a Contribfest](https://www.youtube.com/watch?v=J5KeCHFbnWA) (InnerSource Commons Summit 2024 talk by Tren Baumgarten and Caroline Jones).
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be "Trin Baumgarten" & "Caroline T Jones"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also fix elsewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant