This blog post is the seventh in a series of many that I will be posting about UDS, the Ubuntu Developer Summit.
One thing I've realized is that it's very difficult to capture the firehose of discussions, sessions, and otherwise interesting content from UDS into one coherent daily blog article. So rather than documenting a play-by-play, I'll likely jump around and pull highlights from areas that I'm focused on into shorter summaries.
Day 2 of the Ubuntu Developer Summit was even more jam-packed than the first.
Meet The Ubuntu Desktop Designers
I think this was one of the most interesting and professional sessions sessions of the day. The awesome Alison Randall facilitated a discussion between the remarkable design team (Otto, Christian, mpt, Mika, Stuart, John) and community folks to talk about ways to engage with the community. A lot of the design process is indeed done in close physical proximity. As a result the design team can appear opaque. They aren't generally online and in IRC. As a result, this frustrates some Ubuntu contributors and there's a pent up demand for information about how design decisions are made and the process. We see some of this frustration from our vantage point as disparaging comments about Unity, which I've blogged about before.
There will be some follow-up communications from the team I'm sure. They seem committed to communicating more frequently and with greater transparency.
In the meantime I encourage everyone reading this to check out their blog:
Hmm.. on second thought, please subscribe to it.
What are your thoughts? What can the design team do to help you understand both the process and the outcomes?