Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
When an open source project has gotten stuck, how do you get it unstuck? Especially if you aren't already its maintainer? My teams have done this with several projects. A new contributor, who's never worked on a project before, can be the catalyst that revives a project or gets a long-delayed release out the door. I'll share a few case studies, principles, & gotchas. More than developer time, coordination & leadership are a bottleneck in software sustainability. You'll come away from this talk with steps you can take, in the short and long runs, to address this for projects you care about.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "How To Get A Project Unstuck" features Sumana Harihareswara, who presents strategies for revitalizing open source projects that have stalled, particularly when the person wanting to help is not the maintainer. The focus is on addressing common bottlenecks in software sustainability, especially regarding coordination and leadership, rather than just developer output. Key points discussed in the video include: - **Understanding Project Stagnation**: Explore reasons why projects get stuck, including a lack of clear priorities and decision-making processes. - **Case Studies**: Harihareswara shares several anecdotes, such as her experience with Wiscon—a feminist science fiction convention—where she organized and prioritized a jumble of tasks, leading to improved team efficiency. - **Team Dynamics**: Emphasizes the importance of effective communication, such as gathering different opinions to clarify priorities and streamline decision-making. - **Funding and Financial Support**: Discusses how securing corporate funding was key for moving the Autoconf project forward, which had seen no releases for several years. - **Nudging and Encouragement**: Describes how minor nudges and maintaining regular check-ins can help keep a contributor focused and on track, citing her work with the Pippins tool. - **Practical Steps for Contributors**: Provides a sequential approach for contributors to become effective leaders in projects: - **Settling In**: Start with low-trust tasks to assess and earn credibility. - **Taking Charge**: Engage in tasks that require trust and oversee routine project management. - **Making Change**: Propose and implement necessary changes to the project’s infrastructure. - **Passive Baton**: Phase out responsibly, transitioning leadership to successors. - **Project Lifecycle Considerations**: Discusses how every open source project has a lifecycle and the importance of recognizing when a project may need to end or combine with others. The video wraps up with the significant takeaway that anyone can lead efforts to get projects unstuck and encourages contributors to embrace the challenges involved. Harihareswara also highlights the need for a supportive environment in open source, emphasizing the relationship dynamics that facilitate trust and collaboration within teams.
Suggest modifications
Cancel
