<div dir="ltr">Hello Leo,<div><br></div><div>Thanks for getting in touch, and thanks for your kind words about mosh!</div><div><br></div><div>Right now we have a Debian package, which we maintain in our own source tree, and which we upload to Debian every time there's a new release. That flows into Ubuntu as part of the normal release schedule. For users who want something more immediate, we also have the mosh-dev PPA that pulls from our GitHub repository once a day and auto-builds the Ubuntu source and binary packages, and then we have a "stable" mosh PPA as well, which only gets updated on new releases.</div><div><br></div><div>Is it possible to teach Launchpad to also auto-build a snap once a day (if our Git repo has changed), alongside the PPA .debs? Can we script Travis-CI to automatically build and push a snap each time it runs a successful CI test on the master branch? Or how would you recommend we do this?</div><div><br></div><div>Mosh is pretty simple so I doubt we're going to be pushing the boundaries of the snap format -- it's basically two unprivileged binaries and some man pages. And a bash-completion script that gets put in /usr/share/bash-completion/<wbr>completions/mosh. I guess that might be a little more interesting, depending on whether snap can handle that.</div><div><br></div><div>Happy to work with you on this if you think there is user demand for it.</div><div><br></div><div>Cheers,</div><div>Keith</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 12, 2017 at 10:00 AM, Leo Arias <span dir="ltr"><<a href="mailto:yo@elopio.net" target="_blank">yo@elopio.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello!<br>
<br>
I’m Leo. I work as part of the engineering team around Ubuntu and Snapcraft [1].<br>
<br>
Last year I found about mosh, and it has been the most amazing experience. It<br>
solves most of the problems due to my unstable latin american internet<br>
connection; so first, let me say thank you very much!<br>
<br>
I was reading about your new candidate release, and I thought that this might be<br>
interesting for you. We’re working on snaps, a platform to enable developers to<br>
directly control delivery of software updates to their users, and make their<br>
software available in a secure way, with automatic updates in different<br>
channels.<br>
<br>
The channels are particularly relevant when trying to release new versions, and<br>
solve an old problem we had with Ubuntu. Instead of having a 6 month cycle for<br>
everybody, you can push different versions whenever you want. So you could push<br>
a new version to the edge channel every time something lands on your repository,<br>
to get extreme early feedback from your contributors. When you make a freeze to<br>
stabilize for the release, you can push that to the beta channel. And when you<br>
are ready to release but want to give it to a greater audience for the final<br>
checks, you can push to the candidate channel. When everybody is happy with the<br>
release, it can be pushed to the stable channel. Your users just decide the<br>
level of risk they want to take, and they will constantly receive updates when<br>
you push something new.<br>
<br>
I this sounds like a good fit for your project, I would love to work with you<br>
making the snap. I'm particularly interested in the feedback that you can give<br>
us about a few new features that might be useful for mosh.<br>
<br>
pura vida.<br>
<br>
[1] <a href="http://snapcraft.io/" rel="noreferrer" target="_blank">http://snapcraft.io/</a><br>
______________________________<wbr>_________________<br>
mosh-devel mailing list<br>
<a href="mailto:mosh-devel@mit.edu" target="_blank">mosh-devel@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/mosh-devel" rel="noreferrer" target="_blank">http://mailman.mit.edu/mailman<wbr>/listinfo/mosh-devel</a><br>
</blockquote></div><br></div></div>