update to overall readme on presentations

README.md

@@ -16,12 +16,14 @@ Students will be expected to engage with various features of git/GitLab througho
 
 ## Assessment(s)
 
-**Update as of 15 April 2020: as discussed in virtual class last week, we shall have the final project pitch/feedback session on Tuesday 21 April. Thereafter (28 April, 5 May, 12 May), we shall have short 'stand-up meetings', where we each offer a 5-minute update on how our projects are progressing and what help we might need. We'll hope to have fuller project pitches/presentations on 18 and 26 May respectively (two in each session). These don't need to be fully finished projects, but rather an outline of what a more substantial project would be, if you had unlimited time/resources; and it should give us a hint of the kinds of issues you think you will reflect on in the second part of your assessment (point 2 below).**
+**Update as of 5 May 2020: as discussed in today's class, we will do full project pitches/presentations in an extended session on 26 May from 10-11 (2 projects) and 11.30-12.30 (2 projects). Please ask your final technical questions to Danny (and make final merge requests to the Digizeit master repository) by Friday 22 May at the latest. You can of course continue to work on your projects after 26 May with your 2nd semester reflection paper in mind, but the presentations of 26 May will be the 'time-stamp' on your work in this first semester. Looking forward greatly to seeing your work in this end-of-semester form!**
+
+**Update as of 15 April 2020: as discussed in virtual class last week, we shall have the final project pitch/feedback session on Tuesday 21 April. Thereafter (28 April, 5 May, 12 May), we shall have short 'stand-up meetings', where we each offer a 5-minute update on how our projects are progressing and what help we might need. We'll hope to have fuller project pitches/presentations on 19 and 26 May respectively (two in each session). These don't need to be fully finished projects, but rather an outline of what a more substantial project would be, if you had unlimited time/resources; and it should give us a hint of the kinds of issues you think you will reflect on in the second part of your assessment (point 2 below).**
 
 Because *History in a Digitized World* is not a regular MA Seminar, we will be requiring a mixture of assessments rather than a single Seminararbeit.
 
 1. During the “first” semester (FS20), we shall have an in-course assessment in the form of some kind of digital project (the exact form of this project will be discussed in Week 1’s session). This in-course project will be instead of individual oral presentations. We have scheduled April to be the “project month”, during which time you can develop an original idea, and receive feedback and guidance on how to realise this project in digital space.
-2. During the “second” semester (HS20), when you would normally submit a Seminararbeit, we will ask instead for a shorter written paper in which you reflect on your project with reference to relevant secondary literature. The deadline for this second assessment is Friday 4 December 2020. **Update: ideally we would like you to write this directly into GitLab, at the very least in the form of a README.md file. This would be instead of you submitting a paper copy of your project reflections.**
+2. During the “second” semester (HS20), when you would normally submit a Seminararbeit, we will ask instead for a shorter written paper in which you reflect on your project with reference to relevant secondary literature. The deadline for this second assessment is Friday 4 December 2020. **Update: ideally we would like you to write this directly into GitLab, at the very least in the form of a README.md file. This would be instead of you submitting a paper copy of your project reflections. See also [here](https://docs.gitlab.com/ee/user/project/pages/) for potential ideas on how to publish your reflection piece as a webpage; with some technical help, you can also link your GitLab/GitHub repositories to sites such as [this](https://readthedocs.org) for nice presentational layout.**
 
 ## Support
 
@@ -29,7 +31,7 @@ In addition to Daniel McDonald (@daniel.mcdonald) who will be present in most cl
 
 ## Winging it
 
-This is the technical term for what is also known as "agile management". What this means in practice is that while we have a general course structure in mind, the way the course unfolds will depend on the feedback and interests of the students. Therefore, we shall try to liaise with you, the students, as much as possible about course content and assessment, expecting in return that you help maintain an ongoing dialogue that will shape the course according to your individual interests.
+This is the technical term for what is also known as "agile management". What this means in practice is that while we have a general course structure in mind, the way the course unfolds will depend on the feedback and interests of the students. Therefore, we shall try to liaise with you, the students, as much as possible about course content and assessment, expecting in return that you help maintain an ongoing dialogue that will shape the course according to your individual interests. **Update: classes will take the form of 'stand-up meetings' (to offer ongoing peer review of projects) from 28 April until final semester presentations.**
 
 ## Feedback/interaction