We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Rescue and renew: How to get legacy open source projects unstuck

Formal Metadata

Title
Rescue and renew: How to get legacy open source projects unstuck
Alternative Title
Live: Rescue and renew a project
Title of Series
Number of Parts
33
Author
Contributors
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
How to get legacy open source projects unstuck You depend on scores of open source applications, frameworks, and libraries. One hasn't released for years. Another is struggling with a big rewrite or a difficult maintainer. How do you get a legacy OSS project unstuck? Especially if you don't already maintain it? I've done it and I'll share how. I've helped get several OSS projects unstuck. I'll share success stories (one only took 15 hours of work), and I'll discuss the 5 major ways OSS projects get stuck (strategy, team, interfacing, workflow, and money) and how to address each. And yes, a contributor who's never worked on the project before can be the catalyst that revives it or gets a long-delayed release out the door. You'll come away from this talk with steps you can take to rescue and renew OSS projects - regardless of language, framework, or platform.