# 2025 Sep/Oct CodeRefinery workshop

:::danger

This document is outdated with names! Check https://docs.google.com/spreadsheets/d/1g8Bc_76OPcv1vYWtB54wz6HsXQcb3B1GtQFga4Oanw4/edit?usp=sharing instead!
:::

:::info
## Links

- Registration: https://indico.neic.no/event/282/
- Webpage: https://coderefinery.github.io/2025-09-09-workshop/
- Notes: https://notes.coderefinery.org/workshop-2025-sep
- [Twitch channel](https://www.twitch.tv/coderefinery/about)
- [Advertisement text](https://coderefinery.github.io/2025-09-09-workshop/communication/#workshop-announcement-example)
- [Poster](https://github.com/coderefinery/coderefinery-artwork/blob/beb72ced357d8f01e7901e40522c3cff6eeb6f19/events/2025-09-cr/CR-poster-sep25-general.png)
- [Organizer overview](https://docs.google.com/spreadsheets/d/1g8Bc_76OPcv1vYWtB54wz6HsXQcb3B1GtQFga4Oanw4/edit?usp=sharing)

:::

:::info
## Basic info
- Dates:
- Week 1 "as usual" 9+10+11/September 11:00-13:00 + 14:00-15:30 (Oslo CEST times)
- Week 2 spread over 6 weeks : 17.9+24.9+1.10+8.10+15.10 + 22.10; at 12-14.30 CEST, each lesson separate including exercise sessions

:::

## Workshop roles

- Overview of the roles: https://coderefinery.github.io/manuals/roles-overview/

### Instructors
([Description](https://coderefinery.github.io/manuals/instructors/))

General interests and availability (check dates below):

- Johan: Jupyter, **testing**
- Jarno: **streaming**, **Jupyter**, documentation
- Sabry: **git-intro** (or anything else during first week),
- Radovan: **modular code development** (but can be more and can be less)
- Michele: **documentation**, jupyter (done last year), testing (because it's cool),
- Gregor: **git-collaborative**
- Ina: **reproducible research**, git-intro
- Oskar: testing, **git-intro**, (modular code development), documentation, (social coding)
- Bjørn: git-intro, **social coding**
- Andrew: **git-collaborative**
- Yu: **Modular code development**
- Hossein: git, modular code
- Enrico: any empty slot (e.g. **social coding**)
- Thomas: **reproducible research**,
- Heman: git-intro (or open to anything except during the NeIC AHM)
- Susa: might take over one of TPs lessons (clarified on Tue) -> git intro, automated testing

To be filled in later based on above: Two names per lesson, first is primary

- [ ] day 1 (9.9) - git-intro: SR, HM
- [ ] day 2 (10.9) - git-intro: SM, OT
- [ ] day 3 (11.9) - git-collaborative: GD, AM
- [ ] day 4 (17.9) - reproducible research: TP, IP
- [ ] day 5 (24.9) - social coding: BL, EG
- [ ] day 6 (1.10) - documentation: MM, YT
- [ ] day 7 (8.10) - jupyter: JR, HF
- [ ] day 8 (15.10) - automated testing: JH, SM
- [ ] day 9 (22.10) - modular code dev: RB, YT

:::spoiler Instructor checklist
Before the workshop:
- Review, triage, and work on lesson issues
- Communicate exercise list to Exercise coordinator
- Meet with co-instructor and together test your screen share
- Communicate software requirements and timing changes to Instructor coordinator
- Try to do a dry run (prefereably with someone “new” to the topic)

After the workshop:
- Write a short field report about timings and lessons learned (example: https://github.com/coderefinery/testing/issues/231)
:::

### Managing collaborative document
([description](https://coderefinery.github.io/manuals/hackmd-helper/#hackmd-manager))

Task: Keep the document organized, check for unanswered questions, and archive notes each day.

General interests (write your name and days you would be available below):

- DI (can help with archiving and asking questions, at least week 1)
- MM (haven't done any archiving ever.
- not available on day4
- probably not available on day5
- teaching on day6, so meh
- ..

Based on above we can then fill the schedule:
- [ ] preparation before workshop:
- [ ] day 1 (Sep 9) - git-intro: DI, ???, ...
- [ ] day 2 (Sep 10) - git-intro: DI, ???, ...
- [ ] day 3 (Sep 11) - git-collab: DI, ???, ...
- [ ] day 4 (Sep 17) - reproducible research: ???, ???, ...
- [ ] day 5 (Sep 24) - social coding: ???, ???, ...
- [ ] day 6 (Oct 1) - documentation: ???, ???, ...
- [ ] day 7 (Oct 8) - jupyter: ???, ???, ...
- [ ] day 8 (Oct 15) - testing: ???, ???, ...
- [ ] day 9 (Oct 22) - modular code development: ???, ???, ...

Note that you can also send people to Zoom exercise session during the workshop.

## Zoom help during workshop
(this is not a general exercise room, but rather a drop in session for people with technical challenges or questions that are difficult written down)

- general interest from other documents:
- MM
- OT
- share your interest and availability here:
- ..
- ..
- ..

- [ ] day 1 (Sep 9) - git-intro: ??, ???,
- [ ] day 2 (Sep 10) - git-intro: ??, ???,
- [ ] day 3 (Sep 11) - git-collab: ??, ???,
- [ ] day 4 (Sep 17) - reproducible research: ??, ??,
- [ ] day 5 (Sep 24) - social coding: ???, ???,
- [ ] day 6 (Oct 1) - documentation: ???, ???,
- [ ] day 7 (Oct 8) - jupyter: ???, ???,
- [ ] day 8 (Oct 15) - testing: ???, ???,
- [ ] day 9 (Oct 22) - modular code development: ???, ???,

## Workshop organization; roles "behind the scenes"

Organiser roles and their responsibilities. This does not mean that a person will do
everything that is part of their responsibility, but they will make sure that
their responsibilities are followed-up and not forgotten.

AP for coordinators:
- EG: Update general install instructions
- EG: Certificates

### Event director
([description](https://coderefinery.github.io/manuals/director/))

- lead: Enrico (not around on day 7+8+9)
- backup:
- backup backup: Samantha (available all days except 5, slightly limited availability day 1-3, 9)

:::spoiler Checklist
- Before workshop
- [ ] Distribute roles using this document
- [ ] Ask collaborators/stakeholders to pick roles
- [x] Add all sessions to [CodeRefinery calendar](https://github.com/coderefinery/calendar) separately
- [x] Send calendar invite to all organizers, instructors, expert helpers, with all relevant links
- [x] Decide if certificates will be possible and what is needed for getting a certificate/credits (ask from partner universities)
- [x] Remind co-organizers and instructors to register
- [ ] Send summary email to all co-organizers will all important links in one place
- During workshop:
- [ ] day 1 intro to full workshop
- [ ] daily intro (note that some people may only join one day!)
- [ ] workshop setup with exercises, installation needs
- [ ] collaborative notes
- [ ] daily outro
- [ ] last day outro + where to go from here
- After the workshop:
- [ ] Summarize lessons learned and make it a blog post in [coderefinery.org repo](https://github.com/coderefinery/coderefinery.org)
- [ ] Coordinate post-workshop survey eg. in Indico
- [ ] Merge new edits from here (no names ofc) to the [Playbook](https://github.com/coderefinery/manuals/blob/master/workshop-playbook.md)
- [ ] Port changes from workshop page to [template page](https://github.com/coderefinery/template-workshop-webpage)
- [ ] On CR website move from ["upcoming"](https://github.com/coderefinery/coderefinery.org/blob/main/content/workshops/upcoming.md) to ["past"](https://github.com/coderefinery/coderefinery.org/blob/main/content/workshops/past.md)
:::

### Registration coordinator
([description](https://coderefinery.github.io/manuals/registration-coordinator))

- lead: Samantha
- backup: Enrico

:::spoiler Checklist
- **ca. 2 months before = When workshop details are set:**
- [x] Create [Indico registration page](https://indico.neic.no/category/5/) for the event
- [x] Include event information
- [x] Customise the registration form
- [x] Customise the confirmation email (with outreach and marketing coordinator)
- [x] Add Zoom link if any
- [x] Point to workshop page
- [x] Add collaborative document link if any
- [x] Set up a workshop page from [template page](https://github.com/coderefinery/template-workshop-webpage)
- [x] Add workshop to ["upcoming courses"](https://github.com/coderefinery/coderefinery.org/blob/main/content/workshops/upcoming.md)
- Remember to add all the emails to workshop page
- [x] Open the registration
- **Every day:**
- Check support email (Freshdesk) for requests/questions
- **Every week:**
- Check registrations for problems and read notes to organizers
- Identify if need to do something – basically, "playing" with the registration data to not forget anybody and not to forget follow-up
- Update [stats](https://github.com/coderefinery/workshop-stats)
- Update workshop-webpage if new local organisations
- **ca. 1 month before:**

- [x] [Team leaders](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/email-to-team-leads.md)

- **One weeks before install session**
- [x] [Send general information to all](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/practical-info-2023-03-09.md)
- Links
- Schedule
- General info

- **ca. 1 week before**
- [ ] Update Indico auto-reply for last minute registrations
- [x] Send [email with all links](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/links-2023-03-15.md)
- **1 day before!**
- [ ] Send a [reminder with links](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/links-2023-03-20.md)
- **During the workshop**
- [ ] Send [daily summaries](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/summary-day1.md) (with exercise coordinator)
- [Some of them have also preparation instructions!](https://github.com/coderefinery/2023-03-21-workshop/blob/main/content/communication/summary-day2%2Bprep-day3.md)
- **After the workshop:**
- [ ] Add viewing statistics to [CodeRefinery webpage](https://github.com/coderefinery/coderefinery.org/tree/main/content/about/statistics)
- [ ] Use [statistics repo](https://github.com/coderefinery/workshop-stats) (feel free to edit)
- [ ] Close registration
:::

#### Broadcaster
([description](https://coderefinery.github.io/manuals/broadcaster/))

- lead: Jarno
- backup: Richard
- backup backup: Enrico (with backup Aalto laptop)

:::spoiler Checklist
- [ ] Prepare ice-breakers for each day
- [ ] Create instructor Zoom and communicate it (with exercise coordinator and outreach and marketing coordinator)
- [ ] Publish recordings (does not do all the work but coordinates it)
- [ ] Prepare for upload (use [ffmpeg-editlist](https://github.com/coderefinery/ffmpeg-editlist) and collaborate)
- [ ] Upload videos and communicate (with outreach and marketing coordinator)
:::

### Instructor coordinator
([description](https://coderefinery.github.io/manuals/instructors/))

- lead: Richard
- backup:
- backupbackup: Samantha

:::spoiler Checklist
- [ ] Confirm that each lesson and session has co-instructors
- [x] One instructor per lesson assigned
- [x] Co-instructors found
- [x] Schedule general instructor call
- [x] 8.8 at 13 CEST
- [ ] Schedule calls with each instructor pair to distill most important questions and tasks to them (or inform in general meeting to meet with co-instructor)
- [ ] Show where the detailed schedule is and recommend to move it to instructor guide
- [ ] Discuss that the detailed schedule can and should be improved
- [ ] Show where Q&A and feedback from past workshop can be found
- [ ] Discuss plans for exercises: try 3 exercises each half-day, each not shorter than 20 mins
- [ ] Ask them to check their lesson's exercise list
- [ ] Ask for any software requirements changes
- [ ] Inform about audience (at the time of writing half of registrants prefer to follow on their own) - adapt exercise expectations to audience
- [ ] Check/test for high-quality screen share
- [ ] Discuss how we can give learners get a good experience
- [ ] Test software install instructions
- [ ] List instructors on the website (with exercise coordinator)
- [ ] Organize team leader on-boarding sessions (with exercise coordinator)
- [ ] After the workshop copy detailed schedule to the individual lesson repos as issues
:::

### Exercise and team leader coordinator
([description](https://coderefinery.github.io/manuals/exercise-coordinator/))

- lead:
- backup: Samantha (in contact with local classroom hosts and some helpers)

:::spoiler Checklist
- **Before the workshop**
- [ ] Make sure exercise list is communicated (with outreach and marketing coordinator)
- [ ] We propose putting it in the schedule as subtitles for each session.
- [x] List all team leads (who consent to being listed) on the website (with instructor coordinator)
- [x] Organize staff & helpers on-boarding sessions (with instructor coordinator) -> separate chats offered
- [x] Send team leader onboarding summary email + save it to the website (with outreach and marketing coordinator)
- **After the workshop**
- [ ] Organize a de-briefing call with team leads to learn about their experiences and suggestions
- [ ] Help other roles in putting everybody who contributed and consents on the [website as credit](https://github.com/coderefinery/coderefinery.org/blob/main/content/about/contributors.md)
- [ ] After the workshop remove the [exercise repositories](https://coderefinery.github.io/git-collaborative/guide/#preparing-exercises)
- [ ] Help event director with post-workshop survey
:::

### Outreach and marketing coordinator
([description](https://coderefinery.github.io/manuals/workshop-marketing/))

- lead: Samantha
- backup:

:::spoiler Checklist
- [x] Create/update [advertising texts](https://github.com/coderefinery/template-workshop-webpage/tree/main/content/communication) and relevant news on the workshop page
- [x] Newsletter
- draft: https://hackmd.io/@coderefinery/july25_newsletter
- [x] Advertising texts on the workshop page
:::

#### Channel collection:

- [x] CodeRefinery Social Media
- BlueSky
- LinkedIn
- Mastodon
- [ ] Partner social media
- [ ] CHCAA LinkedIn (Aarhus University)
- [x] CodeRefinery newsletter
- [x] CodeRefinery ambassadors
- [ ] Partner newsletters
- [ ] NAISS (save the date announced before summer, new newsletter soon)
- [ ] NRIS
- [ ] ENCCS
- [ ] CSC (will happen automatically in Aug)
- [x] CSC data support network newsletter
- [ ] Aalto (HR training newsletter in beginning of Sep)
- [ ] Partner and friends websites training calendars
- [x] CSC (https://csc.fi/en/training-calendar/coderefinery/)
- [ ] ENCCS
- [ ] NRIS
- [ ] DeIC
- [ ] UiT
- [ ] Aalto (general event calendar)
- [ ] NAISS
- [ ] NTNU
- [ ] Avointiede.fi (https://avointiede.fi/fi/tapahtumat) (e-mail to [e-mail], sent but no answer)
- [x] HI (https://hi.is/vidburdir/coderefinery_workshop)
- [ ] AU (Aarhus University)
- [x] DTU (https://www.bibliotek.dtu.dk/en/calendar/coderefinery-09092025?id=d2fa87ed-efb3-49bd-86de-7a54d043b3ae)
- [x] UiO (https://www.ub.uio.no/english/courses-events/courses/coderefinery/time-and-place/2025-09-9-coderefineryWorkshop.html)
- [x] Elixir TeSS: https://tess.elixir-europe.org/events/coderefinery-workshop-017a0dc4-bef4-4bd5-8cfa-0f52895dcd3c
- [x] UH (some community news section via Alan)
- [ ] ...
- [ ] Partner and other email lists
- [ ] Aalto STEM students
- [ ] Aalto triton users
- [ ] Delta doctoral network
- [ ] UiB researcher
- [ ] UiB HPC
- [ ] NERSC Bergen
- [ ] Bjerknes Bergen
- [ ] University of Oslo computational biology
- [ ] University of Oslo Phd and Postdocs
- [ ] University of Oslo Dcince contact (?)
- [ ] Research institutes in all countries
- [ ] KIT:
- [ ] horeka-users
- [ ] scc-hpc-dic
- [ ] uc-users
- [ ] rse-announce
- [ ] ...
- [ ] Partner and friends posters
- [ ] Aalto (CS,U,NBE,PHYS,VAARE)
- [x] DeIC
- [x] KTH
- [ ] ...
- [x] Chats
- [x] CodeRefinery Zulip events
- [x] NeIC general
- [x] Soc RSE
- [x] Elixir
- [x] ReSA
- [x] CSCCE
- [x] Turing Way
- [x] Women in HPC
- [x] deRSE
- [x] DRA
- [ ] ...

### Certificate coordinator
<https://coderefinery.github.io/2023-03-21-workshop/certificates/>

- lead: Enrico
- backup: ASC team (the process can be run by anyone and we are now using a ticketing system to track requests)

:::spoiler Checklist
- [ ] Update text on event page abut certificates. Old instructions were temporarily removed because they were on old format
- [ ] Make sure that instructions on certificates are disseminated multiple times
- [ ] Workshop page, emails

	- Learner sends materials to scip _at_ aalto.fi. This opens a ticket in Aalto "esupport" system
	- The person who generates the certificate verifies quickly that the tasks were completed.
	- We then work with https://github.com/coderefinery/generate-certificates to generate PDF certificates
	- Certificate is sent to the person and ticket is closed
	- Aalto specific:
	    - The local version of that repository is at /scratch/rse/generate-certificates/. The commands were slightly modified so that the default working directory is not the home folder
	    - Aalto students can also obtain directly the 1 ECTS credit. See internal process at ASC pages.

:::

---

## Registration confirmation e-mail

You can follow the workshop lectures via Twitch in a web browser, no account needed:
- https://twitch.tv/coderefinery

Please use this collaborative document to ask questions during the workshop:
- https://notes.coderefinery.org/workshop-2025-sep

Schedule and lecture material:
- https://coderefinery.github.io/2025-09-09-workshop/#schedule

We archive all our emails to registrants here in case you signed up later:
- https://coderefinery.github.io/2025-09-09-workshop/communication/

Please install required software before the workshop (ideally in the week before the workshop but not earlier):
- https://coderefinery.github.io/installation/

If you have any questions, please write to [e-mail].

Best regards,

the CodeRefinery team

---

## Meeting agenda and notes

### 2025-08-08 (13 CEST) Instructor meetup

#### Attending:

- Radovan (Tromso; looking forward to preparing an updated version of modular code development)
- Gregor Decristoforo (Tromsø - RSE /HPC group at UiT)
- Richard (Aalto, long time member, trying to pass on what I know to the next generation)
- Andrew Mashchak (Tromso/UiT - HPC/RSE group - New member - Focus: Statistics / R)
- Ina Pöhner (UEF, Finland - mainly a drug discovery/AI researcher, but enjoying some coding/FAIR and teaching)
- Sabry Razick()
- Yu Tian (Aalto, RSE, joined the teaching last year, enjoying it.)
- Jarno (Aalto, RSE, teaching CR for a long time, this time will handle streaming)
- Thomas Pfau (Aalto, RSE, enjoying teaching in Coderefinery)
- Hemanadhan Myneni (UICE, Iceland)
- Michele Mesiti (Karlsruhe, RSE/RSE support, taught a bit this year and supported before)
- Hossein (Aalto, RSE)
- Oskar Taubert (CSC) first time instructor, mosly ML but also some RSE.

#### Notes

- Please register to the workshop: https://indico.neic.no/event/282/
- What we are doing today
- Show instructor [manuals](https://coderefinery.github.io/manuals/) - mostly reading materials
- Kickoff the insturctor preparation
- Instructor distribution (below) ok?
- Finding co-teachers: Anyone want and have time to take a second lesson? -> Fill "??" spaces
- Lesson preparation
- Check past Q&A, e.g.: https://coderefinery.github.io/2025-03-25-workshop/questions/
- Section: https://coderefinery.github.io/manuals/lesson-review/
- What changes this time: more exercises for week 2 than last time.
- !! Install instruction updates (deadline: *before* September; first install help session is Sep 3)
- !! Demos back to exercises might require some updates in your lesson
- Try to make the text suitable for either: there shouldn't necessarily be intrinsic changes
- Learners will need more time than for demos
- Learners will need more explicit instructions (and stuff needs to work perfectly the first time)
- !! Timing (except git lessons): More time to exercises than in earlier workshops, check earlier feedback and instructor notes
- During exercises, do we ask if the learners need more time?
- we ask learners to communicate back to us via notes how it goes (whether they wished more time), actually giving more time and extending a session is then difficult but knowing how it goes in exercises is useful and it can help us adjusting next exercises. at the minimum we can comment on it. bottom line: we want to give learners the feeling that they are heard (read) although we might not be able to see them.
- Teaching practices
- Section: https://coderefinery.github.io/manuals/instructor-intro/
- Includes for example audio, screenshare, livestream, team teaching, presentation hints
- !! Arrange two-on-ones (two instructors and RD) for each lesson.-
- Livestream practice
- Real teaching demo with all the parts
- Scheduled ~1 week before week 1
- Instructor training needs and possibilities
- Practical tech test
- AOB
- The shell crash course from last workshop seems to have been dropped. We should somewhere clarify why and at least link to it from somewhere in the new workshop.
- Can we provide **zoom room where people can pop in and ask question** and MM would be happy to be there in parallel to answering notes questions? There might not be much interest from learners but it would be relatively low effort to try.
- Yes. Michele to create zoom with code to claim host. Day 6: Michele cannot be there, EG can be host.

## Communication

+++
title = "Getting ready for day 2 and 3 of CodeRefinery workshop"
[extra]
subject = "Getting ready for day 2 and 3 of CodeRefinery workshop"
+++

Hi,

Thank you for joining us today!

You may find the archived questions and answers at https://coderefinery.github.io/2025-09-09/workshop/questions/.
If you'd like to revisit or catch up with some of the episodes, you may find the videos on Twitch https://twitch.tv/coderefinery for another week. Recordings will later be uploaded to our YouTube channel: https://www.youtube.com/@coderefinery .

**If you missed day 1, you may still join the rest of the workshop; prerequisites for day 2 are knowing the basics of git.** And even without those, you should still be able to follow and do the exercises.

### Preparations for day 2

Having the local editors available on your computer is good: VS Code or command line. See the second option on installation (https://coderefinery.github.io/installation/). If you don't have these, you can still attend and there are some steps you can do without editors, and you'll learn for the future.

### Preparations for day 3

On Thursday we will all practice how to collaborate using Git/GitHub and one ambitious thing we will try is to collaborate with participants following via stream.

**Day 3 for individual learners**
If you would like to participate as **individual learner** in the collaborative exercises, **please request access by opening an issue at
https://github.com/cr-workshop-exercises/access-requests/issues/new?template=access-request.md (there click the green button "Create" on bottom right)**.

This way we will know your GitHub username and give you write access to exercise repositories.

After we add you as collaborator, you will get an email from GitHub.

Please **accept the invitation** so that on Thursday you can do the exercise on our shared repository.

Don't forget to "unwatch" both https://github.com/cr-workshop-exercises/centralized-workflow-exercise and https://github.com/cr-workshop-exercises/centralized-workflow-exercise-recorded to make sure you don't get too many emails during the exercise.

To "unwatch", go to the repository and click the "Unwatch" button (top middle of the screen) and then select "Participating and @mentions".

**Day 3 for learners in local classrooms or teams**
If you are learning with others as part of an in-person room or a virtual team, your local coordinator will take care of preparing the shared git repository for doing the collaborative exercise with other participants in the room. If you are the coordinator you'll receive a separate email from us with more detailed instructions.

---

**How to follow the workshop**
As usual the links for the following days will be:

Workshop page: https://coderefinery.github.io/2025-09-09-workshop/
Installation pre-requisites: https://coderefinery.github.io/installation/
Twitch-TV stream: https://twitch.tv/coderefinery
Interactive Q&A document: https://notes.coderefinery.org/workshop-2025-sep
Zoom room for further live help during exercises: https://aalto.zoom.us/j/69608324491

Best regards,
Enrico, on behalf of the CodeRefinery team

# another email
-----ANOTHER EMAIL HERE BELOW----

## Email for coordinators of in person rooms

Subject: CodeRefinery exercise leads, preparation for Day 3

Dear classroom hosts and exercise leads,

You are receiving this e-mail because you have indicated in some way that you are hosting a classroom or joining with a team for the CodeRefinery workshop.

First: it's amazing that you provide a space to learn together for the CodeRefinery workshop! We know it's still a day ahead, but never too early to prepare: For day 3 we do collaborative git version control, and that requires you to prepare some repositories in advance so that the learner in your room can collaborate using the repository you have created.

Please have a look at all exercises for day 3 (https://coderefinery.github.io/2025-09-09-workshop/exercises/#day-3), there are step-by-step instructions on how to prepare these git repositories for your learners to work with.

For example, for the first exercise of day 3 https://coderefinery.github.io/git-collaborative/same-repository/#exercise you see that in the tab "Part of team/exercise room" there are a few steps for the **maintainer** (you! (or one of you if you have multiple helpers)) to generate the new repositories under your own github handle, and to add the learners as collaborators to your repository. (You will also need to create a repository for the third exercise of day 3 https://coderefinery.github.io/git-collaborative/forking-workflow/#exercise.) It is good to do this before day 3 sessions start.

If you would like support with setting things up, please visit our "additional installation help" session on Wednesday, 2 hours before the workshop starts (https://aalto.zoom.us/j/69608324491)

Please do reach out via [e-mail] or join our Zulip chat (https://coderefinery.zulipchat.com) if anything is unclear.

---
# emails of post day 2 (10/9/2025)

+++
title = "Getting ready for CodeRefinery day 3 with git version control!"
[extra]
subject = "Getting ready for CodeRefinery day 3 with git version control!"
+++

Hello!

Today we covered the basics of git and tomorrow we will collaborate together using git and GitHub. If you missed today (or yesterday) it is still possible to fully enjoy tomorrow and do exercises together.

**A short reminder on what you need to do before tomorrow**

Tomorrow we will all practice how to collaborate using Git/GitHub and one ambitious thing we will try is to collaborate with participants following via stream.

If you would like to participate as **individual learner** in the collaborative exercises, please request access by opening an issue at
https://github.com/cr-workshop-exercises/access-requests/issues/new?template=access-request.md (there click the green button "Create" on bottom right).

This way we will know your GitHub username and give you write access to exercise repositories.

After we add you as collaborator, you will get an email from GitHub.

Please accept the invitation.

Don't forget to "unwatch" both https://github.com/cr-workshop-exercises/centralized-workflow-exercise and https://github.com/cr-workshop-exercises/centralized-workflow-exercise-recorded to make sure you don't get too many emails during the exercise.

To "unwatch", go to the repository and click the "Unwatch" button (top middle of the screen) and then select "Participating and @mentions".

That is all for today. You may find today's video on Twitch https://twitch.tv/coderefinery for another week. Recordings are also being uploaded to our YouTube channel later next week.

Have a great evening!
Enrico, on behalf of the CodeRefinery team

---

## Post day 3 email

+++
title = "Week 1 summary"
[extra]
subject = "Week 1 summary (and a survey for those who could not make it)"
+++

Dear all,

Thank you so much for your active participation during the first week of the CodeRefinery workshop!

**If you could not join us this week, could you let us know why? [Take this 15-seconds-survey](https://link.webropolsurveys.com/S/BCA7C9465741A5AC)**.

We try to minimise overlaps with conferences and other events, so we would like to know what stopped you from joining us this week.

We are especially grateful to all the exercise leaders and expert helpers for their additional effort during the exercise sessions. We could not have a workshop of this scale without you!

We hope that our Git lessons have made you more comfortable using Git for your solo- and collaborative- projects. Of course, we would have loved to show a lot more if we had the time. If you have ideas on how to improve them (some ideas were already noted in the collaborative document), please open issues at https://coderefinery.github.io/git-intro/ or https://coderefinery.github.io/git-collaborative/, or even better, send us pull requests.

During next weeks we'll take best practices for software development to the next level, by learning about documentation, testing, reproducibility, software licensing, and more. We'll start using additional tools. If you have not yet set up your Conda environment, please do so during the following days: https://coderefinery.github.io/installation/.

**The following episodes are self-contained,** so you can pick the one(s) that are more relevant to what you need in your research. Please note that the starting time and duration have changed now.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice weekend and see you on Wednesday!

the CodeRefinery team

--
Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at https://coderefinery.org/about/code-of-conduct/.

## Pre day 4 email

+++
title = "Before day 4 - Reproducibile research"
[extra]
subject = "Before day 4 - Reproducible research"
+++

Dear all,

Thank you so much for your active participation during the first week of the CodeRefinery workshop!

**If you could not join us last week, could you let us know why? [Take this 15-seconds-survey](https://link.webropolsurveys.com/S/BCA7C9465741A5AC)**.

Tomorrow, Wednesday 17/September, we start our weekly series of self-contained events focused on specific topics.

Have you ever done something with your computer/code, and couldn't do it again? A bit of a problem, since science is supposed to be reproducible, isn't it?

Tomorrow's episode is the core element of the whole CodeRefinery workshop: **reproducible research**! We connect all the pieces and consider reproducibility from the level of the lines of code we write, to the scale of the systems and computers we use.

For the exercises tomorrow we will use some simple python scripts (it's ok even if you are not a python user). If you have not yet set up your Conda environment, please do so during the following days: https://coderefinery.github.io/installation/.

If you have issues with conda installation and want to verify your installation before the workshop, join us in our zoom room from 9am Oslo/Stockholm/Rome time zone at https://aalto.zoom.us/j/69608324491.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice rest of the day and see you tomorrow!
the CodeRefinery team

--
Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at

-------

## Pre day 5 email

+++
title = "Before day 5 - Social coding"
[extra]
subject = "Before day 5 - Social coding"
+++

Dear all,

Thank you so much for your active participation during the first four days of the CodeRefinery workshop. We have had more than 700 views so far, we are happy to see that you find our training useful! You can find recordings of the past episodes at the [CodeRefinery YouTube channel](https://www.youtube.com/watch?v=4fwmkB2A6Vs&list=PLpLblYHCzJAAqSSVAwHUuipB5hhW6GobY).

**If you could not join us so far, could you let us know why? [Take this 15-seconds-survey](https://link.webropolsurveys.com/S/BCA7C9465741A5AC)**.

Tomorrow, Wednesday 23/September, we continue our weekly series of self-contained events focused on specific topics.

Tomorrow's episode is dedicated to **social coding**: open-source software, software licenses, and how to publish your code. To work in modern science, you need to build on the work of others - both scientific and code. Can you copy code from Stack Overflow? Can you copy from your colleagues? Can you copy form ChatGPT? Does your code and data exist after you leave your position? We'll discuss all these and more.

The exercises tomorrow will not require any Python or git.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice rest of the day and see you tomorrow!
the CodeRefinery team

--
Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at

---

## Pre day 6 email

+++
title = "Before day 6 - Documentation"
[extra]
subject = "Before day 6 - Documentation"
+++

Dear all,

Thank you so much for your active participation during the first days of the CodeRefinery workshop. We are still working on past recordings, you will find them at the [CodeRefinery YouTube channel](https://www.youtube.com/watch?v=4fwmkB2A6Vs&list=PLpLblYHCzJAAqSSVAwHUuipB5hhW6GobY).

**If you could not join us so far, could you let us know why? [Take this 15-seconds-survey](https://link.webropolsurveys.com/S/BCA7C9465741A5AC)**.

Tomorrow, Wednesday 1st/October, we continue our weekly series of self-contained events focused on specific topics.

Tomorrow's episode is dedicated to **documentation**:
Why is project documentation important? What tools are available for creating documentation pages? How do I create github.io web-pages?

The exercises tomorrow will require Python or and the CodeRefinery conda environment.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice rest of the day and see you tomorrow!
the CodeRefinery team

--
Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at [this link](https://coderefinery.org/about/code-of-conduct/).

## Pre day 7 email

+++
title = "Before day 7 - Jupyter notebooks"
[extra]
subject = "Before day 7 - Jupyter notebooks"
+++

Dear all,

Thank you so much for your active participation during the first days of the CodeRefinery workshop.

Tomorrow, Wednesday 8th/October, we continue our weekly series of self-contained events focused on specific topics.

Tomorrow's episode is dedicated to **Jupyter notebooks**:
Have you ever wished your code, data, and explanations could live together in one beautiful, shareable document? How are Jupyter notebooks used in research projects?

The exercises tomorrow will require Python or and the CodeRefinery conda environment.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice rest of the day and see you tomorrow!
the CodeRefinery team

--
Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at [this link](https://coderefinery.org/about/code-of-conduct/).

----

## Email before day 9

Dear all,

Tomorrow, Wednesday 22nd/October we will have the last session of our autumn CodeRefinery workshop called "modular code development".

Tomorrows episode brings all the other lessons of the workshop together by discussing and applying them on an example code through live coding. The examples will be in Python, but the process is also applicable to other programming languages. So please do still join, even if you are not programming in Python.

If you want to follow the session on your own computer with Python you will need the CodeRefinery conda environment setup (https://coderefinery.github.io/installation/conda/), but this is not mandatory. We encourage you to participate actively through discussions in the collaborative notes and by sharing your suggestions during the live coding.

If you'd like to receive a certificate of participation, please do not delete your Git repositories yet and have a look at https://coderefinery.github.io/2025-09-09-workshop/certificates/.

- Q&A archive: https://coderefinery.github.io/2025-09-09-workshop/questions/
- Past emails: https://coderefinery.github.io/2025-09-09-workshop/communication/

Have a nice rest of the day and see you tomorrow! the CodeRefinery team

---

Privacy! You are receiving this email because you registered for the next CodeRefinery workshop. If your plans have changed, you can update your registration by visiting https://indico.neic.no/login/?next=/event/282/ or by contacting us at [e-mail] . Please consider subscribing to our newsletter to get information about upcoming events https://coderefinery.org/about/newsletter/. You can check the code of conduct for the workshop at this link: https://coderefinery.org/about/code-of-conduct/.

---

## After workshop e-mail

Subject: [CodeRefinery workshop] Thank you, summary and feedback

Dear all,

Thank you very much for participating the autumn CodeRefinery workshop 2025! Special thanks to all the helpers, instructors, and organisers.

We'd like to know how this workshop went for you. Please give us honest feedback about what went well and what didn't go so well, either by adding it to our notes document (https://notes.coderefinery.org/workshop-2025-sep?edit , open until end of this week) or by writing to [e-mail].

We recognize that applying all these tools and techniques is not easy. Don't try to do things perfectly, try to do things better. Ask for help and work together.

All of our lessons can be found at https://coderefinery.org/lessons/. They are open source and will stay open and accessible also in future. They are now also citable, see https://coderefinery.org/lessons/reusing/. Please open issues with suggestions and please send us pull requests with improvements.

The workshop outro includes links to different places with more training around scientific computing as well as where to find local support: https://github.com/coderefinery/workshop-outro

Recordings of all sessions will be available on our youtube channel: https://www.youtube.com/@coderefinery

If you would like a certificate or credit for the workshop, please see: https://coderefinery.github.io/2025-09-09-workshop/certificates/.

If you would like to stay informed about future events, please sign up for our newsletter: https://coderefinery.org/about/newsletter/.

We can already mention that our next online workshop is "Python for Scientific Computing" 25+26+27/Nov/2025 https://scicomp.aalto.fi/training/scip/python-for-scicomp-2025/ Maybe see you there?

Thank you for your time and feedback.

the CodeRefinery team