Hackseq 2017 hackathon logistics

[oneillkza]

@cmorganl, @klimstef, @sibylgisela, @jesszha, @jjonphl and @adammendoza, welcome to Screw!

I'm creating this post to give you some background reading ahead of the hackathon, and to make announcements regarding logistics. I'll also send out info on Slack, but I feel like this is more likely to get through.

Background reading

• Firstly, and most importantly, we have a code of conduct for this project and for our time at the Hackathon, so as to ensure we work in an inclusive and welcoming space. Please familiarise yourself with it.
• For general background on Screw, check out my poster and talk from BOSC earlier this year.
• For background on CWL, which will be pretty essential for a lot of the work we will be doing, check out the gentle introduction. Please at least skim this, and spend a little time trying to understand what's going on in the Screw codebase.
• For some general background on single-cell epigenomics, check out the Wikipedia article I wrote. It also has links to several good review papers.
• I intend to use a compressed form of Scrum to manage our work during the hackathon. I used this to some success at a hackathon earlier this year. We will consider the whole hackathon to be a sprint, and each half-day coding to be a "day" for the purposes of daily stand-up meetings. This means we will have one sprint planning meeting at the beginning, for about an hour (certainly no more), at which we estimate issues and divide them up amongst the group. We will also have five minute stand-up meetings before coding each morning and afternoon. If all of these terms feel foreign to you, feel free to do some background reading. I will also explain them as we go!

And let me know if you have any questions, either via comments or Slack.