The Snappy Sprint in Heidelberg came to a close yesterday. Here are my thoughts, and a little background about the event, for those of you who've contacted me with questions.
First some background as to how this Sprint was organised. There were three tracks running, each broken down into sessions lasting between 45 mins to an hour. Each afternoon there was the option to participate in a 2 hour hacking session or continue to follow the other sessions. Trello was used to keep the session time table up to date. Wednesday evening we all had a meal together, lightning talks (mostly from the non-Ubuntu invitees) and an evening of hacking.
My first observation is the invited community contributors were warmly welcomed, had access to everything and were encouraged to participate, be it discussion, design or code. It was an inclusive and productive environment. ☺️
I mostly followed the community and cross distro track, but did dip in and out of some of the snapd, snappy core, +Snapcraft
and snapweb sessions. From outside Canonical there was participation from AppSteam, +Arch Linux
, +Blue Systems
, Debian, +elementary
, +Fedora Project
, KDE, +MATE Desktop
, nextcloud, +openSUSE
, OpenWRT and VLC. And just to be clear, all the representatives are leaders and decision makers for their respective projects.
At the end of day one the discussions that had taken place in the community/cross distro track were described as "intense" by +Mark Shuttleworth
in the daily wrap up. Linux distros have different missions and the desktop environments have different user experience stories. But even on day one, it was apparent we did all agree on something fundamental. Snaps enable us to deliver the best software we have to offer in a secure and predictable manner, everywhere.
On day two, the ideas started emerging as to how the different projects could leverage snaps and by the end of the week firm plans, initial code and in some cases final solutions were in place. The level of collaboration has been brilliant. The existing snap capabilities have been explored and some new limits discovered along with plans/proposals that outline how to overcome them. There was a particular focus on a new Snappy feature called Content Sharing, which is the mechanism by which shared platform/runtime snaps are made possible. A platform snap for GNOME 3.20 is nearly complete and the race is on to see if I can land the MATE 1.15 platform snap first 😉
I've left the Snappy Sprint with a clear understanding of the road ahead, an enthusiasm and commitment to be a part of the snap journey, and most importantly, some great new friendships. Keep your ear to the ground about snaps, there is certainly big news to follow in the not too distant future... #snappysprint