Succession Planning for Space
Code repos, succession planning, space backups, and more
If you are into New Year resolutions, are you going to update your Successor settings?
My early career in telecom and INFOSEC taught me painful but valuable lessons about documentation and effective succession planning. Those experiences shaped my view that knowledge sharing and continuity are non-negotiable.
With that in mind: If you use a source code repository, what happens if you can no longer maintain it?
I only recently noticed a new setting made available in GitHub specifically for this. It’s worth a look.
However, depending on your trust in the longevity of any single organization, a POSSE (Publish on Own Site, Syndicate Elsewhere) approach might make more sense. I’m seeing more developers replicating or migrating entirely to alternatives to ensure redundancy.
YMMV, but if you are looking to adopt a “cockroach strategy” for your code, here are a few alternatives to consider:
- The Archives: Software Heritage
- The Community Hosts: Codeberg, Forgejo, SourceHut
I’ll leave out the discussion on the implications of AI “hoovering up” POSSE source code for now (legally murky at best ⚖️). This is strictly about succession planning and documentation. 🤓
Do you foresee your repos being placed in cislunar space? On the Moon? On Mars? Or beyond?
🚀 Space Value Chain (SVC) Related Videos
- 🌖🏗️ Vast shared Haven-1 fit test for docking
- 🚀🇮🇹 SpaceX Falcon 9 launch of Earth observation satellite Cosmo-SkyMed Second Generation Flight Model 3 (FM3) for Italy
🛸 Space Value Chain (SVC) companies and organizations
Enjoyed this post?
Consider supporting my sponsor!
🔓 Unlock Your Best Self with Lida Coaching! 50% off regular coaching rates until July 31, 2026!
A quick message from Lida:
With 18 years building, marketing, and scaling products at startups, I work with founders and leaders stuck between where they are and where they need to be. I help you cut through the noise, make sharper decisions, and get your team executing with clarity instead of chaos.
Most founders mistake complexity for strategy. They keep adding when they should be subtracting. When I'm brought in, the team is usually doing a lot right, and the real issue is focus and direction. I diagnose what's actually going wrong across product, positioning, and execution, then reset direction and get everyone aligned around one clear path forward that will lead to growth.
A bit of what I've done: I was the first PM on a fintech product that hit 10,000+ users within months, built a national incubator that supported over $500M in startup funding, and led teams at 23 Design before it was acquired by frog (the design team behind Apple’s first products). I've spoken at Google, Microsoft, and LinkedIn, etc.
🔓 Unlock Your Best Self with Lida Coaching! 50% off regular coaching rates until July 31, 2026!
