Lucid Community Team Plans

As many of you will know, I manage the Ubuntu Community Team at Canonical, which has horsemen Holbach, Castro and Planella in it. A large chunk of my job is to take into account the wide range of needs from our different stakeholders (community teams, Canonical teams, upstreams etc) and to flesh out a strategy for my team for each cycle. To do this I gather input and feedback from the team and these stakeholders and put together strategy that will guide the team’s work through the cycle. Today I want to share this strategy with you all.

Most components in this strategy includes a blueprint which itself includes a set of actions and in most cases a spec that outlines the goals for Lucid. The benefit of this approach is that you can subscribe to blueprints you are interested in and keep track of those projects as we work through them. If there are elements of these blueprints that you would like to contribute to and get involved with, do let us know. :-)

So, on with the blueprints. Please note: each of these blueprints is targeted for the Lucid cycle only and these are the blueprints that my team specifically is working on with assistance from the community – other Canonical teams are of course working on their own sets of blueprints. Also, this does not include all community blueprints: there are many blueprints that are not part of my teams expected deliverables.


Engage in outreach with targeted upstreams to build support for Application Indicators into their code

Help communicate needs of upstreams to Launchpad team

Continued documentation for Upstreams

Upstream Contacts

Adopt-an-Upstream initiative


Get Harvest more production ready

Improve Kernel community patch flow

Facilitate transition of Permissions Reorganisation

Governance Support

Help the IRC Council in being effective

Community Council

Developer Membership Board

Technical Board


Improve translation status reporting

Increase community participation in coordinating translations

Definition of translations best practices and policies

Improve Quality Assurance on translations

Increase community developer contributions in Launchpad Translations

LoCo Teams

Raise awareness of LoCo team work

Help the LoCo council to be successful

Make LoCo Directory usable for the LoCo Community

Governance Changes

LoCo Council

EMEA Membership Board




Regular Cycle Activities

Ubuntu Open Week

Ubuntu Developer Week

Release Party Coordination

Ubuntu Global Jam

Ubuntu Free Culture Showcase

Improve UDS Scheduling

Team Sprint Planning
LoCo Docs Day(s)
Release Name Announcement
Governance Assessments
LoCo Week
Debian Relationship
LoCo Stories
UDS Planning
Desktop Events


The Fridge

LoCo Directory and


Participate Pages
Hall Of Fame
5-a-day statistics
Governance Tracker (WIP)
Sponsoring Overview

As you can see, we have quite a bit to keep us occupied in this cycle. :-) If you want to watch the sausage being made, subscribe to the blueprints you are interested in,and do hang out in #ubuntu-community-team on Freenode where we work together. There you can see such exciting conversations as:

<jono> jcastro, call?
<jcastro> all set

We look forward to seeing you there! Horsemen…roll out!

  • nixternal

    Ahh, now this is refreshing. You know if you need any help, don’t hesitate to ask.

  • Jef Spaleta

    So about that indicator outreach blueprint….

    rhythmbox is listed as DONE in the whiteboard. Same with system-printer-config

    Can you point me to a publicly archived discussion with rhythmbox upstream concerning the indicator patch for rhythmbox? Or the system-printer-config upstream? I’m having trouble finding them.


  • jono

    Those discussions have not really started in earnest yet. Rhythmbox, Tomboy and system-config-printer (which is now going to be postponed) are demo apps that show off C, Mono and Python respectively.

    The patches are available in the Lucid archive and also in the Karmic PPA at

    We are still somewhat at the beginning of the discussion. We will be talking with each of these upstreams in detail throughout the cycle.

  • Jef Spaleta

    Okay the “demos” are done. The blueprint doesn’t make the point these are meant to be demos. Is there a timepoint in the Lucid process by which a decision is going to be made as whether or not these “demos” are going to be part of an LTS release? It seems pretty unwise to commit to shipping “demos” as part of an LTS release before a sincere effort to discuss this with the relevant upstreams…even if its just a heads up that you are experimenting with a significant functionality patchset.

    You’ll pardon me if I’m not particularly big admirer of seeing significant functionality patches to applications bitrotting in launchpad instead of being submitted to the relevant upstream project for discussion.


  • jono

    Jef, when I say demos I meant that they are first apps that show off this functionality, and yes, they are incomplete, mainly because the application-indicator code was completed last week and is still baking, and the apps have only just been ported over.

    Of course we are not going ship incomplete functionality in an LTS. I hope my explanation above clears this up.

    As for patches bitrotting in Launchpad, I think you may be jumping the gun – the Rhythmbox patch was written last week and the Tomboy patch was written today. I know you are a critic of our work, and generally look at our work from a glass-half-empty perspective first, but we are really early in the cycle and we are working hard to genuinely make a great contribution to this problem. It will though take some time for us to get all of our ducks in a row.

    In terms of our upstream relationship, a significant chunk of Jorge Castro’s (who is on my team) work is engaging with upstreams regarding this technology. I am overseeing this work and we are committed to having the best possible relationship with upstreams.

    Thanks, Jef.

  • Jef Spaleta

    You have it all wrong. The glass isn’t half empty nor half full. Its completely full… half liquid and half air. I just don’t take the air for granted. Fun fact its the air in the glasses that transmit the sound waves when playing music on a glass harmonica. And if you haven’t heard Nine Inch Nails’ Head Like a Hole played on a glass harmonica you haven’t lived.

    Sure get your ducks in a row… but give upstream the opportunity to weight in while the work is going on. Don’t wait till your happy with the UI and then drop it on upstream expecting them to agree with your design decisions after its baked-in to the point where you team is unwilling of changing the design.


  • Lucid Community Team Review | jonobacon@home

    […] the start of the Ubuntu 10.04 Lucid Lynx cycle I blogged about these plans for my team in Lucid. They included these […]