Mastodawn

Aral Balkan Oct 5, 2017

Re: internal tech at DiEM25 (an issue I’m not directly involved in & never had authority for), as I mentioned in my talk in Passau, the next step you have to take is simple:

1. Put all DiEM25 code on public source control (including the code for the voting systems). Ideally, a GitLab instance under source.diem25.org.

This will reduce the truck factor, provide transparency (especially essential for voting code), and allow others to help.

Once this is done, let’s chat about step 2.

Show thread

lynX

@aral I wished that was our problem, but I'm afraid the entire ruby-on-rails thing is too slow for a free website. As soon as you have half a cup of popularity you probably have to boost it with cloud technology. I recommend rewriting the website using more efficient tools, and — most of all — not reinvent voting systems… in particular do secret vote machines that aren't even legal in some EU countries.