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!

Share This
%d bloggers like this: