You improve your relation with a project if you invest in it, and that is good for the quality of the project and Ubuntu. I would like to make you aware of a great way of being nice to upstreams: Adopt-an-Upstream. Slick name! But what is it? It is part of something a group of people from the community team lead by Jorge Castro have been working on ince the last UDS. The goal was to make it easier for upstream developers to find out how Ubuntu works and to improve the relations and synergy between up- and downstream.

At the wiki a starting point was created for upstreams where they can find an overview of the information that matters to them. Furthermore, a guide was created for upstreams that would like to get included in Ubuntu, but would like an overview of the requirements, the dos and the don’ts.

For members of the Ubuntu community there is something else: Adopt-an-Upstream is a way of taking care of a specific project that is included in Ubuntu. It’s mainly about being the communicational glue between up- and downstream. A comprehensive list of tasks:

• watch what’s going on upstream
• make sure new releases get to Ubuntu
• forward patches from Ubuntu to upstream
• communicate release schedules and announcements from Ubuntu to upstream

Summarised: act like a bridge between Ubuntu and the upstream project. Do you have an application you really like, or you really know a lot of, please consider to adopt it. Of course you don’t have to do it all on your own. Especially for large — be it in size, functionality or the number of bug reports — applications this can be a burdensome task. Those applications can be adopted by a group of people.

Next week Thursday 11 March at 17.00 UTC and on Thursday 18 March at 23.oo UTC Jorge Castro and I will be giving a one-hour session in #ubuntu-classroom at Freenode about Adopt-an-Upstream. We will explain the project more thoroughly and show how you can help out. Also, we will mention the Adopt-a-Package programme, which could be considered a part of Adopt-an-Upstream. If you consider getting involved in either one of these projects, please join one of the two sessions!

Questions? Please leave a comment!

Every day a lot of new bugs are reported on Launchpad, adding to the number of open bugs reported against Ubuntu. Currently there are 81259 open bugs in Ubuntu, of which 43775 are in the ‘New’ state. This means that roughly 54% of all open bugs in Ubuntu are not or were barely touched and when this post will have been published the number is already larger. When handling such large numbers of bug even the omnipotent BugSquad can’t keep up. How can we make sure the important bugs don’t get lost in this superabundance of support requests for writing good defect reports?

If you’re working with something — in the case of Adopt-a-Package an application — you like, you’re more productive. If you work on something you can keep an overview of, work is easier. This is what Adopt-a-Package purports. You choose an application you’re familiar with, or particularly fond of, and focus on getting it into shape on Launchpad. What does this mean? A small list:

• Triaging previously untriaged — ‘New’ — bugs
• Making sure no bugs are forgotten
• Moving Confirmed bugs to Triaged
• Forwarding bugs upstream

There are several ways to tackle the adoption. If you would like to adopt something as big as GDM[1] you’ll have a hard time if you’d try to do it all on your own, unless you have a lot of spare time. In such cases it’s better to form an AdoptionTeam and attack the bugs together with some other people. Smaller applications like ‘gedit‘ can be handled by one person, although it largely depends on your personal preferences and the amount of time you’re able or willing to spend on triaging. Of course you could always look for an existing group to join. As a matter of fact, I’m still looking for some more people to help out with Nautilus.

Adopt-a-Package is thoroughly explained on its wiki page, and it is that page you should use as your primary source of information. On this page you find a list of currently adopted applications and applications that we’d really like to see adopted. When you decide to adopt an application, whether you do it with a group or on your own, please check this page first to make sure you’re not duplicating efforts. After you’ve made up your mind about what you’re going to adopt, please add your name and the application to the list and notify the BugSquad maillist.

Are you interested but still have got some questions now you’ve read this? Don’t hesitate to leave a comment or drop by in the #ubuntu-bugs IRC channel. Also, in March there will be two sessions about Adopt-an-Upstream in #ubuntu-classroom, one by me at 4 March on 17.00 UTC and one by Jorge Castro at 18 March on 23.oo UTC. You can find them listed in the Ubuntu Classroom schedule.