Canonical Voices

Daniel Holbach

The Ubuntu Developer Advisory Team has been in place for two or three release cycles already and it’s been a fun journey so far. We’ve got in touch with many many new contributors and old contributors as well. If you don’t know what this team does, here’s what our wiki page has to say:


  • Reach out to new contributors, thank them for their work and get feedback.
  • Reach out to people who might be ready to apply for upload rights and help them.
  • Reach out to contributors that went inactive and get feedback from them and offer help.

I personally found this very rewarding as I got to talk to many new contributors and see how they feel about Ubuntu Development.

You can help!

If the above sounds interesting to you and you enjoy engaging socially, if you have made a few experiences in Ubuntu Development and want to help out, please talk to me or comment below. It’d be great to have you on board!

Read more
Daniel Holbach

Parabéns e muito obrigado!

I’m particularly happy to announce that the Brazilian team managed to get their translation of the Ubuntu Packaging Guide up to more than 70% of completion, which is the magic threshold to get it accepted and posted on This means that our current list of available languages is:

  • English
  • Spanish (99%)
  • Russian (85%)
  • Brazilian Portuguese (74%)

You can view the individual forms of the Packaging Guide in Brazilian Portuguese here:

Right at the start I said that I was “particularly happy” about this translation. That’s because I recently picked up a little bit of Portuguese. Mostly useful sentences like “Meu irmão gosta de cerveja” or “O leão escreve cartas”. Thanks Duolingo!

A big big big “obrigado” to the tireless Brazilian Portuguese translators. You all are heroes! This is great news for everyone who wants to get involved in Ubuntu development, as it smoothes the first steps considerably.

You can help out with translations. Just head to the Packaging Guide’s translation page in Launchpad, pick your language and get started. Current runners-up to the translations mentioned earlier are:

  • German (32%)
  • Japanese (15%)
  • French (7%)
  • Indonesian (5%)
  • Dutch (4%)

The available translations are not entirely complete yet either, so please do get involved.

Read more
Daniel Holbach

Ubuntu Touch summary (week 11)

I’m posting this on behalf of the Ubuntu Touch team. (Originally posted here.)

The interest in Ubuntu Touch is still going strong, many work on apps, many helped with porting, some started fixing bugs in Ubuntu Touch, so here’s a few highlights of Ubuntu Touch development of the last week:

  • Jim Hodapp worked on enabling Qt multithreaded rendering in the camera app.
  • The media app received a number of updates. Jim also enabled Qt multithreaded rendering here and greatly simplified the UI orientation/rotation support. It’s based on Screen.orientation instead of directly using QtSensors now. Renato Filho added some autopilot tests.
  • qtubuntu-media-signals (a library that coordinates qtvideo-node, qtubuntu-camera and qtubuntu-media across thread contexts) was added by Jim and Francis Ginther.
  • Gustavo Boiko put quite a bit of work into the telephony app, which was optimised to load data from telepathy-logger by reading it just once and dispatching the events to the correct model. Also some unit tests were added, the autopilot tests now pass as well. HUD actions were added and the app now uses the toolbar from the SDK.
  • Guenter Schwann worked on the gallery app, which had its event view updated to use Listview. Also “Add album” and opening the photos view from the album view were reenabled.
  • The Platform API was updated by Jim and Ricardo Mendoza to read the resolution and getting the updated rates of sensors. The accelerometer support was refactored so that it supports calling more than one observer listener per Sensor instance. Sessions can now be tracked in a different namespace than the app manager. Various tests were fixed.
  • ubuntu-session had support added for SMDK4210 (Samsung GT-I9100) by Oliver Grawert.

Many other fixes have gone into the lower levels of the stack which were not considered for this update.

The ports team was busy as well and many Ubuntu Touch ports received updates. Some of them regularly and daily (just like the normal images on cdimage.u.c). Newly added ports are:

  • working: Samsung Galaxy Tab 7.7 (GT-P6800)
  • work in progress: HTC Sensation XL, SGS III (Qualcomm AT&T), Toshiba AC100

Thanks to everyone involved for your fantastic work!


Ubuntu Touch runs on tablets, phones and other devices. We are open to suggestions, fixes and new crazy ideas. If you want go get involved, please get in touch:

Read more
Daniel Holbach

Ubuntu: you’ve changed

I can’t precisely date back when I got involved in Ubuntu, all I do know is that Michael Vogt helped me out with some Debian CDs in university and some months later told me: “you might like this, you can upgrade to it”. I tried it and was hooked immediately.

Ubuntu 4.10 (CC BY-SA 2.0 -

Ubuntu 4.10

When some time later the Ubuntu preview was announced and I learned more about the project goals and values, I felt totally inspired and knew I would totally love this. I had a hard time focusing on my thesis, I ignored it for a while and got involved in Ubuntu. Many folks encouraged me and I started to do some packaging. I packaged some software outside of Ubuntu first (coaster for example, it seems not to exist any more), but quickly got dragged into Ubuntu itself. (pyzor was the first upload I could find.)

Life in 2004 was exciting:

  • Plugging in a USB key and having it show up on your desktop finally worked.
  • We used GNOME 2.8, Firefox 0.9, XFree86 4.3, Evolution 2.0 and 1.1.2.
  • Some months later we had Live CDs!

This was a very special time, it inspired many to do all kinds of crazy things.

April Fool's login (lifted from

April Fool’s login

Admittedly, I looked funny too.

myself at Ubuntu Down Under (picture taken by Tollef Fog Heen)

myself at Ubuntu Down Under

Ubuntu was very different. Its focus on making things work and favouring simplicity won many hearts over. Also its friendly community with high social standards inspired many and made it a pleasure to be involved and try something new. Ubuntu introduced LoCo teams, which brought Ubuntu into many parts of the world, which helped many finding new friends and which brought many new opportunities to everyone.

Ubuntu always was full of change. We pioneered and forged ahead in many many places. We were the first to ship a 2.6 kernel, we modularised X, derooted many services, made it easier to upgrade and install packages, wrote upstart, made booting fast and very often were the first to think new, shake up the standards and improve things for everyone.

Each of these changes was hard work, sometimes brought some problems with it, had its opponents, but also inspired many others, often new folks to jump in and help.

Some of these disagreements were very loud, sometimes they were inside the Ubuntu community, sometimes included Canonical people, sometimes they were on the sidelines of the Ubuntu world. And they were almost accompanied by calls that Ubuntu/Canonical should do more, do less, do it earlier or do it later. Some of the decisions which were made were reverted as a result of testing and feedback, but many stuck around and proved themselves as wise choices.

We were quick to embrace and count on new technologies. Many casual Ubuntu users might not be aware of the great work and innovation which made Ubuntu quickly became a favourite in the Cloud space, which is moving fast as well. This is a significant achievement and the fast pace and amount of change might have been just unnoticed by some because they’re don’t actively use the cloud or don’t watch the space.

Being and staying relevant in the software world is tough, it requires lots of hard work, sometimes a surprise element – quite often it requires change. This is hard, especially in a large community like ours, with many subcommunities, teams, different goals and directions.

Another possible source of disagreements is the symbiosis between Canonical and Ubuntu. The ideals of Open Source communities and business decisions sometimes go against each other and trust me, I’m not always 100% convinced or 100% happy with every decision. Then again all these  decisions are very hard to make. Partners, long-term plans, the press, big investments and lots more have to be considered carefully, which is not always on the radar of people who comment first.

Canonical’s and Ubuntu’s success are very tightly intertwined and it’s worth keeping these mutual benefits and what we achieved together in perspective.

Ubuntu devices

Who would’ve thought this is possible 8 years ago?

Looking at the client side, I still can’t believe where this wild ride took us. We went from “working USB keys” to “favourite product” at MWC, which according to Wikipedia is the “world’s largest exhibition for the mobile industry”, an industry known for moving fast and being unforgiving. This is a major achievement for us as a community. People trust us to actually pull this off.

There are many open questions right now, many uncertainties, some problems, but one thing is clear: if we want this to happen and Ubuntu on devices everywhere, this is the opportunity. This is the time and we’ve got to work together.

Perfect teamwork (lifted from

Perfect teamwork

We have the world’s attention, we’re off to a great start, but we have lots of work to do. This year will be the year in which we make it happen.

In the last weeks I’ve been working alongside the Ubuntu Touch team and have been able to witness how hard they work and how quickly the team gained new members from everywhere, how inspired everybody was to contribute and work on core apps, port Ubuntu to new devices, write patches and kick off discussions to lead us into new places. In some ways this is not unsimilar to what Ubuntu felt like in the early days. A lot of people thought we were crazy, there were established projects and players, still we managed to bring something new to the table together.

This is exactly the pioneer spirit we need, the inspiration we need. If you want Ubuntu to succeed, ask yourself what the best place is in which you contribute. There are many, but obvious picks I can see are QA (both manual and automated testing), work on core apps, porting and fixing bugs in Ubuntu in general.

I realise that the increased pace and a set of new priorities in the project are painful for some of us and they are disruptive. There are problems which need to be resolved and as some pointed out elsewhere before, communication and compromises are hard. What I feel is most important in our current discussions is: We all care a lot, and we all agree on much more than we actually disagree on. Let’s resolve the issues and figure out what we all can do make this a success.

Ubuntu, you’ve changed, yes, but we were never closer to our goal of bringing free software to all of the world! Let’s work together to make this happen!

Read more
Daniel Holbach

The Port-a-thon is in full swing


I can’t believe it hasn’t even been a week since we announced the availability of the Ubuntu Touch Developer Preview images. We also put instructions out to contribute to the effort and specifically how to port Ubuntu Touch to new devices.

In the recent Ubuntu Development Hangout with some members of the Ubuntu Touch team I mentioned it already: these people are heroes. They’ve worked day and night and it was a pleasure to put the porting guide and Port-a-thon event together with them.

After that it has been very satisfying to be subscribed to the Ubuntu Touch devices list. We started with four devices, on which Ubuntu ran right from the start. The reference devices so to speak. Fast-forward 5-6 days and we have images and instructions for 15 other devices. FIFTEEN!

On this list currently are: Asus Transformer Infinity, Asus Transformer Pad TF300T, Galaxy Nexus (toro + toroplus), Galaxy Tab 2 10.1 Wifi, HTC Desire, HTC DNA, Huawei Ascend G300, Nexus One, Samsung Galaxy Note II, Samsung Galaxy Note, Samsung Galaxy S (GT-I9000), Sony Xperia S, Sony Xperia T, VZ SGSIII.

If your device is on the list and you’re curious, head to the devices list and find out how to get the new Ubuntu Touch hotness straight to your device.

Another 22 ports are work-in-progress with developers or teams of developers working on them.

Update 2013-02-27 17:56 UTC: it’s 23 work-in-progress ports. :-)

Update 2013-02-28 09:38 UTC: On the list of completed ports we now also have: LG Nitro/Optimus HD, Kindle Fire 1st Gen, Kindle Fire 2nd Gen, Kindle Fire HD 8.9″ and 2 more work-in-progress ports. Awesome! :-D

Thanks a lot to everyone who helped make this happen. If you’re curious what’s happening, make sure you join the ubuntu-phone mailing list and ubuntu-touch IRC channel. More info on the Contribute page.


Ubuntu Global Jam is coming up this weekend (1-3 March) and if you have a look at the list of events, you can see that from Tempe to Tehran we have events lined up where people get together to make Ubuntu better. With all the excitement around Ubuntu Touch, we added instructions to the Ubuntu Global Jam page on how to help by either testing, porting or writing apps.

If you don’t have an event nearby or your team is too spread out over the state or country, you could at least still get together on IRC or over Hangouts. We have docs on how to run an event.

Read more
Daniel Holbach

It takes two

At the last UDS we talked quite a bit about LoCo teams in during the Leadership Mini Summit. One interesting point was that many seemed to have the impression that events have to be big, everything has to follow an established protocol or a rigid process. That’s not the case.

I’m sure my friend Jorge Castro would agree with me if I told you to JFDI. The result of not doing things is that things will not get done. Setting up an event is sometimes just a matter of sending a mail to the team and asking everyone to come to a certain place at a certain date and time. Another point discussed was the number of people. Seriously, if it’s just two of you who hang out and make Ubuntu better or just have a good time together, that’s so much better than not meeting at all. :)

The reason I write all of this is that we’re getting closer to Ubuntu Global Jam again and some of you might be considering setting up an event and adding it to the LoCo Team Portal and you might still be a bit unsure. There’s really no need to.

It’s very very likely you don’t need a huge venue with lots of bells and whistles, maybe just meeting in a coffee shop will be good enough? A room in your local university? Or invite people to your place? Just somewhere with internet might be good enough. You might get to know some new local team members and it’s all about having a good time.

We have instructions up how to set up a jam, a video, and you can always ask for advice. Join the Ubuntu Global Jam today!

Read more
Daniel Holbach

Going mobile

Many asked me in the last time what became of the Ubuntu on Nexus7 project. I’m happy to say that it’s going really well. Some weeks ago it was already very easy to install Ubuntu on a Nexus7, since then things got better and better. Many bugs were ironed out, but the piece most folks have been concentrating on recently was the desktop-r-reduced-power-ram blueprint.

The spec says:

In the past few cycles, we saw that our desktop took more and more RAM to run the full session. Also, more daemons mean more interruptions on the CPU, and less battery file. We will get services to not run when not needed and work on improving the code of those components to consume less resources

Why is this so relevant in a mobile setting? Simple. Most mobile devices are less well-equipped than the common Desktop or Laptop, and every interruption, every bit of CPU usage, every disk access costs precious battery life. Fixing this kind of bugs will have a great and positive impact for all devices running Ubuntu.

Here’s a quick summary of the work which has been done:

  • Robert Ancell: look at why lightdm is using 30MB (it’s due to the memory locking – without locking it drops to 3.7M)
  • Michael Terry: Make lightdm selectively lock memory instead of using mlockall
  • Sébastien Bacher: look if gnome-keyring needs to be running all the time (needs to, restarting would mean having to unlock it again, e.g ask user for password every time)
  • Sébastien Bacher: look at what is making goa run for some users (it’s e-d-s)
  • Sébastien Bacher: set up follow-up meetings about the topics we didn’t cover during the session
  • Ken vanDine: check with online team if signond needs to be running all the time
  • Ken vanDine: investigate long running telepathy-indicator/mission-control
  • Iain Lane: drop g-c-c recommends on goa so it’s not installed by default
  • Oliver Grawert: seed zram-conf
  • Brian Murray: look at what update-notifier is used for nowadays, identify if those functionalities could be replaced/moved to upstart jobs []
  • Colin Watson: fix upower memory leaks
  • Colin Watson: reduce update-notifier memory use

Update: Sébastien also mailed the ubuntu-devel@ list with a nice summary of the work.

We need your help

If you have a look at the desktop-r-reduced-power-ram blueprint you can see that there is still quite a bit of work which need to be done. There are assignees for some of the work items, but all of them will be happy to hear you offer help. The effort is coordinated on #ubuntu-desktop, so you best head there and start chatting with the team.

More information – live hangout

Tomorrow, 7 Feb 2013, at 9 UTC I am going to talk with my friend Sébastien Bacher on about this initiative, so if you want to find out more, be sure to tune in or watch the recording in the ubuntuonair youtube channel afterwards.

Read more
Daniel Holbach

We all want more quality. We all wasted too many hours trying to fix broken software and we all know that new users struggle the most when facing crashes or other unexpected results. We probably all also agree that testing is a good idea and if it’s automated, then that’s even better.

Automatically exercising large parts of some software’s functionality helps a lot in guaranteeing that things still work, even if the code or some underlying foundations change. The idea is to write the test-case once and have it do its work whenever bits change and let us know if things break unexpectedly – especially before users run into bugs.

Tomorrow, 1st February 2013, we are going to hang out in #ubuntu-quality on to have a Hackfest about Automated Testing.

So what’s going to happen there?

  • We are going to have seasoned Ubuntu developers who will introduce you to autopilot (for UI testing) and autopkgtest (for integrating tests with the package in a more general sense).
  • We have a list of tests we want to work on together (but you can work on your own tests if you like as well).
  • We are going to have lots of fun and make Ubuntu a better place.

If you are interested, that’s great, because this is one of the coolest contributions to Ubuntu you can make. For autopkgtest it might be good to have at least a bit experience with scripting or programming, for autopilot less so. Be curious, be there, make Ubuntu better!

Check out our docs here and see you tomorrow!


Read more
Daniel Holbach

I mentioned the upcoming Ubuntu Developer Week in my last blog post already, but I thought I’d mention a couple more great sessions we are going to have during the event.

If you haven’t read the original post yet, here’s the quick details: running from 29th to 31st January 2013 we are going to have sessions, mostly on IRC, some on Hangouts-on-Air, where you get a introduction to all kinds of topics surrounding Ubuntu Development. After attending the sessions you will have a good idea how things roughly fit together, how to get started, who to talk to and what’s going on. It’s the perfect opportunity.

Here’s a few quotes from session leaders:

Benjamin Drung

Benjamin Drung

Benjamin Drung and Michael Bienia (of whom the internet does not seem to have any pictures whatsoever) are going to lead the Developers Roundtable and have this to say:

Do you have questions about Ubuntu development? Here you have the best opportunity to ask everything you want to know, because we will have a number of developers there who can answer your questions for you.


David Planella

David Planella

David Planella, who will talk about “Writing apps for Ubuntu”, says:

Learn how to use the best open source tools and technologies to write your apps on Ubuntu, both on the desktop and on the phone. You’ll be able to get your first app running in a matter of minutes!



Michael Hall

Michael Hall

Michael Hall never gets enough, so he’s giving two sessions at UDW this time around. Here’s what he has to say about Ubuntu App Developer tools: “Ubuntu provides a variety of tools to help you write and manage your applications. This session will cover everything from bootstrapping a new project, to making the final packages installable through the Software Center and everything in between.”

He will also talk about Unity integration: “The Unity desktop provides many opportunities for your application to integrate with the full user experience. Learn how to add your Application to the Unity messaging or sound indicators, add your own indicator, extend the Unity Launcher and much more.

Oliver Grawert

Oliver Grawert

We’re excited to have Oliver Grawert here, who will talk about Creating Ubuntu images and the Nexus7 images in particular. He will talk about “[t]he Ubuntu image build infrastructure at a glance, what tools do we use, how do they interact and how is the hardware set up for building the official Ubuntu images” and “[h]ow are the nexus7 images different from “normal” Ubuntu images, what can be hacked to make small modifications, how can they be re-packed or supplied with a different root file system“.


Alex Chiang

Alex Chiang

Alex Chiang will introduce us to the world of memory leaks and says:

As we polish and prep Ubuntu for mobile devices, a key activity will be hunting down and squashing memory leaks. This session will discuss the basic theory of leaks, introduce valgrind and our brand new apport-valgrind wrapper, and how to analyze a valgrind log file. A C/C++ background will be helpful to get the most out of this session, but is not strictly required.

Nicholas Skaggs

Nicholas Skaggs

QA mastermind Nicholas “balloons” Skaggs will talk us through “Automated Testing with autopilot” and says:

Learn about how autopilot is utilized by the unity team and quality team to test the ubuntu desktop. We’ll also provide an overview of what autopilot can do, show and run some example testcases, and give you the knowledge needed to get started writing your own autopilot testcases.


We are super happy to have brought this line-up of speakers to Ubuntu Developer Week this time around. Head to to review the full schedule, how to join in and find out more.

Share the news with your friends and bring your questions! :-)

Read more
Daniel Holbach

The times for Ubuntu have never been more exciting. Cloud, server, desktop, laptop, TV, tablet, phone – everything runs Ubuntu or is soon going to. This makes developing Ubuntu very special, because fixes which go into Ubuntu in one place will benefit all form factors and all circumstances where it’s used. By improving Ubuntu you make millions of people around the globe happy.

During every 6 month release cycle we run Ubuntu Developer Week. It’s back and we’re going to have it from 29th January to 31st January. During the event we will have online sessions where seasoned Ubuntu developers introduce you to their respective area of expertise or to Ubuntu Development in general.

We will have many great sessions, from hands-on introduction to packaging and Ubuntu development to talks about how to quickly get involved in certain teams and interact with other projects. We will talk about tools and infrastructure, fixing bugs, finding memleaks, working with apps, create Ubuntu images and much much much more. This is the best opportunity to get a feel for how Ubuntu development works, get to know people and ask all the questions you might have.

I talked to a few session hosts, read below what they had to say.

Martin Pitt

Martin Pitt

Martin Pitt, who will talk about Automated Testing, says: “We have been, and are changing the Ubuntu development process to employ automated testing and avoid introducing regressions, and to improve confidence, focus, and development speed. In the first talk I will give an overview about the various kinds of tests that we do, so that you know where to watch out for failures and get debugging information. The second talk focuses on how to write tests, i.e. which technologies are available for e.g. hardware and GUI related behaviour or system-wide integration checks.”


Stefano Rivera

Stefano Rivera

Stefano Rivera, who will talk about Upstreams and Debian in particular, said: “So, working effectively in Ubuntu means also working with the teams and people upstream who wrote the software we distribute. I’ll talk about why this is important, when it’s necessary, and how to go about it. In particular, our most important upstream is Debian. Debian has a rather unusual (though powerful) bug-tracker. We’ll cover finding, submitting, and modifying bugs on it.

Chris Wilson

Chris Wilson

Chris Wilson, project leader of the Hundred Papercuts Team, says: “Unity may be the shiny new thing that everyone loves, but style without substance is only so much fluff, and the substance of Ubuntu is still its GTK-based apps. Once Hundred Paper Cuts focuses it’s attention on that substance, rubbing out the little annoyances that get under our skin every day we’re using Ubuntu. This session will introduce you to the project, how it works, and how to get involved. If you want to contribute to Ubuntu in a way that has the biggest impact on the quality of experience for the end user, then don’t miss this.


Bhavani Shankar

Bhavani Shankar

Bhavani Shankar, said about his talk about patch systems: “Many a time we wonder how to integrate a particular fix a particular part of the code in a program and upload into repositories without having to change code each time by hand and making it clumsy. In this session I’m going to show how to use different patch management systems that are in practice now.

About his talk about the app review process in Ubuntu he says: “In this session I’m going to explain the present workflow of reviewing apps and give an introduction into the new app dev upload process to automate reviews.

The forum we use for this is IRC, as it makes it easy to interact for many people without losing track, you can easily copy/paste and we can save the logs as searchable docs afterwards. You join in by simply connecting to #ubuntu-classroom on

Check out the schedule and find more info on the Ubuntu wiki. We hope to see you all there, please let you friends know too. :-)

Read more
Daniel Holbach


Many have asked me what’s been going on with the work on Ubuntu on the Nexus 7 recently. A lot of people put work into getting the raring images ready for public consumption. 12.10 worked great on the Nexus, but there were a few blockers on getting 13.04 to work as well. On this road among other things these issues were fixed:

  • A new onboard pre-release made it into 13.04 which fixes many bugs already and makes our on-screen keyboard a lot easier to use. Thanks a lot to the onboard team.
  • The new Unity stack got into raring, which is now automatically tested after commits and auto-released into 13.04. This is a huge milestone from the Unity team. Among the issues fixed was a nux problem, which constituted a blocker.
  • The new raring images use oem-config to present us with an installer window, where you can specify a user name, the wireless network you want to use and other bits.
  • Many many other issues were fixed as well.
Ubuntu on the Nexus 7

Ubuntu on the Nexus 7

So what does this mean for you now? You can now very easily put Ubuntu 13.04 on your Nexus 7. It won’t need any additional PPA, it’s stock raring, you won’t have to reflash, but can just do your regular updates and enjoy the latest and greatest improvements day by day.

This is a huge achievement and will allow us to do better and more immediate testing and hacking on the device.



One thing we want to improve on the Nexus 7 (and in Ubuntu in general) is memory consumption. Alex Chiang has put together some great blog posts on how to help with finding memory issues and debugging them. They are absolutely worth a read and an effort worth getting involved with. Here are the links:

If you want to make Ubuntu better and have a bit of a development background, be sure to check them out.


Meeting the team

Everybody who has been working on Ubuntu on the Nexus 7 has documented things on the wiki pages, so if you are excited about this, be sure head there first. Also does the team hang out in 24/7 in #ubuntu-arm on, so feel free to drop by, say Hi and get to know the others.

These are exciting times for Ubuntu and you can be part of it. :-)

Read more
Daniel Holbach

A great way to contribute to Ubuntu is to ensure its functionality always works. What’s even better is that our infrastructure allows us to write tests once and continuously test if the tests still all pass, so whenever a package is updated or changed, we run the tests and can see if the functionality we rely on is still there and working perfectly.

This puts us into a situation where we all can contribute tests once and can basically monitor forever if the code still works. Personally I believe this to be one of the most efficient contributions you can make to Ubuntu (and to Open Source in general).

We want more people to use Open Source software and we all want more quality. We don’t want regressions, we don’t want subtle bugs which nobody ever got around to test. We don’t want anyone (least of all less technical people) to be surprised by bugs.

I hope you are excited about these possibilities as much as I am. If you are, I’d like to invite you to our Automated Testing Hackfest on Thursday, 13th December 2012. Many experts around Automated Testing are going to be hanging out in #ubuntu-quality, there are going to be demos, a lot of talk about automated testing infrastructure and tools and of course a lot of live-hacking!

Jean-Baptiste LallementMartin Pitt

There will be many more, but Jean-Baptiste and Martin already confirmed they’ll be around to help out and get us started! Be sure to join us in #ubuntu-quality on and check out the Automated Testing Hackfest page for some more info!

Read more
Daniel Holbach

We have achieved a huge milestone in the development community. For years we wanted translatable packaging and development documentation. It’s there. If you head to you can see the following:

The Ubuntu Packaging Guide (Spanish) – would you like to learn how to package or become an Ubuntu Developer? Here’s a comprehensive, topic-base guide that explores and describes the main concepts of packaging. It is available as

This is absolutely awesome. From now on we will be able to add languages and have up-to-date Packaging and Development docs available whenever they are complete enough.

This work was brought to you by many people who worked very hard to get all the bits right, both on the packaging, integration, beautification and translations sides. You all know who you are. Be proud of your work. This will ease the steps of many people into helping out with Ubuntu!

As always this is ongoing work and the great thing is, you can help out:

This makes me a very happy man and it’s great we finally got there. Now let’s get all the other translations up to scratch! :-D

Read more
Daniel Holbach

Our Ubuntu Development Hangouts have had guests every now and then, but we wanted to get more people on board to talk about what’s going on in Ubuntu development. Many of our viewers asked for more detailed information about specific topics.

So here’s what we’re up to in the next weeks (we’ll add more dates and more sessions):

  • 4th Dec 2012, 15:00 UTC: Rick Spencer, Vice President of Ubuntu Engineering at Canonical will talk to us about 13.04 and the great things which are coming.
  • 11 Dec 2012, 16:00 UTC: Iain Lane, Ubuntu and Debian Developer will chat with us about desktop stuff, motu stuff, release team, backports and all that jazz.
  • 13 Dec 2012, 9:00 UTC: Didier Roche, Unity+Desktop hacker, Unity progress in 13.04, daily builds, automated tests.
  • 18 Dec 2012, 16:00 UTC: Chris Wilson, One Hundred Paper Cuts Team Lead will talk about the One Hundred Paper Cuts project, what the project does and how to get involved.
Your host

This guy will be part of the fun as well. :)

Read more
Daniel Holbach

13.04 progress

We are on the road towards 13.04 where the Raring Ringtail will be released on April 25th. Until then we still have some time, but everybody has made great progress in the last few weeks. The time after UDS is usually the busiest, where people massage the discussions at the conference into specifications and blueprints, but also get busy on figuring out what might and what might not work for the Ringtail.

Here’s a list of great things which happened in the last few weeks in areas I had to do with:

  • The team working on the Nexus7 is very close to releasing a first ‘raring’ image for the Nexus7. This will make life for everyone a lot easier. We will be in a position, where we can immediately see which changes improve the experience and where things need fixing. The current blockers for this is mostly just a nux fix. Some other small pieces of breakage are under investigation as well. (Matt Fischer let us know that the installation problem regarding the “32Gb Nexus7 with 3g” will also be fixed by this image.)
    The team also kicked off work to get the memory consumption on the Nexus (and in general) under control. Alex Chiang blogged instructions to help out with identifying issues in there. (You don’t need a Nexus device for this.) If you want to learn something new and very useful, please read the article since not only the Nexus 7 but Ubuntu on all platforms will benefit from this work. Matt Fischer also blogged a nice overview over the kinds of bugs which were filed on Ubuntu on the Nexus 7.
  • Automated Testing in Ubuntu has seen a huge boost in this cycle already. People following the raring-changes list closely will have seen numerous uploads across many parts of Ubuntu adding or improving tests. Autopilot is also getting closer to generally being usable for Desktop-related testing. We improved our documentation for writing autopkgtest tests to better align with our improved tools. Also go and do read Martin Pitt’s updates to get an idea of how automated tests are used in Ubuntu. Awesome.
  • New contributors should have a much easier time to get involved in Ubuntu Development this cycle. Harvest now lists ‘lintian-easy’ and ‘lintian-very-easy’ opportunities which should be great to get involved. We will soon deliver the Packaging Guide in Spanish as well. We started the planning for Ubuntu Developer Week (January 29th-31st 2013). Last but not least: we are going to have many exciting Ubuntu Development Hangouts on UbuntuOnAir and will invite many developers who talk about what’s going into the Raring Ringtail.

Speaking of which: the dates and times for these hangouts are

  • Tuesdays at 16:00 UTC and
  • Thursdays 9:00 UTC.

This cycle is going to be exciting and you can be part of it! :-)

Read more
Daniel Holbach

Ubuntu Core on the Nexus 7

There was lots of buzz around Ubuntu on the Nexus 7 and I was lucky enough to get my hands on a Nexus 7 myself, so I had to try out getting Ubuntu on it. The instructions were incredibly clear and everything worked just perfectly. I couldn’t believe how quickly the the Nexus 7 booted into a standard Ubuntu Desktop.

Ubuntu on the Nexus7

When I started to play around with it, I noticed how much of the vision which shaped Ubuntu in the last years works really well on such a small device. Unity is great, the Ubuntu font looks very crisp, the touch gestures, etc. It was a pleasure to see this and play around with it. Naturally I ran into a couple of issues, which was totally expected. We want to know what these issues are and want to work on them to make Ubuntu ready for ranges of hardware. It was great to see that almost every issue I noticed was filed as a bug report already and the most pressing ones have assignees already.

When I decided to dive into it some more, I was glad I had a a Micro USB Host Cable (OTG Cable) and the small USB hub, Intel gave to UDS participants. I was all set to use the tablet as a small computer. Awesome. (To everyone who has hacked on small devices before, this might be boring – I found it quite exciting to be honest. ;-) )

The current image uses 12.10 plus some patches, but it will soon move over to the 13.04 development release, where we can see bug fixes in a more immediate fashion and benefit from all the new goodness which goes into Ubuntu. Expect an announcement of the move to ‘raring’ very very soon.

This effort is a fantastic opportunity for Ubuntu, as we can all look at one reference device and fix whatever needs fixing and let Ubuntu benefit as a whole. If you think this is a worthwhile project, you can help out. What is most needed right now is people who help test the device, report bugs, triage the list of bugs, forward them to the upstream projects if necessary. If you know how to debug memory consumption and how to improve it, you’d be a great fit for the team as well. Please join #ubuntu-arm on and talk to the folks in there.

Our documentation is up at and there soon will be more meetings, more announces and more chances to get involved. These are exciting times.

Read more
Daniel Holbach

It is another Ubuntu Community Appreciation Day already and although it’s hard to pick just one person, and I’ve worked with many great people and I admire many for what they do and who they are, today I will mention one person I’ve enjoyed working with a lot. To everybody else: you know there’s always enough hugs for you where I am. :-)

Andrew has helped out in many unnoticed places, never claimed much credit and never stood much in the limelight. Andrew, whose last name is pronounced in many different ways (ranging from ‘Starr-Bow-chick-a-wow-wow’ to ‘Something’) has the talent of turning up unexpectedly, picking up some of the hard problems and leaving a fix for it behind. Maybe it’s because our timezones only overlap somewhat and he’s only occassionally on IRC, I often woke up, looked at my inbox and felt like I just found a present in there.

Andrew has been involved in NGOs working in his local area and mailed me after a short absence that he had been busy helping out on the south shore of Staten Island after the hurricane hit. He also became a MOTU and helped out in many teams I’m involved in as well (Dev Advisory Team, Packaging Guide editors, the early NGO team, etc.)

It’s a pleasure to work with Andrew, he’s relaxed, he knows his stuff, he helps with the hard and unrewarding stuff in the beginning to give others the breathing room and open up the field and he has his heart in the right place.

Thanks a lot for your hard work Andrew, it’s much appreciated!

Big hugs to you and everyone else who make the Ubuntu, Open Source and general world a better place. You all rock!

Read more
Daniel Holbach

Restarting the Ubuntu Development Hangouts

For the 13.04 cycle, the Ubuntu Development Hangouts will be back from today onwards and we’ll be live on at

  • Tuesdays at 16:00 UTC and
  • Thursdays 9:00 UTC.

The first one is going to be today, 20th Nov 2012, 16:00 UTC. Can’t wait to see you there! :-D

Read more
Daniel Holbach

For the 13.04 cycle a team of people got together to make sure that the standard Ubuntu Desktop works great on the Nexus 7 device. This is a great opportunity for Ubuntu as we can all refer to one device and one chipset and make sure that Ubuntu is capable of dealing with the device. This will lay the foundations for making Ubuntu ready on many other devices.

The team meets on the 16th November 2012, 16:00 UTC in #ubuntu-meeting.

On the agenda are:

  • general Q&A – the team will answer all your questions,
  • an overview of the current work

We are actively looking for help, we need you to make Ubuntu even better. If you like to test, work with bug reports, measure, debug or fix doesn’t matter, we need you and want you on board.

We put together documentation which should provide pointers to installing Ubuntu on the Nexus 7, how to use it, how to debug and measure certain things like power consumption or memory usage and which bugs we want to fix.

If you have a Nexus 7, plan to get one or are generally excited about the initiative, or just want to find out more, make sure you’re there. Please also let your friends now.

Read more
Daniel Holbach

Our UDS in Copenhagen was the busiest for me ever, but I enjoyed it a lot. There was heaps of energy, good ideas and many good conclusions for the Raring cycle. One thing I really enjoyed was the Leadership Mini-Summit.

We had it at UDSes two times before and what I feel we did better this time around was that we had more concrete examples of Ubuntu teams, their leadership and the challenges we face. It gave us a great opportunity to be together, brainstorm and learn from each other.

I volunteered to give a brief summary for all those who could not attend this time around. The following points are all based on my memory and our notes of the event. Lots of other brief conversations happened there as well.

  • Actively training successors: we discussed a number of interesting experiences in teams and found that some teams had problems finding successors, especially in teams where leadership had been in the same hands for a longer time. We found that when the structures of new team, where things are more open and free-form, slowly moved towards more structure and more processes this might lead to the feeling that things are tedious to main and some fatigue.
    Somebody noted that when finding new leadership and key people in the team, that it’s important to note who has a special skill (maybe presenting or organising or just a special interest), and even if they are a bit reluctant in the beginning, give them lots of positive encouragement and form a personal relationship with them. Their interests are obviously important too.
    Another point mentioned was that sometimes it’s necessary and important to scale back activities if necessary. Also to harness volunteer energy when it’s there.
    Some mentioned that they had been in touch with a new class of contributors: users who need more of a framework, more instructions and were generally less self-starting. Others mentioned they had met people who had misconceptions about involvement in Ubuntu, that there are requirements or they need to be “allowed to” work on something rather than just jumping in. We should definitely encourage these people to get involved. As leaders in the community we should strive to empower others to do things like give the presentations at their events rather than inviting us to do them.
    It’s also important to always provide lists of opportunities (a TODO list basically).
  • Milestones and mid-cycle check points for community projects.
    Some team members found this very useful in watching their team projects progress during the cycle. Most technical teams use work items and blueprints which through our infrastructure are used very well. In less technical teams they are used much less.
    What everybody agreed on was that they’d try to get more team reports and use work items as well.
  • Ubuntu Member “incubator”.
    Some noticed a concern around great contributors who for reasons of their own didn’t want to apply for Ubuntu membership. Sometimes it was lack of knowledge about it, others said they didn’t know why and other just didn’t feel they were ready yet, although they clearly were.
    We will review our Membership documentation to make it clearer what Ubuntu membership is there for and how it is important.
    There were also some related discussions about how some members were just interested in becoming members and then dropped their activities. Discussions around this did not come to any conclusions though.
  • How to respond to “How can I get involved?”
    Some teams mentioned they had had great results with one-to-one mentoring, other teams said they were overwhelmed by requests for 1-on-1 mentoring. Everybody agreed that it was important to not drown potential new contributors with “walls of text”, but that for more diverse projects a simple flow chart could help to explore interests. In there it would be important to define “requirements” for the involvement, but to be encouraging at the same time.
    Some work will go into a proof-of-concept flow-chart which then could then be re-used and translated.
  • Some good ideas for LoCos in general. (These ideas turned up in various discussions.)
    One team had a meeting where lots of people had lots of ideas, but no concrete outcomes or plans of action. Some said that it’d help to categorise the ideas and try to group people into teams who could then collaborate and present their work the next time.
    In another part of the conversation we talked about “official events” and “big events”. Everybody agreed that it’d help to generally try to also encourage small, fun events, like Ubuntu Hours for example.
    Although there were conflicting views on how to organise a big LoCo in general, everybody agreed that it was important to encourage a feeling of one team, no matter which part of the state/country the contributors are from.

Many other topics were discussed as well and it was great to see how we, once we sat together, solve problems together and inspire/help each other. Thanks a lot everyone for turning up.

The work items we agreed on were:

  • Daniel to write a blog post about the Leadership Mini-Summit.
  • Alan to draft proof-of-concept workflow diagram to visualise activities in a team. Daniel to help publicise it and get feedback.
  • José to edit the Question2Answer template and ask to get localized version of a Q&A system.
  • Daniel to add flavour teams to CC checkup schedule and mail CC list about the idea to reach out to regularly teams to check in how they’re doing.
  • Chris to check into automating the team reports by way of the LoCo Team Portal, and try and get it implemented. Pasi to work on a proof-of-concept for a simple website for sending and gathering team reports easily.
  • Daniel to bring up the idea of creating a mailing list for the broader community (we can use it for announcements).
  • Laura to mail all councils/boards who can approve members to notify the CC about new members.
  • Joel to review and send suggestion to CC.

Thanks again and good work everyone!

Read more