3 ms·

If the failure of Sandstorm has shown one thing, it's that people will not maintain forks of software if the layer you're integrating with is too complex. I'd

If the failure of Sandstorm has shown one thing, it's that people will not maintain forks of software if the layer you're integrating with is too complex. I'd much prefer if Sandstorm just shipped with an IdP and contributed OIDC implementations to downstream projects.

ocdtrekkie 7y ago
We've definitely had varying levels of success with this. Sometimes an app has a switch or two for being on Sandstorm and a .sandstorm directory in their repo, and you can more or less "vagrant-spk pack" it and it's good to go. One of the things we're interested in with vagrant-spk updates is ensuring the flow to update old apps is a lot smoother. Others have a fair bit more difficulty, but I think it comes down to market share: If a lot of their users are on Sandstorm, they're going to care about maintaining a Sandstorm package. If the Sandstorm project isn't as widely used, people aren't going to be that excited to do all the extra work for packaging. Wekan has Sandstorm packages as part of the release pipeline: Every single release is submitted to the Sandstorm app market, actually. But Wekan is both considered a core app for Sandstorm, and has been available on Sandstorm since it's very early days as a project, so the group of users using Wekan on Sandstorm has always been pretty healthy.
- sascha_sl 7y ago
  It's a bit like providing a snap. I know exactly one non-cannonical project that maintains a reliable out of the box experience for snaps, Nextcloud. And that's because they use and package it themselves. Yet I'm never quite sure if I'm about to shoot myself in the foot installing any other snap. Same with Sandstorm. When I ran Mattermost for a bit I was initially shocked how seamless and fast it worked, followed by immediate disappointment that apparently just a handful of versions had been patched and it was lots of major versions behind by now.

ocdtrekkie 7y ago

We've definitely had varying levels of success with this. Sometimes an app has a switch or two for being on Sandstorm and a .sandstorm directory in their repo, and you can more or less "vagrant-spk pack" it and it's good to go. One of the things we're interested in with vagrant-spk updates is ensuring the flow to update old apps is a lot smoother. Others have a fair bit more difficulty, but I think it comes down to market share: If a lot of their users are on Sandstorm, they're going to care about maintaining a Sandstorm package. If the Sandstorm project isn't as widely used, people aren't going to be that excited to do all the extra work for packaging. Wekan has Sandstorm packages as part of the release pipeline: Every single release is submitted to the Sandstorm app market, actually. But Wekan is both considered a core app for Sandstorm, and has been available on Sandstorm since it's very early days as a project, so the group of users using Wekan on Sandstorm has always been pretty healthy.

sascha_sl 7y ago
It's a bit like providing a snap. I know exactly one non-cannonical project that maintains a reliable out of the box experience for snaps, Nextcloud. And that's because they use and package it themselves. Yet I'm never quite sure if I'm about to shoot myself in the foot installing any other snap. Same with Sandstorm. When I ran Mattermost for a bit I was initially shocked how seamless and fast it worked, followed by immediate disappointment that apparently just a handful of versions had been patched and it was lots of major versions behind by now.