GitLab

Addresses #359

`README.md` says to submit a form through AMY, while `index.html` still asks for sending an email. This PR makes the latter consistent with the former. Replaces #329

Closes #151.

Closes #250.

Previous instructions had too many 'next's for current installer (2.8.2)

This should enable participants who don't yet have a github account
in their own time, so they're less likely to end up with "yet another
account at some website".

Current Python 3 installer is called Anaconda3-4.0.0-Linux-x86_64.sh
and 'bash Anaconda-' would not autocomplete.

We sometimes get questions about what OS people should use. We also see often people coming with laptops that they don't have admin rights on.
Do we want to go ever further and say a recent version of the OS?  We may have some challenges if people come with,  say, Windows XP or Ubuntu   10.4 (or whatever Mac's outdated version is -- I've never used a Mac).

There is no corresponding opening <p> tag. This looks like useless cruft.

per #277 link now downloads windows installer rather than directing user to windows installer repository

When people edit the workshop agenda they often end up removing the links to the surveys and then need SWC staff to re-send them.  Links are now moved outside the agenda.

Close 274.

An attempt to make it even more clear which entries in index.html should be quoted and which not.

Use YYYY-MM-DD instead of "YYYY-MM-DD", which offends `tools/check.py`

Sometimes instructors forget to customize their CHECKS, but learners
still follow this link and run the stock checks, resulting in a bunch
of confusing errors about missing packages that the learner doesn't
actually need [1,2,3,4].  Instead of expecting instructors to edit
CHECKS or remove the setup/ reference from index.html (a default that
is right for nobody), this commit comments that setup/ reference out
(a default that is right for folks who don't want
installation-checks).  Instructors who *do* want installation checks
now need to do two things (uncomment the setup/ reference and update
CHECKS), but with both steps listed in CUSTOMIZATION they are more
likely to get that right.

[1]: https://github.com/swcarpentry/workshop-template/issues/136
[2]: https://github.com/swcarpentry/workshop-template/issues/180
[3]: https://github.com/swcarpentry/workshop-template/issues/181
[4]: https://github.com/swcarpentry/workshop-template/issues/258