Managing changes in open source projects (DevConf.CZ)

In my first DevConf.CZ talk, I describe the general concepts that go into planning features in an open source project. The second half of the talk explains how Fedora applies those concepts, and how that process has evolved over time. This talk is the basis for the “Manage Features” chapter in Program Management for Open Source Projects.

Date: 26 January 2019

Location: Brno, Czechia

Abstract:

The larger a project gets, the more important it is to communicate changes in a structured way. This talk gives attendees considerations for managing changes in their own projects like: Why have a change proposal system? What are the benefits and drawbacks? What is important to track? Who should be involved?

I’ll cover Fedora’s approach to managing changes and how it has changed over the years. I’ll share the benefits and drawbacks of Fedora’s approach and give historical examples of successes and failures. I will also address how Fedora’s approach can be used in smaller projects and where a different approach is better.

Attendees will come away with the ability to create or update the change process for their own community projects.

This post’s featured image is by airfocus on Unsplash

Ben formerly led open source messaging at Docker and was the Fedora Program Manager. He is the author of Program Management for Open Source Projects. Ben is an Open Organization Ambassador and frequent conference speaker. His personal website is Funnel Fiasco.

Share