Research Says.....Insights on Building, Leading, and Sustaining Open Source
328 | Fri 02 Aug 4:30 p.m.–5:15 p.m.
Presented by
-
Kaylea Champion
@kayleachampion
https://www.kayleachampion.com
Kaylea Champion is a PhD Candidate at University of Washington. Her work is focused on how people work together to build groovy things like Linux and Wikipedia -- including what gets built and maintained (and what doesn't), who takes part (and who is excluded), and how those organizations form (and fall apart).
Kaylea Champion
@kayleachampion
https://www.kayleachampion.com
Abstract
How do we know when a project is struggling? How can we build communities to sustain open source projects?
In this beginner-friendly talk, I will describe recent research findings about successfully sustaining an open source project and the lifecycles of these projects. We know that open source software is fundamental to global communication, business, education, and more. This software is often produced and maintained through dynamic organizations in which we have a great deal of flexibility to choose our own tasks. But what we choose to work on and what the global public most needs are not always in alignment. What organizational structures, governance practices, and technology choices are associated with increased risk? And given these circumstances, how might we work together to improve software quality and security? Let's look at what we know about signs of trouble and strategies for success, and then discuss how the research community can better serve the needs of open source.
You'll walk away with:
* new ideas for taking action personally and inside organizations
* specific data-driven insights into how projects evolve over time
Videos
How do we know when a project is struggling? How can we build communities to sustain open source projects? In this beginner-friendly talk, I will describe recent research findings about successfully sustaining an open source project and the lifecycles of these projects. We know that open source software is fundamental to global communication, business, education, and more. This software is often produced and maintained through dynamic organizations in which we have a great deal of flexibility to choose our own tasks. But what we choose to work on and what the global public most needs are not always in alignment. What organizational structures, governance practices, and technology choices are associated with increased risk? And given these circumstances, how might we work together to improve software quality and security? Let's look at what we know about signs of trouble and strategies for success, and then discuss how the research community can better serve the needs of open source. You'll walk away with: * new ideas for taking action personally and inside organizations * specific data-driven insights into how projects evolve over time
Available sources: