There are still some dependencies on Py2 in the image. Let's see if we can port them to Py3 this cycle.

In the world of Snappy Ubuntu Core, interfaces allow snaps to communicate or share resources according to the protocol established by the interface. Find out more about everything works and discuss how to get more interfaces implemented.

After its first release in 15.04, almost every bit in the codebase has changed and the list of improvements is huge. Developers of the team will take some time to talk you through the changes and what's planned. There's going to be time for questions as well.

In a smaller group we started a project called snappy-playpen a few weeks ago. The goals were manyfold: we wanted to snap softare, learn more about snapcraft, find issues, create good examples and collect common recipes for common cases. We'd like to extend this scheme and open it up, so we'd like to talk about workflow and additional new ideas.

Snapcraft is easy to use and has come a long way already. In this session let's talk about its future, your ideas and what's coming up next.

Most of the documentation around Snappy and Snapcraft is written during the development process of both. Let's discuss what is still missing, what needs updating, what needs to be clearer and discuss next steps together.

Snapcraft comes with the promise to make publishing of software super easy. Let's take a look at the snap workflow, how it works, how to get started and a few examples together.

A typical Ubuntu system contains a number of daemons and applications that will happily log to syslog or to a variety of other destinations. Some of these messages are errors that perhaps should not be showing, others may be genuine issues waiting to happen. Some more may just be totally superfluous information for the average user, and only contribute to wasting more space on disk. We should spend a bit of time reviewing logs on one or a few representative sample(s) for the various flavors of Ubuntu we ship to find areas of improvement.