Planning

The website

The goal is to get a working site up while doing as little work as possible ourselves.

Prelude

(Copied from Discourse)

Just to reorient ourselves: the reason why I wanted to go with rails because I don't want to write the entire stack myself - there should be pieces that already exist (like an events & calendar system) that we can just plug in.

I'm not married to rails, but I want to see if we can do that with rails before we explore other options. So in this case, I'm prioritizing "getting it done" over having cool tech :P

s/rails/django/g if we decide to go with Django instead.

Of course, we can reimplement this stuff in a "fun" way after we get it working. I've just been a part of too many "let's do boring activity X in fun technology Y" projects that never got finished because X is still boring, even if you're doing X in Haskell. So I think we should take the pragmatic approach here.

What we need

A possible solution

Switch to Django (from Rails) and use the web app powering lug.ncsu.edu (source) as a starting point for building our main website (the front page).

Pros:

The following will instantly be available to us:

Cons:

Ongoing discussion

There's an ongoing discussion about other possibilities such as:

Please check out http://discourse.emacsconf2015.org/t/reconsidering-our-stack/54 and feel free to add them here