I just wanted to provide a quick update on how the team is doing on our set of commitments in the 12.04 cycle. Feel free to ask questions in the comments.
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.
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.
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…
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!
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.