These guidelines are work in progress and only a first draft
The CodeRefinery project provides open lesson materials that can be reused freely under a CC-BY license. We also organize and support workshops based on these materials.
This document defines what qualifies as a CodeRefinery workshop and sets out the criteria for using this label. While we strongly encourage reuse and adaptation of our materials, the term "CodeRefinery workshop" should be used only when specific conditions are met. This ensures consistency, maintains quality, and protects the reputation of the project.
A CodeRefinery workshop is an educational event that teaches tools and techniques around programming for research, using the CodeRefinery teaching approach and materials. These workshops are grounded in open science principles and designed to be inclusive, collaborative, and practically focused for learners across scientific domains.
There are two main categories:
1. The CodeRefinery workshop
This refers to the core, multi-day "tools" workshop that covers key topics such as version control, reproducibility, modular code, and documentation. It is typically taught online by a team of instructors, using live coding and a collaborative document.
2. Other CodeRefinery workshops
These include additional workshops developed or endorsed by CodeRefinery (e.g., "Python for Scientific Computing", "Tools and techniques for HPC") which also follow the CodeRefinery teaching philosophy and use its infrastructure.
To refer to your event as a CodeRefinery workshop, you must meet all of the following minimum requirements:
Affiliation
At least one organizer or instructor must:
Connection and communication with the project
This helps us track impact and include your event in our reporting and community updates.
Note: If the workshop is open to external participants, the CodeRefinery team can help advertise it.
These aren’t mandatory, but they are strongly encouraged to preserve the CodeRefinery spirit:
You’re welcome and encouraged to use CodeRefinery materials in your teaching!
However, if your event doesn’t meet the criteria above, please don’t call it a “CodeRefinery workshop.”
Instead, feel free to say that your event:
Please avoid suggesting an official affiliation if one doesn’t exist.
These criteria help us:
When in doubt, please contact support@coderefinery.org.
END of draft
Answers from team (during kick-off)
I think that anything being taught can be linked to CodeRefinery as long as the person teaching has gotten approval from a CodeRefinery team member and the teaching follows the principles that CodeRefinery embodies.
There is THE CodeRefinery workshop (the "tool" workshop) and then there are other CodeRefinery workshops (TTT4HPC, python for sci comp)… Maybe if materials are hosted under coderefinery organisation and/or if streaming or youtube is under coderefinery, then it is a coderefinery workshop…?
The workshop need to use 2/3 to 3/4 of the CodeRefinery Material.
Open material distribution, Open access to the course, online distribution and inclusion, questions presented and answered in some form of collaborative document (were participants can edit)
Live coding content paced in a way that students can follow along.
Having never attended or taught a CodeRefinery training yet, I do not have an intuition for this.
I guess if both the organizers of the workshop and some fraction of the CR instructors agree, it could be branded as such.
Can we go through and identify what should and shouldn't be, from our examples (main lessons at our partners).
I'd like to hear what others think, because I'm not sure. First thoughts to me:
To me it's almost synonomous with a workshop which is: user-centric (for diverse new learners, not highly specalized), online, livestream, with good exercises and open materials
I think we should be fairly strict with letting activities and event be held and announced with referral to the CodeRefinery name. To my knowledge use of our material and referral to the CodeRefinery have commonly been in done in a context where our materials have been used, people on the team have been involved