Ubuntu Community Team Meeting Tomorrow
Just a quick reminder that tomorrow (Tues 25th October 2011), the Canonical Commmunity Team will be having our regular weekly meeting on IRC at 8am Pacific / 11am Eastern / 4pm UK / 5pm Europe. The meeting will take place in `#ubuntu-meeting` on the [freenode](https://freenode.net/) IRC network. If you can’t join us, the log will be available [here](https://irclogs.ubuntu.com/).
On a related note, if you are interested in how our community functions and helping it to prosper, be sure to join the `#ubuntu-community-team` channel; that is where we all hang out. It is a fun place to be. 🙂
Ubuntu Accomplishments System Spec
Some time ago I was kicking around some ideas about how we reward our community for different types of contribution. While Launchpad karma is useful for indicating who has been working on code, bugs, translations, and specs, it doesn’t cover a wide variety of community contributions and is also not a particularly exciting way of visualizing these achievements. I believe that many folks really want to feel a sense of ownership over their accomplishments, be it as simple as reporting a bug or as complex as contributing a package upload.
As such, I started developing some ideas around a trophies-like system for Ubuntu contributions. I was keen though for this not to be a *pointless achievement* system. As an example, contributing *100 bug comments* is not necessarily and indication of an accomplishment, but instead an indication of *traffic* (all those comments could be garbage). I think it is much more important for such rewards to be tangible affirmations of a quality contribution. As such, this system is called an *Accomplishment System* and is more focused on things you do in Ubuntu that are accomplishments in your contributions.
Fortunately, around the time of having this idea, [Stuart Langridge](https://www.kryogenix.org) was visiting Erica and I with his daughter. We did what we normally do: stay up until 4am discussing an idea and fleshing out the details and then I started writing everything down into a document. We then discussed it with [Daniel Holbach](https://daniel.holba.ch/blog/) and I discussed it furthewr with Randall Ross (LoCo community) and Jim Campbell (Ubuntu Docs Team) and at that point the idea stalled while we got busy with the release.
I now want to present the idea thus far with you all and to invite discussion, and more importantly, to motive some of you coders who are interested in the idea to consider writing some code to implement it. Stuart wrote a proof of concept which is something that could be built upon.
To get things rolling, I have [put the spec so far on the wiki](https://wiki.ubuntu.com/AccomplishmentsSpec), complete with all my mock-ups, and I [registered a blueprint for a UDS session](https://blueprints.launchpad.net/ubuntu/+spec/community-p-ubuntu-accomplishments-and-trophies) which I hope to see some of you participate in.
If you are interested in implementing this vision (particularly if you are a Python coder, let me know in the comments!
Ubuntu Community Survey Next Steps: Leadership
*This post is part of a series of posts discussing next steps based upon findings in the [Ubuntu Community Survey Report](https://archivedblog.jonobacon.com/2011/10/24/ubuntu-community-survey-results/) that was released recently. The goal of these posts is to focus on solutions, and I would like to encourage your comments and discussion to be focused on areas in which we can drive solutions forward*.
Let’s first discuss leadership. In the context of the community, leadership can span many different groups: the Community Council, the Technical Board, Team Councils, Canonical team leaders, and of course our SABDFL, Mark Shuttleworth.
I believe that leadership can be broken into two broad areas of focus:
1. How accessible leadership positions in Ubuntu are (i.e. how empowered people feel to become a leader).
2. How effective our leaders are at leading, motivating, and inspiring our community, and how equipped they feel to lead.
Let’s discuss these more.
## Accessible Leadership Positions
In terms of the former, when asked about whether the respondents see themselves as leaders (**45%**) *sometimes* do and **26%** *definitely* do. Following on, **59%** of respondents were interested in becoming a leader in the Ubuntu community, and most respondents (**46%**) felt empowered to apply for a leadership position.
It seems that there is definitely a thirst for pursuing leadership positions in Ubuntu and I would like to investigate ways in which we can help our community feel more empowered to approach these positions. From looking at some of the reasons why people don’t feel empowered, it includes:
* Lack of time (busy with family/personal things) — this was highlighted as the primary reason.
* Lack of interest in participating in leadership.
* Some highlighted that they were unaware of when new members are required for leadership positions.
While complex, I think we can improve the former two reasons here. For the first one, some people expressed that leadership meetings were at inconvenient times (e.g. during working hours) so we could explore other ways of leadership boards meeting and making decisions (e.g. reviewing decisions on a mailing list). In terms of lack of interest, I personally feel we could explore options of better articulating the importance of leadership and the role it plays in Ubuntu. We have general descriptions of each of the boards, but I suspect we could provide a more inspirational description of these boards; I feel like we don’t really *sell* the important function of leadership in our project, and we can improve this somewhat. Any thoughts on how we do this?
For the latter point I wonder how we can better communicate out when leadership changes are required, and maybe better inform around the expectations and opportunities of the different leadership positions. Any thoughts and ideas on how you think we could improve this?
## Helping Our Leaders To Be Effective
One interesting piece of data from the survey was the kind of topics our community would like to see from our leaders. They include the following (in priority order):
* Communicate about leadership and decisions more
* Recognize contributions and help improve recognition
* Helping people to succeed
* Listen to input from the community
* Provide motivation
* Improve Canonical/Community relations
* Improve Ubuntu processes
* Provide direction
* Identifying where people can help
* Bring in more contributors
I think each of these different areas are valuable areas in which our leaders should empowered to lead and it would be useful to discuss approaches to how our leaders can feel equipped to advise and resolve issues in these areas. More in this in *Next Steps* below.
One area that I did not inquire in the survey is how effective the leaders themselves feel at leading, but my email and phone research has suggested that sometimes our leaders don’t feel motivated to lead as much as they would like. Some of this feedback suggested that leadership positions sometimes feel more administrative (merely approving/rejecting applications etc). I am keen to see how we can make our leaders feel motivated to lead.
In summary, I see some core areas of focus I would like to explore:
1. How can we make leadership positions more accessible to our general community?
2. How can we improve the motivation of our leaders to feel inspired to lead?
3. How can we better support our leaders with knowledge, guidance, and support?
I believe the best way in which we can approach these topics is to work together with our leaders to explore areas in which we can focus. With our [new Community Council board elected](https://fridge.ubuntu.com/2011/10/24/community-council-election-results/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+ubuntu-news+%28Ubuntu+News%29), I think this could be a good area to focus on initially. More on this below.
One other piece of feedback outlined in the survey was that sometimes the same people are elected as leaders over and over again on our community boards and maybe we should explore term limits. What do you folks think of this?
## Next Steps
Based on these observations I have put in place the following next steps to get the ball rolling:
* [UDS Leadership Mini Summit](https://archivedblog.jonobacon.com/2011/10/17/mini-leadership-summit-at-the-ubuntu-developer-summit/) – I have organized a UDS Leadership Mini Summit on the Tuesday and Thursday afternoon of UDS. The goal of these sessions is to get as many of our leaders together in the same room and discuss topics that help our leaders to lead effectively. I expect we will review much of the content from the survey, but I have also opened a call for topics – you can add your topics [on this wiki page](https://wiki.ubuntu.com/UDS-P/LeadershipSummit). We will review and prioritize the list of topics at the begginning of the first session on the Tuesday afternoon. I expect these sessions to generate some great focus and work for the 12.04 cycle in terms of these leadership challenges.
* [Improving BuildingCommunity](https://archivedblog.jonobacon.com/2011/10/18/documenting-great-ubuntu-community-best-practice/) – in terms of supporting our leaders with guidance and best practice, some years ago I created the [Building Community](https://wiki.ubuntu.com/BuildingCommunity) wiki and back at the Dallas UDS *Chris C* and *Penelope S* contributed a lot of content to the site. Unfortunately it bit-rotted a little, so last week I proposed we work as a community to keep this as a central resource for supporting our leaders and wider community. Today in the new *Ubuntu Leadership Team* meeting we discussed how to focus on this site and the team will be participating in building out the content.
* Supporting our new governors – with the new Community Council board elected I reached out to the group to see how I can more closely align myself and support the group. I proposed having a regular call with a representative of the new board, and I am going to strive to be at their meetings (timezone permitting). I think this will better align the needs of the board with my team and Canonical.
Obviously these are just some first steps, and I am keen to hear of other solutions that you folks think might help. Thanks everyone!
Ubuntu Community Survey Results
Earlier this month some concerns were expressed in a Community Council meeting about some aspects of the Ubuntu community experience. Based on this feedback I [released a survey](https://archivedblog.jonobacon.com/2011/10/07/feedback-welcome/) that went out to all Ubuntu Members to gather some data about views on motivation, pride, leadership, and more. I also invited feedback via other means such as email and I was keen to reach out to many community members on the phone to continue to explore these concerns further.
This weekend I closed the survey off and started collating the results into a report I could share with our wider community. I deliberately made a lot of the questions in the survey open ended to provide as much feedback to the respondents as possible. As such, when collating this data over the last few days I wanted to go through and identify the patterns and themes in the feedback so you folks don’t have to read all the individual responses. This took a little longer to prepare than I expected, but it provides a useful overview of the common themes expressed in the data. For the curious, I have also included the full list of open ended responses in the appendix in the survey.
You can [download the survey here](https://ubuntuone.com/1DWnm1bTcZUcmRs8aAaZ6u) and you only really need to read the first **28** pages; the rest of the document is the full collection of open ended responses included for completeness.
I will be blogging throughout the next week to discuss many of the core themes highlighted in the report and I am keen to hear your thoughts and views on how we can make improvements. I am also going to be registering a series of [Ubuntu Developer Summit](https://uds.ubuntu.com/) sessions to cover these themes in more detail when many of us are together in Orlando in a week. If you can’t attend UDS in person, remember you can [remotely participate](https://uds.ubuntu.com/participate/remote/).
Many thanks to everyone who participated in the survey and now we together have a firmer idea of some of the core themes, we can start driving some improvements forward. I am looking forward to working with you folks in doing this. 🙂
Ubuntu Community Survey Now Closed, Report In Progress
I just wanted to let you all know that the Ubuntu Community Survey I [published earlier this month](https://archivedblog.jonobacon.com/2011/10/07/feedback-welcome/) is now closed and today am writing the results up into a report. I closed it now so I can publish the report and you folks can digest the data in time for us to discuss next steps and solutions at the [Ubuntu Developer Summit](https://uds.ubuntu.com) in Orlando in a week.
I will also be publishing a series of blog posts over the coming week highlighting some particularly interests parts of the feedback and how we can drive forward towards solutions.
Many thanks to everyone who participated and shared their feedback!
Seven Years Old
Seven years ago Ubuntu 4.10, the Warty Warthog, was released. It was the very first Ubuntu release.
I remember when it came out, feeling like this was the right step forward for Linux and Free Software. While the technology looked awesome (removable USB with automatic mounting, woo!), and it was built on the rock that is Debian, the community-orientated nature of Ubuntu right out the gate filled in the complete picture for me.
Since then I believe Ubuntu has become a defining technology, and we have only just begun. Here’s to the next seven years!
Happy birthday, Ubuntu, thanks to Mark Shuttleworth for investing so heavily Free Software, and to Mark and the original Ubuntu team for creating a release that inspired so many of us to develop such a passion to join the Ubuntu journey!
Ubuntu Community Q+A Videocast Today
Just a quick reminder that today (Wed 19th Oct 2011) I will be running my Ubuntu Q+A live videocast. This is an hour of Q+A where all questions about Ubuntu, Canonical, or anything else are welcome. It takes place today at **11am Pacific / 2pm Eastern / 7pm UK / 8pm Europe**.
Taking part is simple. You can join the videocast by [clicking here](https://www.ustream.tv/channel/at-home-with-jono-bacon), but be sure to register with ustream.tv first so you can type in questions. See you there!
Day o’Meetings
Today two important meetings took place in the venerable `#ubuntu-meeting` IRC channel that I wanted to point out.
* Firstly, the first meeting of the newly elected *Community Council* took place. You can [see the log here](https://irclogs.ubuntu.com/2011/10/18/%23ubuntu-meeting.html#t11:00) for the meeting.
* Secondly, my team held our first *Canonical Community Team* meeting on IRC too. We spun through a series of round-tables of what we have been working on over the previous week. It was mainly our team doing to speaking, but as time goes on I suspect other folks will feel comfortable chipping in and participating too. You can [read the log here](https://irclogs.ubuntu.com/2011/10/18/%23ubuntu-meeting.html#t15:00).
As ever you can see the full schedule of community meetings on [the Fridge Calendar](https://fridge.ubuntu.com/calendars/).
Documenting Great Ubuntu Community Best Practice
Our community has a wealth of experience. Different skills, capabilities, life experiences, and perspectives all contribute to a boiling pot of knowledge that when shared can help us all to do great work as part of our different Ubuntu community teams. When we can learn from each other, we can spread this experience far and wide and accomplish even more.
As part of my goal to help support and motivate leaders it struck me that we don’t have as much of this supporting documentation and best practice as we could. Our leaders and wider community should be able to have a dependable set of documentation and resources to help them grow community teams and tend to issues effectively; in essence, a shared knowledge base from the community’s combined insight.
Some years ago I created an Ubuntu wiki mini site called [BuildingCommunity](https://wiki.ubuntu.com/BuildingCommunity) where we set out to document this kind of best practice. Unfortunately, like many people, I got busy with other work, as did others, and the pages have not been updated as often as I think we would have liked.
Tonight I spent some time digging through the pages and cleaning them up a little. There is some great content on there, with two particularly interesting sections I think we could expand:
* [Knowledge Base](https://wiki.ubuntu.com/BuildingCommunity/KnowledgeBase) – a collection of pages, information, tips, tricks, and other guidance for common community challenges.
* [FAQ](https://wiki.ubuntu.com/BuildingCommunity/FAQ) – what was intended to be a growing FAQ of common questions and answers about how to grow, manage, and coordinate a community and team.
Tonight I also created a [Leaders and Governance overview](https://wiki.ubuntu.com/BuildingCommunity/CommunityLeaders) which summarizes how the community is structured; this could also do with some additional content and tweaking.
I would like to put out a call to encourage folks to contribute to refining these pages, adding content, fixing errors, and otherwise helping to produce this awesome shared resource. I also talked today in `#ubuntu-community-team` with Amber, Greg, Benjamin and some others about how we could coordinate some more docs, such as a docs day. Would you folks be interested in taking part in a day to get this resource in shape?
Ubuntu Tat
Benjamin Kerensa from the [Ubuntu Oregon](https://loco.ubuntu.com/teams/ubuntu-us-or) LoCo Team has got something rather familiar inked on his arm:
Badass has a new name.
Wow. Is now the time to tell him we are changing the logo?
Just kidding. Respect, Ben!