InnerSource Hackathon: Add Aerospace Corporation as Known Instance and other content improvements

[rrrutledge]

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

[spier]

Hey @rrrutledge. Thank you for contributing this.

Before starting the review just one question, as I got confused due to the other PRs related to this pattern that you opened and then closed.

Currently this PR here is not only adding another known instance but also reformatting and adding new content. Is this intended?

[rrrutledge]

Hi @spier, thanks for taking a look at this. Sorry for the confusion yes I did intend to do more than just add the known instance. I wanted to do everything for the pattern to be ready to move to structured so it can be published.

Hope it looks OK!

[spier]

Great job with this @rrrutledge! Will merge as is, and as some follow-ups separately.

[spier]

@rrrutledge will you create another PR to get the pattern published in the book (move to 2-structured folder, add to mindmap, ...) / similar to what you had already started and then aborted in #900?

Some questions:

• why did you opt to remove the scenario descriptions in the "Context"?
• do you want to add yourself as an author?
• should we ask Trin Baumgarten & Caroline T Jones for a review of this pattern? (always good to get more contributors)