[TOOLS-DEVELOPMENT] Fwd: Re: [Tools-discuss] Etherpad no longer on standard port

[Robert Sparks <[e-mail]>]

Carsten wrote:

>
> So my take is that there is additional incentive to look for what’s 
> next after Etherpad, for functional as much as for those operational 
> reasons.
> I repeat my ceterum censeo that hackmd/CodiMD is a viable candidate, 
> but that observation is not addressed at operational people at this 
> point (although we’d have to figure out whether that can be run 
> reliably — the sysadmins at my university tell me they can).

This looks like it would be easy to deploy to me and it passes a first 
sniff-test at keeping it going.

I was able to do a one-click deploy in heroku, and tweaking options to 
make it be fairly wide open was simple.

By default, it requires some simple registration (it allows on-instance 
registration with an email address that it doesn't verify). In the long 
run, it could be made to require datatracker credentials with what I 
currently think isn't a _lot_ of work (depending on the current quality 
of the django libraries to facilitate becoming an OAUTH2 provider).

I'd like to see us seriously investigate supporting this soon.

RjS