by Robie Basak
from Canonical

Robie has been working for Canonical as a software engineer on the Server Team since 2011. As a full time Ubuntu Core Developer, he is involved in all aspects of the development of Ubuntu itself.

Robie has two further Ubuntu-specific hats:

As a member of the Stable Release Updates (SRU) team, he is delegated the task of reviewing, deciding upon and releasing appropriate updates to the stable releases of Ubuntu. This is the equivalent of being a "stable release manager" in other software projects.

As a member of the Developer Membership Board (DMB), he reviews and votes upon applications from contributors to be able to upload directly to the project. This is the equivalent of "granting commit access" in other software projects.

You have a patch that fixes a bug on your Ubuntu system, and you'd like to see it made official. Where do you go next? Where should your submission go?

I'll talk about the flow of Free Software: how code propagates from upstreams through to Ubuntu's stable releases and how we minimise maintenance burden. This will explain how to submit your patches so that they join the flow rather than struggle against it, and to help understand some of the trade-offs involved as projects decide whether a particular contribution will be accepted.

Getting bugfixes into stable releases of Ubuntu contains a further hurdle: the quest for stability means that we have to take extra care to avoid disrupting Ubuntu users. I'll cover Ubuntu's policies and procedures for stable release acceptance.

This talk is intended for prospective contributors, but developer experience will not be required to understand it: I'll be talking about how code flows through the Free Software ecosystem, rather than the code itself. Non-developers may also find it useful in understanding how different parts of the ecosystem interact to bring Free Software to your system.

2017 September 9 13:30
30 min
104 - Agora
Ubuntu Convention Europe
Community / Contributions