This is an accomplishments system that can be used to identify when people have accomplished various things in the Ubuntu project and reward them with trophies. The plan also makes additional skills and accomplishments more discoverable and provides better help for people to get started. While designed for Ubuntu, the system can be used for other projects and also for local applications (e.g. completing Level 1 on a game). Accomplishments in community projects are verified for their integrity so people can’t fake their trophies.

I wanted to present a video demo of the system working so far:

Can’t see it? See the video here!

You can find out more about the project here and the code is available in the following branches:

• lp:ubuntuaccomplishments – contains the main trophy viewer app, the daemon, and the libaccomplishments Python module.
• lp:~jonobacon/ubuntuaccomplishments/ubuntu-community – a collection of Ubuntu accomplishments for different things you can accomplish in the Ubuntu project. There are only two accomplishments right now – can you help write more?.
• lp:~jonobacon/ubuntuaccomplishments/validation-service – the server-side verification service that runs on an Ubuntu One headless machine.

Now, this is really early in the stages of development. If you grab the code you will find various bits that are not yet implemented, but the core idea works.

Things we need to do next:

• Generate the user’s trophy directory and share it with Ubuntu One. I have the code written to do this, I just need to merge it in.
• Add a Getting Started page which asks the user if they want to use verified trophies that use Ubuntu One.
• Fix support for machine-verifiable trophies that are dependent on others.
• Actually sign the trophies.
• Implement the categories filter in the My Trophies view.

I plan on writing a longer blog entry about how the system works later for those who are interested in contributing.

I thought this could be of general interest to the community, so I figured I would write these things down into a blog entry. So meta.

Some tips:

• Keep it concise – your blog should get the point and talk through the topic you are presenting. Now…seasoned readers of my own work will know I tend to ramble from time to time, so I myself always need to try and keep this in check. Few people will want to commit to a huge block of text, so keep it concise.
• Format it – the web has many wonderful things, and this includes formatting such as italic, bold, code, different heading sizes and more. Use them to help add emphasis to your posts.
• Make it visual – pictures say a thousand words, and so do videos. Break up your content with images illustrating what you are discussing, or just amusing images to make a joke (example). If you want to display images, I recommend you upload them to Flickr and then link directly to the images. For videos you can usually embed them directly from YouTube or other video sharing sites, but aggregators such as Planet Ubuntu often strip out the embedded videos, so be sure to provide a direct link underneathe the embedded video (example).
• Link to interesting things – if you are discussing something online, always provide a link to it. This helps the user get access to the information quickly and easy.
• Be professional – always keep your posts professional and thorough. Ensure your writing is clear and that you have spell and grammar checked it.
• Be fun – being professional doesn’t mean you can’t be fun. Writing in a fun and amusing way is a great way to keep your readers interested.
• Invite discussion – if your blog has a comments feature, always end your posts and ask for input and opinions from your readers. This provides a wonderful way to trigger some discussion around your post.

In terms of blogging more and getting more eyeballs on your posts, here are some tips:

• Get into the habit – to become a regular blogger you need to get into the habit of thinking “this is cool, I should blog about this“. This can take a while to get used to. If you are in a team, it is helpful to suggest to others when they should blog about something; this keeps us all regularly posting. If you are struggling with getting into the habit, put a reminder in your calendar to remind you.
• Ensure you are aggregated – if you are an Ubuntu Member, be sure to add your post to Planet Ubuntu. Add your post to other appropriate aggregators (e.g. Canonical staff should add their blogs to voices.canonical.com).
• Use social media – post a link to your post on Twitter, Google+, Facebook and other social media accounts.

I am sure there are plenty of other suggestions from you folks; please add them to the comments!

From 2nd – 4th March 2012 we will be running the Ubuntu Global Jam. This is a global event in which we ask Ubuntu users and contributors to organize events in their local areas to meet other Ubuntu people and help contribute to Ubuntu.

The Ubuntu Global Jam is a fun event, and a great way to meet other Ubuntu and Free Software folks. It is also really easy to organize an event if there is not one near you.

To explain more, tonight I created a video explaining what the Ubuntu Global Jam is, and how to organize an event:

Can’t see it? Click here!

We are going to be encouraging you good folks to start organizing your events. You can find out more about the events here at loco.ubuntu.com and more information on the wiki.

Please feel free to ask whatever questions you like about how to organize an event in the comments here. Do let me know if you organize an event!

Mike is also working on some website updates on loco.ubuntu.com that will make the event a little more interested both before and when the event is running.

Sponsored by Colgate.

L-R: Daniel Holbach, David Planella, Yours Truly, Jorge Castro, Michael Hall, and Nicholas Skaggs.

Google Hangouts are awesome for team meetings.

When you load the app it shows you a list of the available opportunities you can achieve:

(obviously a bunch of these are dummy ones).

You can use the combo boxes at the top to choose which types of opportunities (e.g. Ubuntu Community, Ubuntu UK LoCo Team) you want to view, as well as their category (e.g. Ubuntu Community could have categories such as QA, Development, Advocacy).

Some of the opportunities have padlocks on them. This means that you need to complete another opportunity before that one is unlocked. This helps provide more of a logical journey of things that you can do.

Part of the goal of the accomplishments project is to provide better, more contextual information for how to get started doing something. As an example, if you are curious about the Filed First Bug opportunity, you can double-click it to read information about how to complete it and where to find help:

Obviously this information can be improved (and particularly the links, they are just dummy links). We would also want to add nice things like clicking on an IRC channel and it loading in an IRC client.

The Filed First Bug is a real working accomplishment. When you run the scriptrunner (part of the prototype, but not tied into the GUI yet) it will run the accomplishment’s script and check Launchpad to see if you have filed a bug. If you have, a small notify-osd bubble appears and you can see your trophy in the My Trophies view:

In the real implementation the scriptrunner would run as a service without you having to run the app to start it.

I am pleased with the progress I am making. Next I want to get some more example accomplishments tied in and then I am going to start looking at building the verification service. Should be fun!

I am certainly not presuming that this documentation was as a result of someone reading my blog post; I assume I didn’t see it online before, but thankyou to everyone who has contributed to it.

In terms of general team progress, this is how our burndown chart looks today:

I asked each of the guys on the team to follow up with their respective community members to start moving the needle on those work items. As such, if you committed to something in 12.04 for our team’s burndown, expect Jorge, Daniel, or David to come knocking on your door soon.

With Nick and Michael joining the team recently, their work is not reflected in this burndown – their work will appear in the 12.10 burndown.

Developer Growth

Daniel’s core focus in this cycle is developer growth. The first step here is ensuring that our developer processes are working effectively. Over the holiday period the sponsorship queue got a little out of shape, so I asked Daniel to work with the patch pilots to get this back on track. Good progress is being made:

You can see how the queue is falling back down at the end of the graph since Daniel started hammering on this over the last few weeks. Thanks to all the patch pilots for their hard work.

Daniel has also been fixing up some metrics so we can track this work more effectively, and putting together a developer outreach team to provide a more personal level of support to get developers through the process. He will be speaking more about this in the coming weeks.

Cloud and Juju

Jorge is focused on growing the Juju charming community and is making great progress. A tour of events is planned and Jorge has a hit-list of upstream projects which he is focusing on to get charms put together for. We are seeing good progress on this list and I am confident Jorge will hit his goals in this cycle.

Juju really is awesome. You should check it out.

App Developers

David has been focusing on app developers in this cycle. A first chunk of work here is helping the App Review Board to get in shape. The ARB has a large queue of content to get through, so in Budapest we sat down and dissected the ARB process and made a bunch of optimizations. David has been coordinating with the team to help coordinate this work, and we are seeing progress happening.

We have recently seen three lenses get through the ARB, and David is going to be starting a regular cadence of queue reviews to keep the ball rolling. Thanks to the ARB for all your contributions.

David originally planned a Phase II set of additions to developer.ubuntu.com, but with some re-structuring from the Canonical web team, those plans have been put on hold a little. Instead d.u.c is now being put into maintenance mode and we identified a set of things that need fixing (particularly on the publishing side), and David is coordinating those changes.

The next chunk of work will be outreach to grow our app developer community. Stay tuned for more…and an up-coming competition…

Upstream Relations

Michael is the new upstream community coordinator, and will be focusing on Unity in particular as he gets started. I have asked him to first work with the Desktop Experience team to help get their community merge proposals in shape. There are a number of branches that have been sitting around for a while, and Michael is coordinating a patch pilot scheme to ensure these get reviewed regularly. We expect to see this in place over the next week.

Michael has also been performing an assessment of Mozilla’s SUMO for a potential solution for help in Ubuntu. He has put together an extensive report and a test instance to play with and he will be working with the docs team to continue assessing this as a solution. I am excited to see what work happens here.

Finally, next week we will be putting together an upstream target list for Michael to reach out to to start engaging app authors more effectively around our technology. I am excited to see this work progressing.

…oh, and one other thing: Michael is working with Didier to merge Singlet into Quickly. This should make creating Unity lenses a piece of cake. Bring it!

QA

Finally, the latest addition to the team has been Nick Skaggs. Nick has been working with the QA around a few core pieces of work:

• Getting our manual test infrastructure in place. We are going to be piloting Case Conductor as a solution that will fit alongside Jenkins.
• Consolidating our QA community teams. Nick is evaluating our current QA on-ramp and then we will put together a proposal for bringing more efficiencies and consistency to the QA community.
• Building a take-and-bake testing process so Ubuntu Engineering can reach out to Nick to facilitate community testing more effectively.

The former two items will take time to put in place, but the latter item should be in place in the next week. As such, you should see a regular stream of testing campaigns driven by Nick in 12.04. Be sure to keep an eye on his blog.

. . .

Of course, there are lots of other things going on, but these summarize some of the key themes.

The Ubuntu Developer Summit (UDS) is the most important event in the Ubuntu calendar. It is where we get together to discuss, design, and plan the next version of Ubuntu; in this case the Ubuntu 12.10 release.

The next UDS takes place at The Oakland Marriott City Center, Oakland, California, USA from the 7th – 11th May 2012. You can find out more about why UDS is interesting from the perspective of a member of the community, an upstream contributor, and a vendor. We also welcome everyone to participate remotely if you can’t attend the event in person. More more details on how to get there, see this page.

At the heart of a great UDS is a diverse group of attendees who can bring their experience and expertise to the discussions. You don’t have to be technical, or be a programmer or packager to attend – UDS is open to everyone (including non-Ubuntu folks) and free to attend. We encourage everyone with an interest in Ubuntu to attend.

Sponsorship

For every UDS Canonical sponsors the hotel and accommodation of a set of community members to ensure they are free to contribute and bring value to the discussions. We have a limited budget so we can’t sponsor everyone, but we are always keen to have a capable and diverse group to sponsor:

• We strive to support community members who are actively involved in Ubuntu and who are providing significant and sustained contributions to the Ubuntu project.
• We always welcome Upstream contributors who are bring value to Ubuntu indirectly via active participation in their upstream project, but who are keen to see quality support for that upstream in Ubuntu.
• Contributors are willing to actively participate not only throughout the full Ubuntu Developer Summit week, but also following with active contributions throughout the release cycle.
• We are always keen to welcome members of the community who have never been to UDS before and are keen to participate and experience the event.
• You don’t have to provide technical contributions to apply – if you have participated in the areas of advocacy, documentation, testing, art, design etc, you are encouraged to apply.
• UDS is an event that encourages diversity – we welcome everyone to apply for sponsorship, irrespective of gender, race, impairment, technical expertise, or other factors.

If you are participating in the Ubuntu community, we would love you to apply for sponsorship. This is how it works:

1. You can apply for sponsorship by following these instructions. Apologies for the different forms you need to fill in – we are going to consolidate these forms at the next UDS. The deadline for submissions is Wed 22nd February 2012 so be sure to get yours in!
2. When the deadline is reached we will assess the applications and finalize who we will be able to sponsor.
3. You will then receive an email outlining whether we can sponsor you or not.

Simple! I look forward to seeing your applications, and seeing many of you in Oakland!

Can’t see it? See it here.

I wanted to point you folks at Nicholas’s blog post about how to test the HUD. You will need to be running Ubuntu 12.04 (which is still in development) to test.

We would like to encourage everyone to test so we can get this rock-solid for 12.04!

Fortunately (or unfortunately, depending on your view), I have had Python and GTK to serve my needs here. Python, with it’s awesome batteries-included range of facilities and GTK as a simple yet flexible toolkit has allowed me to create implementations of the ideas that I have dreamed of. I started using these tools many years ago, and they have always provided a simple and effective toolset for me.

My preferred toolset of choice. One day…

Having not written any code for a while, I got the itch this weekend to start writing the trophy helper app that I wrote about as part of the accomplishments system spec that I created with Stuart Langridge and Daniel Holbach. I thought this would be a good opportunity to brush up on my skills, given that PyGTK is dead and the new world is instead the GIR approach to GTK. In a nutshell, this is where the language bindings basically match the C API for GTK thus reducing the need for people to maintain different language bindings.

Of course, this is a good thing: less work for volunteers in maintaining multiple-language support for GTK and a consistent API is good. Unfortunately, I found getting started with this new world a little more complex than I imagined.

From reading the documentation it suggested that all I needed to do was to import Gtk from gi.repository and instead of creating widgets with gtk.<foo> that they would be Gtk.<foo>. The docs suggested a few other lexical adjustments, but not much more than that. There is even a pygi-convert.sh script that can convert older PyGTK code over to the new PyGI way. Unfortunately the script didn’t work for me, so I instead used it as a cheat-sheet for things that needed changing. Sadly, it seemed like some things were not covered in the script.

An example of this included when I was creating a ListStore. In PyGTK code I could add a gtk.gdk.Pixbuf to the ListStore for an icon, but I had a difficult time trying to figure out the new way to describe this. I tried Gtk.gdk.Pixbuf and Gtk.Gdk.Pixbuf but had no luck. Fortunately the awesome Ryan Lortie informed me that it needed to be GdkPixbuf.Pixbuf. Another example of this was gtk.SORT_ASCENDING in my original code and the new Gtk.SortType.ASCENDING in the new code. It seems like various functionality in GTK has been moved around and re-factored.

Unfortunately I could not find any documentation to help me with this. Sure, the C docs are available online, but I am not a C programmer; I am (in the most generous and understanding way) a Python programmer and where I previously had a pretty decent tutorial and reference guide to PyGTK, as a desktop app developer I no longer have these resources to help me. Even though I am not a fantastic programmer, I have written enough Python and GTK code to fumble my way through writing various apps, and if it stumped me as a relatively old hand, I wonder how a brand new developer would get on.

Pictured: old hand.

Now, this may sound a little critical, but it is not mean’t to be. I have tremendous respect for the GTK team, and I am hugely thankful to them for all their hard work. I am also thankful for the team that has worked on the GIR support so that multiple language support can be more efficiently provided. Thanks to all you folks for providing great tools that let a programming numpty such as myself be able to write Free Software.

I just wanted to share this because I feel like these tools are missing the final component: if we had a good solid set of reference documentation generated for each language (naturally, Python is the language I mainly care about), this would help novice and established developers use GTK more effectively. From my personal experience, my patience started wearing pretty thin when I felt like I didn’t have anywhere to find help as I navigated C documentation to try and figure out how the API fitted into my Python application. A good solid Python reference manual would have resolved this issue, and from what I understand, this could potentially be generated from the GIR files. Unfortunately, I don’t think I have the skills to help solve this problem, so I figured the best I could do was to share my story and see if anyone would be interested in helping to solve this problem.

If so, thanks in advance, and thanks again to the GTK team for all your hard work!

Update

I found this excellent documentation after publishing this entry. This provides exactly the kind of documentation I was looking for. Thanks to anyone who helped contribute to this!