Update hackathon best practices with a timeline.

[bangerth]

No description provided.

[ljhwang]

@bangerth thanks for starting this.

I personally am not a fan of icebreakers and am wondering if the same can be achieved in a different way. I think game night and similar group activities work well if done early(ier).

I would suggest some minor rewording but I am going to let others chime in.

[baagaard-usgs]

I would label this addition as a "sample" or "example" schedule. The schedule is quite specific and the appropriateness of some activities can depend on the format (for example, individual projects versus group projects). That said, the general ideas are a good addition and provoke additional thought about how to run a hackathon.

[bangerth]

@baagaard-usgs FYI, this patch came out of a conversation we had post-ASPECT hackathon this year in which we felt like we had one or two people fall through the cracks, and how we can improve the situation. I entirely agree that this isn't mean as a schedule for all projects, but rather as a way to think about the issues. I've prefixed the new text by a paragraph that outlines the goals the sample schedule is intended to achieve.

@ljhwang I've added alternatives to icebreakers.

[ljhwang]

Looks good.

Please fix one typo in Day 5: get to gether => get together

[bangerth]

So fixed.