evand

Canonical | REMOTE (Americas) | Full-time

We're growing the Robotics team at Canonical (the company behind Ubuntu):

* Robotics Engineer: https://boards.greenhouse.io/canonical/jobs/1535166

* Robotics Security Engineer: https://boards.greenhouse.io/canonical/jobs/1550997

* Robotics Developer Advocate: https://boards.greenhouse.io/canonical/jobs/1541376

Could you file a bug report here and send me a link?

https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setu...

I'll chase it up with the responsible team.

You can update as often as you like, but that does not ensure users will get that update, nor does traditional packaging make it safe to install the update (no rollbacks, maintainer scripts run as root and have full access to the filesystem, library mismatches, etc).

I'm all for debs and rpms, but they seem best suited to providing the base system.

[disclaimer: I'm on the Snapcraft team]

>IMHO, operating systems should ultimately be immutable and basically be similar to a snap. You update it as a whole and you don't modify parts of it.

Absolutely agree. Ubuntu Core is trying to achieve something like this: https://www.ubuntu.com/core

Snapcraft (https://snapcraft.io) | Senior Software Engineer | REMOTE | Full time

The Snapcraft team at Canonical (Ubuntu) are trying to make it easy to deliver app updates to all Linux-based cloud, IoT, and desktop systems safely (confinement, rollbacks) and automatically.

We're motivated by making developers' lives easier. We want to see people spend time on what makes their app unique and interesting, not on packaging. We also understand that developers currently face an impossible choice between few updates to lower the risk of breakage and frequent updates to lower the risk of compromise.

The open position is for a Senior Software Engineer. We want someone with years of war stories building developer tools to help re-architect the core of Snapcraft (https://github.com/snapcore/snapcraft). It needs to integrate deep into Python, Node, Ruby, Electron, and others so that releasing your app for tens of millions of Linux users is a natural extension of setup.py or npm run.

https://boards.greenhouse.io/canonical/jobs/1067097

The "Users by distribution" table at the bottom of the Spotify page is worth a look: https://snapcraft.io/spotify

Snaps are not Ubuntu-only. You can find install instructions for many distros here: https://docs.snapcraft.io/core/install

That is not true. You absolutely can specify a license: https://snapcraft.io/vlc

I work for Canonical, but I also share maintainership of some snaps. From an automatic email I received recently: “A scan of this snap shows that it was built with packages from the Ubuntu archive that have since received security updates. The following lists new USNs for affected binary packages in each snap revision: … Simply rebuilding the snap will pull in the new security updates and resolve this. If your snap also contains vendored code, now might be a good time to review it for any needed updates.“

Yes, you don’t get that library update everywhere all at once, but this gives each vendor a chance to make sure that update actually works with their app.

Canonical | Senior Software Engineer | Remote | Full time

Snapcraft (https://snapcraft.io, https://github.com/snapcore/snapcraft) makes it possible to deliver app updates to all of Linux automatically, eliminating the long tail of supported releases and complex install instructions.

I am looking for a senior software engineer with background in developer tools to join our globally-distributed, home-based team.

More at https://boards.greenhouse.io/canonical/jobs/1067097

Canonical | Software Engineer | Full-time | Remote

Canonical’s Snapcraft (https://snapcraft.io) makes it possible to deliver app updates to all of Linux automatically, eliminating the long tail of supported releases and complex install instructions.

With thousands of applications on the platform from over a thousand developers, including well-recognised names like Spotify, Slack, and Microsoft, the Snapcraft team’s mission is to uphold a high bar of quality as well as predictable, intuitive behaviour.

We are looking for an experienced software engineer with background in developer tools to join our globally-distributed, home-based team.

Apply at https://boards.greenhouse.io/canonical/jobs/1067097

Sincerely curious why you think a squashfs of the app contents (without any additional operating system bits) running under seccomp and apparmor is a hack? What do you think is the ideal solution?

I wouldn't call the snap build process for Electron apps backwards:

  npm install -g electron-builder # for brevity, --save-dev works
  electron-builder --linux snap --x64
  ls dist/*.snap

There's no operating system rootfs in your snap. That lives in the core snap.

It's packaging and delivery for Linux desktop, server, and IoT apps. As elsen mentioned, updates happen automatically and roll back if unsuccessful. Automated review covers most cases and the format is simple yaml, so you can quickly push something up that you can install from anywhere.

Some guides using real world examples if you want to have a poke: https://docs.snapcraft.io/build-snaps/languages

Canonical (http://canonical.com) | Developer Advocate | REMOTE | Full-time

We are seeking an experienced Developer Advocate to join a small team helping developers get up and running with the Snapcraft platform for Linux application delivery (https://snapcraft.io) and Ubuntu Core, the optimised version of Ubuntu for IoT (https://ubuntu.com/core).

The key challenge of the role is improving the onboarding experience of snapcraft.io. Sample activities include writing guided material for popular languages and frameworks, running email campaigns, and architecting documentation.

Strong technical writing skills are a must. Candidates familiar with the needs and terminology of the popular language communities will be preferred.

Email your CV to [email protected] or fill out this form: https://ldd.tbe.taleo.net/ldd03/ats/careers/requisition.jsp?...

Canonical | Developer Advocate | Work from home | Full-time

I'm looking for an experienced Developer Advocate to join a globally-distributed team driving advocacy for Snapcraft (https://snapcraft.io) and the optimised version of Ubuntu for IoT (https://ubuntu.com/core).

You can email me ([email protected]) or learn more about the role here: https://ldd.tbe.taleo.net/ldd03/ats/careers/requisition.jsp?...

I've put together a snap of this. If you're on Ubuntu you can `sudo snap install seashells` then `echo hello | seashells`.

All the learning and process needed to create Debian packages has been a big motivator for us to make snap packaging simple and quick. Have a look at the Heroku CLI snap, for example: https://github.com/heroku/cli/blob/master/snap/snapcraft.yam...

You can quickly piece together a snapcraft.yaml, push it to GitHub, and turn on auto builds and publication (https://build.snapcraft.io). Then anyone can install your package with a single command - no PPA/repo needed.

This is exactly right. Debs, snaps, and flatpaks will happily coexist. The upstream gets to choose which works best for them while still supporting users of all distros.

I think snaps + Debian stable could be that solution. You get the stability of Debian at the system level with the reliability of app updates from snaps.

Bad updates automatically roll back, and you can subscribe to a risk level at a per-application level (https://www.youtube.com/watch?v=-3b9qkl9Z_k).

As well, because snaps bundle their dependencies you don't have that problem you mention of adding a repo and getting busted library versions.

Hi, Evan from the Snapcraft team here. We're really excited to launch https://build.snapcraft.io today. It'll automatically build and publish your software every time you push a commit to GitHub.

You can then promote any build as a release, installable on the tens of millions of Linux systems that already support snaps.

You just have to provide a config and you're off:

- https://github.com/popey/emoji/blob/master/snapcraft.yaml

- https://github.com/abacao/packer-snap/blob/master/snapcraft....

- https://github.com/RocketChat/Rocket.Chat/blob/develop/.snap...

Keen to hear what you think of it or any feedback you have. Also happy to answer questions.

This isn't a problem with snaps (https://snapcraft.io), which bundle their dependencies. They're also transactional: if the update fails it just rolls back to the last known-good state.

That option to automatically install security updates is on by default in Ubuntu 16.04, by the way: http://blog.dustinkirkland.com/2016/10/dirty-cow-livepatched...

Snaps were designed from the beginning to push automatic updates, even of non-security updates: https://www.youtube.com/watch?v=DLxqdf89hRo