Perth, Western Australia - 6th to 10th January 2014

<-- Back to schedule


As an increasing number of applications and services shift to “the cloud”, close attention needs to be focused on the platforms that deliver these services to their users. From a user’s perspective, the browser implements the web platform. Therefore, it’s important that there is open community-driven discussion about the browser development process.

Browsers are hard - they must support a family of incredibly complex specifications, provide a safe user environment in the presence of scripts, maintain backwards compatibility for old specifications and features, and allow multiple complicated web-apps to run in parallel while remaining performant. With the range of services now exposed by the web, browsers have been likened to operating systems, and some projects, such as Google's ChromeOS and Mozilla's Boot to Gecko, are attempting to make this analogy a reality.

The Browser Miniconf is an opportunity to provide a focal point for discussing issues related to the development of open-source browsers. Several open-source browsers exist, and the three most popular rendering engines (Gecko, WebKit and Blink) all have vibrant and active communities of hackers in the Australasian region. This miniconf will allow those communities to meet and exchange ideas. Further, the miniconf will provide an access point for open source developers to discover more about the various browser efforts, and an introductory point for those developers interested in improving web browsers.

Like last year, the Browser Miniconf will accept talk proposals in the following areas:
* browser internals, from birds eye right down to deep detail. Example titles: “1000 foot overview of the Firefox code-base”, “implementing accelerated compositing of layers in Blink”
* integration of browsers with platform libraries and distributions. Example titles: “exposing Gecko to Gtk+ developers”, “why distros and browsers can’t all just get along”
* The browser development process. Example titles: “open source browsers, standardisation, and the web”, “Hacking Chrome - how hard can it be?”, “Why is the browser like a kernel?”
* browser landscape / history / wars. Example titles: “Why did javascript just get 10x faster, and why does it matter?”

A note about the organizers: Cameron McCormack is a Software Engineer at Mozilla working on Gecko’s SVG implementation and participating in a number of Web standards efforts. Shane Stephens is a Software Engineer working out of Google’s Sydney office, concentrating on the new Web Animations specification as well as its implementation in Blink. Cameron and Shane are excited about increasing communication between the various browser developers in the Australasian region, and about attracting more interest and new developers to browser development efforts.

Shane Stephens

Shane is a Software Engineer at Google, and a member of the Chrome team, working on the Web Animations specification, polyfill, and implementation in Blink. Shane has been involved with the open source community since university.

Shane's previous FLOSS-related projects have included liboggplay, which is a library for synchronized playback of ogg media; the Annodex Firefox plugin; and the Google Wave project as part of the API team.