Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Resurrecting the Dead

Resurrecting the Dead

Presented on
* June 20 2025 at NeosConf, Karlsruhe, Germany.
* September 25 2025 at LoopConf, London, United Kingdom.
* June 30 2026 at DrupalCamp Belgium, Kortrijk, Belgium.

---------------------------------------------------------------

Have you ever considered what would happen when a popular open source package is abandoned ?
Now, what about when that package is one of your essential dependencies ?

This scenario is not some abstract scenario for a far away future. Projects get abandoned every day and your dependency might be next... But you can help!
Come & listen to some tales of an accidental maintainer and learn about what you can do to help try and prevent these situations from getting out of hand.

----

The image on the fourth slide is copyright Tristan Elwell and used with permission.
Prints of this image can be ordered via: https://www.inprnt.com/gallery/tristan_elwell/curses-inc/

More Decks by Juliette Reinders Folmer

Other Decks in Programming

Transcript

  1. Accidental Maintainer ? ▪ Requests with Alain Schlesser ▪ PHP

    Parallel Lint with Václav Makeš Linnaea Mallette
  2. Accidental Maintainer ? ▪ Requests with Alain Schlesser ▪ PHP

    Parallel Lint with Václav Makeš ▪ PHP_CodeSniffer ©Tristan Elwell
  3. “If something "just" works, it generally means someone in the

    background is putting a sh*tload of effort into it to keep it running smoothly. Linnaea Mallette
  4. Succession Management ▪ Document ▪ Activate ▪ Identify ▪ Coach

    ▪ Validate ▪ Promote ▪ Funding! Nicky Pe
  5. Keys to the Castle ▪ Repo ▪ GH Organisation ▪

    Packagist ▪ Access to domains/DNS ▪ Open Collective ▪ Social Media Accounts ▪ Etc George Hodan
  6. “Apparently, it is perfectly acceptable for companies and governments to

    demand that open source software used by millions complies with QA standards, security protocols etc, but it is still regarded as unseemly when the maintainers of that same software ask to be paid… Petr Kratochvil
  7. Do's ▪ Set up Funding Channels ▪ Dedicated Organisation ▪

    Contributing Guide ▪ PRs & Protected Branches ▪ Expand CI/QA ▪ Signalling via Labels ▪ Close Quickly Linnaea Mallette
  8. Struggles ▪ Slow turn-around on feedback ▪ "good enough" ▪

    Lonely ▪ I don't know everything… Michal Spisak