Registration
There is no deadline and you are welcome to register and join even after the event started. You can attend just those days or sessions you want but please register anyway.
Should all in a team sign up? Or only one person? We recommend that all register so that they get all necessary information.
If you want to join as organization to provide local helpers or in-person sessions, please do! This usually takes the form of a "watching party" with coordinated breaks for exercises.
Some organizations offer their own registration form. In this case please register with them and then you do not have to register here centrally as well. We will then make sure that everybody gets all necessary information.
Schedule
All times are displayed in the local timezone of your browser. Detected timezone offset compared to UTC:
Breaks: 10 minutes every hour, between xx:50 and xx:10, but it is difficult for us to indicate exactly when.
|
Installation help |
|
| , - | Installation help for everybody |
|
Day 1 |
|
| , - |
Welcome and introduction
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 1/4
Why we want to track versions and how to go back in time to a working version: Motivation, Browsing, Commiting
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 2/4
Presenters: TBA
|
|
Day 2 |
|
| , - |
Introduction to version control with Git - part 3/4
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 4/4
Presenters: TBA
|
|
Day 3 |
|
| , - |
Collaborative distributed version control - part 1/2
Presenters: TBA
|
| , - |
Collaborative distributed version control - part 2/2
Presenters: TBA
|
|
Day 4 |
|
| , - |
Reproducible research
Preparing code to be usable by you and others in the future
Presenters: TBA
|
| , - |
Social coding and open software
What can you do to get credit for your code and to allow reuse
Presenters: TBA
|
|
Day 5 |
|
| , - |
How to document your research software
Presenters: TBA
|
| , - |
Jupyter notebooks
A tool to write and share executable notebooks and data visualization
Presenters: TBA
|
|
Day 6 |
|
| , - |
Automated testing
Preventing yourself and others from breaking your functioning code
Presenters: TBA
|
| , - |
Modular code development
Making reusing parts of your code easier
Presenters: TBA
|
| , - |
Concluding remarks, general Q&A, and where to go from here
Presenters: TBA
|
Be a team leader
Do you know some of the topics, but want to review them? Do you wish your colleagues or friends would use these tools? Why not attend as a team leader? Gather some friends who want to learn the topics and follow the workshop together. You don't need to be an expert: if you have been through CodeRefinery once or have some familiarity with the topics, and you are confident to call an expert helper when needed, then you have all it takes to lead a team to success, or lead even more people and join as an organization (see below).
Be a Q&A helper
Help us answer questions from the participants in the online Q&A document (collaborative notes).
Partners and local exercise groups
Some partners offer local support, such as breakout rooms, to their local teams. You can become a partner to support your community!
We collect here the exercise groups that we know:
- Aalto University:
- Local in-person exercise session and local support.
- Possibility of credit points to those in Finland.
Instructors
- ...
Workshop organizers
- ...
On-boarding
- ...
Outreach
- ...
Recording and broadcasting
- ...
Local organizers
- ...
Collaborative notes managers
- ...