Ubuntu Patch Pilots
Welcome to the Patch Pilot Program! Our aim is to support contributors with their patches, package sponsoring, and other activities to improve Ubuntu. The program is designed to make contributing to Ubuntu a welcoming and inspiring experience while fostering community knowledge and maintaining ongoing contributions.
Receiving Help from a Patch Pilot
Are you interested in contributing patches to Ubuntu? There are a number of ways to participate, and through this program we’d like to provide you with mentoring and support in getting your patches into Ubuntu. You should reach out to a patch pilot if:
- You have a patch against an Ubuntu-specific package that you’d like to contribute.
- Your package can’t go into Debian and you’d like to contribute a new Ubuntu-specific package.
- You’d like a new package or patch to appear in Ubuntu, but need some guidance on how to make it part of Debian.
Patch pilots are available on #ubuntu-devel on irc.libera.chat and will be monitoring bugs with patches on Launchpad. The current pilot is noted in the channel topic. If you’d like to plan ahead, please see the Ubuntu Patch Pilots calendar.
If you would like to contribute to Ubuntu in other ways, please see our guides on how to contribute.
Being a Patch Pilot
As a patch pilot, you will be a primary contact in supporting the community towards Ubuntu development. It is the development equivalent of being “on call” in the site reliability engineering world. Learn more about how patch pilots are helping the community and how to become one.
Welcoming the Community
We value the support from Ubuntu community members and strive to create a positive and engaging atmosphere. To achieve this, we identify contributors with potential to grow as advocates or future patch pilots while ensuring that all contributors are treated respectfully, provided with learning resources, and supported throughout their journey.
Some techniques to foster engagement include:
- Thanking contributors for their contributions and time commitment
- Offering encouragement and highlighting their strengths
- Informing contributors of their progress and setting expectations
Reasonable Contributions
Please do your best to accept contributions in any reasonable form. Remember, every contributor has their own unique journey and way of giving. All we ask is that the submitted contribution is functional (e.g. patch applies) , builds correctly, and has been tested. If you’re ever uncertain, here are some examples of where you as a patch pilot can support contributors:
- Patch against the wrong git branch
- Needs a quilt patch rather than a change directly to upstream sources
If there are opportunities to improve tooling for uncommon types of contributions, please discuss on the ubuntu-devel mailing list. You are welcome to point contributors to guides on preferred ways to contribute for their future patches, which helps them learn more about our ecosystem.
Activities Breakdown
Sponsoring Queue
The primary focus is the general sponsoring queue. We want to avoid items being open for extended periods of time. When reviewing changes and sponsoring uploads, keep the following in mind:
- Prioritize items waiting the longest
- Manage expectations by informing contributors about expected feedback times
- Avoid moving goal posts and provide thorough explanations when abandoning long-pending changes
Availability on #ubuntu-devel
During your piloting session, you are the primary representative for inquiries in #ubuntu-devel on libera.chat. Address questions about contribution processes, technical patch issues, or repository support while fostering encouraging conversations about patch contributions.
When you begin your session, please write @pilot in in #ubuntu-devel, which will add a note to the topic that you are the current patch pilot. Once your session is finished, use @pilot out to get yourself removed.
When conversing on other platforms such as launchpad, you are also welcome to point patch authors to #ubuntu-devel and this program to continue discussions. If contributors reach out to you outside of your session, feel free to refer them to the current patch pilot.
Operation Cleansweep — Open Bugs with Patches
There is a growing number of open bugs with patches on them. Following the Review Guide, you can help make sure community members have the support they need to get their patches into Ubuntu. Contributors might occasionally need clarification on the guidelines, and we’re here to provide support and guidance.
Developer Documentation
There’s extensive documentation on the sponsorship process and Ubuntu Development at wiki.ubuntu.com. In line with Diataxis principles, even small changes can greatly improve the documentation, ensuring it remains updated and effective. This is a great opportunity to improve on that, which will decrease recurring questions over time.
If you are unsure about the scope of your changes and would like some guidance, please reach out to #ubuntu-doc. However, don’t be afraid to make more extensive changes. A large amount of outdated documentation can cause more harm than a small amount of available up-to-date information.
Program Logistics
Communication and Handoff
The primary channel to exchange information as a patch pilot is #ubuntu-devel. Please avoid private messages unless needed, this helps keep the community in the loop and scrollback for the next patch pilot.
After completing your work, provide a helpful handoff to the next patch pilot, including context and additional instructions as needed. Handoff should be posted in the patch pilot handoff thread on discourse for this cycle.
Time Commitment and Requirements
To be a patch pilot, you need to be able to upload packages to Ubuntu. There are a number of ways to get there, but the first step is to become an Ubuntu Developer. When you begin patch piloting, ask to be added to the Ubuntu Sponsors group as well. If you’re not currently an Ubuntu Developer but wish to become one, find out how to apply.
Our rotation schedule presently results in one pilot session every 3 weeks. Each session lasts up to 4 hours, designed to offer uninterrupted time for contributors to ask questions. However, if you’re a community member interested in joining and have concerns about the session duration, please reach out. We’re open to feedback and discussions about possible adjustments to make participation feasible for you.