standard live blogging warning
I’m here at TheTeam offices in London Bridge, with a number of my Osmosoft colleagues for this open source event.
- Iain Farrell, Canonical - Ubuntu Update
- Julien Fourgeaud, Symbian - Managing the Symbian community
- Jeremy Ruston, Osmosoft - HTML5 and the slow death of Flash
- Leisa Reichelt, Disambiguity.com - Drupal 7 Update
- Phil Hawksworth, The Team - Playing with each others toys: Developing with open technologies
- Rain Ashford, BBC - Open Source Gaming for Handhelds
- Robbie Clutton, BT - iPhone development using web technologies
Canonical: The Ubuntu Developer Summit
Iain explains the process of updating Ubuntu. Happily enough, the release cycle is 6 months, coinciding nicely with these OSSAT events, hence the trend is set for an update each OSSAT.
Every 6 months, there’s a big Ubuntu shindig; this is (I think) just after the last release ships. All ~240 employees invited and ~30 invited people from the community. Room for talks - the schedule is always evolving even during the conference - and spaces for just hacking. Very online too for those who can’t make it - stereo recording in every room. All the audio, mixing, publishing, and so on is power by the magic of open source. Naturally.
The design process is generally speaking 6 months ahead of the development process, i.e. in cycle t, they’re thinking about what they’ll be developing in cycle t+1. For users, a 6 month cycle means lots of incremental improvements, as opposed to
Julien Fourgeaud: Symbian's Community Programme
Nokia started as an alliance and Nokia then purchased Symbian Ltd. When that happened, there was a move to open source the code. Julien explains the ecosystem - 90 people maing up the foundation (people in US, UK, Finland, Japan, China, elsewhere) - working with a large community of consumers, ODMs, OEMs, and operators. They often run BOFs embedded in other conferences.
What’s Symbian doing to get consumers what they want? They’re creating initiatives to get agile and engage in dialogue going with consumers. [I would have liked to see more on this, but it sounds like they’re just at the start of the path here.]
Of possible relevance to the next talk, Symbian’s portal is a Flash-heavy representation of standard web technologies such as hyperlinks …
Jeremy Ruston on HTML5 and the Slow Death of Flash
Jeremy points out he’s dogfooding by presenting in Cecily, his 3D zooming and panning interface powered by open web technologies. He points out the anti-Flash vibe isn’t new, with Jacob Nielson having declared Flash “99% bad” back in 2000. A few of the problems with Flash are:
- Battery drain
- Can’t exploit hardware acceleration (except video and certain blitting operations) - the operations of HTML5 have been designed to take advantage of it
- Big opaque ball of bits - can’t reach in and get at the data/content inside
- Controlled by media interests (e.g. to ensure ads are watched)
- Breaks the web UI, e.g. browser navigation, text selection, accessibility
- Not properly open - the license stipulates for what purposes you can use it (restricts uses such as downloading video)
- Not compatible with open source - can’t ship as part of open source; so a pain for users as it requires a separate download.
He walks through the history of Flash. He explains there was a time when they looked quite innovative, but it’s become more closed systems and walled gardens, with silly license fees. So a young person who wants to get into the industry is required to pay 500 quid to get started with it.
In Q&A, @psd points out that Flash lets you make nice toys, but HTML5 lets you build something better than Flash, i.e. the data inside there.
Drupal 7 Update
Leisa Reichart explains the design work going on with Drupal 7. Where most open source (including Drupal) is done bottom-up, grassroots, stuff, there’s an element of top-down design here. Leisa’s talking about “open source design” (#d7ux), where she’s spent around 85% of her time engaging the community to help with design, rather than just doing it herself. The community includes end-users, agencies whose customers are using the CMS, and also other designers and usability studies. (Reminds me of the message in the community session at OWF - don’t just engage programmers, but also translators, designers, tech writers, etc.)
They set up a WordPress, yes WordPress, blog to act as the community portal; because (a) Drupal takes too long to get a very nicely designed blog; (b) it sent out a message to the Drupal community and got them engaged.
She also shows a nice eye-tracking study, something you don’t see much in open source land.