2018 edition of the syllabus should be archived in a branch

Here's a sketch of what we (@bergmul and @lachlandeer ) talked about on Skype.

Let's iterate here as needed. I've put @bergmul 's name on material I assume he can teach, feel free to change it based on your comfort level.

Some thoughts my me:

• Could we move git later (post python?) get's everyone coding early then they might see the need for version control as we develop some stuff, then we introduce it
• what for the third person to do?
  • Could they lead the project sessions in R, Python and Snakemake? If we essentially sketch it up they can steer it? Or we can make them figure out a good exercise (passing it my us of course ... )
  • Would give them exposure to all of the tools to help them take a bigger lead in following years

Let me know what you think!

L

We need to update the meta data on

• who
• when
• where
• weblinks
• email
• [ ]

Course material at end of syllabus needs to be updated once we settle on the exact material outlined in #1

check over motivation part of syllabus to make sure the narrative is still in line with both:

1. how we fell about the state of the world
2. what we think this course is doing

We are potentially facing two sets of students (from UZH)

• those that took JL and I's 'foundation course' in 2019
• first years that didnt do the above

Question is how we want to set up syllabus etc to deal with this and make it clear which parts of the course are relevant to each set of people.

Two immediate thoughts emerge

1. bold face (or similar) the material that is similar so that those who did the foundations stuff don't need to attend
2. separate syllabi for each group
   • there's a stack of overlap if we go this way which is frustrating

@lachlandeer prefers route 1.

similar to #5 , we need to archive the 2017 edition in a branch + release

the most recent commit 948f816 is the 2017 edition update