I’m posting updates later and later every day. Right now, I’m in community round table and I’m writing a blog post, sigh, procrastination - how I love thee
I ran into some audio issues and power went out half an our into the session, had to step out to an internet cafe and get back into the connection. We also reminded ourselves that people who become Canonical employees don’t automatically become ubuntu members or get upload rights. They still have to go through the same process and don’t have corners cut if they don’t have a proper wiki page.
I’ve heard about this team and it was nice to join in to their sessions. We made a bunch of decisions including having more regular meetings, perhaps once a month. Jonathan came up with an idea about Manifest, he’ll be writing to the mailing list about that stuff. I had this idea about having documentation for NGO to set up Ubuntu on their infrastructure and how to migrate to them. Eventually, Penny and I’ve volunteer to do this action. A bunch of more actions were created and assigned out including creating a Facebook group and exploring a planet for NGOs.
I feel that this idea is great. The Ubuntu Manual team intend to put the information from a wiki into a website. This site would also be translatable. Now, the Ubuntu Manual Project is a direct competition to the doc team. Martin (I think) brought up the point that the manual team should be collaborating with the doc team instead of competing because there would be a bunch of duplication that doesn’t make sense. So, the action plan is to give the feedback to doc team what made the manual team successful and perhaps integrate that into the ubuntu doc practices
The second session about the development workflow. This was as productive as the first one. Among the suggestions was a tool to make patch from a file on the system:
So, the proposed tool finds the package that owns the file, grabs the deb, makes a diff of the files installed vs. in the package, and makes a bug/uploads patch against that package. If we have something like it, that would be really cool. Another point was advertising how to get fixes into Ubuntu in Launchpad, a small text showing, “Do you want to fix this bug?” or something to that end. A lot of the talk was focused on the persona of someone who knows a language and fixes a small bug and wants to get the fix out, but not necessarily interested in ubuntu development.
This was a very interesting plenary which I could experience to any extent thanks to James Tatum posting pictures of the slides onto IRC channel. I hope the video team posts videos of this stuff! A lot of the work that Dr. Chevalier presented was using slow animation to display revision changes to code or text. The immediate application I could think of was scanning commits in bzr or git and also looking at wiki edits.
Most of the community sessions were very interesting and this was one of them. I think having folks in the room that you know and know you changes a lot of things. We started with discussing what didn’t work and how we can improve stuff this cycle. Most significant decision was to make Developer Week earlier in the cycle and rename Opportunistic Developer Week to Application Developer Week.
I was having dinner during listening to this session. It was nice to know what’s coming in the next cycle. The ability to write reviews and have sale of software is very promising.
This session was working into thinking what is going wrong with this and who has issues with this processes. A lot corner cases were discussed and it was kind of nice. The best part of UDD is that its easy to get the maverick (or any release) source code.
So, this overview was very late, we’re into half the day 3 and I’m still doing this stuff. If you haven’t looked into the Ubuntu Developer channel on blip.tv, now is the time to do it. New videos are being added daily.