[Discuss] shutting down our sandstorm instance

2016-01-28 Thread Bryan Richter
We primarily wanted Sandstorm for Etherpad. However, Etherpad is a
node.js based, JIT-compiled application. Sandstorm's security model
requires each document to be running in its own, sandboxed copy of the
app, and the JIT-ness apparently precludes such applications from
sharing memory. Thus, each *document* uses 60-100MB when open.

We can't support that right now, so I plan on shutting down our
Sandstorm instance in two weeks.

Perhaps we can run Etherpad *outside* of Sandstorm, if we still find
ourselves wanting for a collaborative document solution.

P.S. These facts were confirmed by a friend of mine at a Sandstorm
meetup in SF yesterday. They hope to solve the memory usage with
"snapshotting" at some point.


signature.asc
Description: Digital signature
___
Discuss mailing list
Discuss@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/discuss


Re: [Discuss] shutting down our sandstorm instance

2016-01-28 Thread Aaron Wolf
On 01/28/2016 02:28 PM, Bryan Richter wrote:
> We primarily wanted Sandstorm for Etherpad. However, Etherpad is a
> node.js based, JIT-compiled application. Sandstorm's security model
> requires each document to be running in its own, sandboxed copy of the
> app, and the JIT-ness apparently precludes such applications from
> sharing memory. Thus, each *document* uses 60-100MB when open.
> 
> We can't support that right now, so I plan on shutting down our
> Sandstorm instance in two weeks.
> 
> Perhaps we can run Etherpad *outside* of Sandstorm, if we still find
> ourselves wanting for a collaborative document solution.
> 
> P.S. These facts were confirmed by a friend of mine at a Sandstorm
> meetup in SF yesterday. They hope to solve the memory usage with
> "snapshotting" at some point.
> 

I think Sandstorm's clunky interface for sharing etc. and even seems
laggy as a user… I'm happy to skip it. It has promise, but feels not
great right now.

I made some notes about our tools:

IRC: *check* (we talked about embedding a client in the site sometime
though)

Jitsi meet: *check* use their instance

Etherpad: we don't have a good third-party host that we know we can rely
on, the updated one with in-line commenting is nice. Maybe we should run
it ourselves…

Wekan: probably run ourselves…

Redmine or OpenProject: user-stories, processing, sorting, project
management stuff, I guess should run ourselves

Wiki: need to separate wiki stuff out from our code, probably separate
the main articles for public-consumption stuff from the stuff that we
use for our organizing. I'd like to integrate Gitit eventually. I could
see using a wiki with Redmine/OpenProject or something for immediate
notes and internal organizing.

GitLab: *check* via git.gnu.io

Email lists: *check* but probably should move the announce stuff to
CiviCRM probably

CiviCRM: *check* but need better organizing, better access for people,
use the email announce functions, use hooks/API or something to
integrate potentially…

http://42.meup.org for image paste sharing…

We're still working on:

image repos, collaborative graphics work…

spec'ing of the site… will Redmine cover that?

Sorry for the dump of stuff, I guess ideally even Redmine might offer
better ways to process all this info vs just this mailing list?
___
Discuss mailing list
Discuss@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/discuss