# CodeRefinery project meeting at NeIC AHM 2025

:::info
- September 22.+23.2025
- Tallinn, Estonia
- Full days
- Monday starting with lunch (see timetable on registration page (link in e-mail))
- Tuesday is time for project meetings.
- Location: Hilton Tallinn Park, Fr. R. Kreutzwaldi 23, Tallinn, 10147, Estonia
- Dinner: Platz, Address Roseni 7, Tallinn ,Webpage
https://www.platz.ee/en/
- Tuesday zoom room: https://cscfi.zoom.us/my/samwi
:::

:::warning
- travel costs covered for CodeRefinery team
- CodeRefinery steering group can join on own costs
:::

Timetable: https://docs.google.com/spreadsheets/d/15s1jJ4Rlgw4pIjGkc4A3adoNQeN_ipInB8EPIZsYS8Q/edit?usp=sharing

## Welcome and practicalities (15min)

- Timetable
- Notes
- Summary

## Introductions (30min)

- How did you first get to know about/connect to CodeRefinery?
- A "value" you think the CodeRefinery community has that speaks to/ is important for you

> **Core Values:** values we are not willing to compromise; **Aspirational values:** Values we don't have yet, but strive for them; **Behavioral values:** minimum expected behaviour; **Accidental values:** common interest/culture

- I could provide instructor training on ...
- I would like/need instructor training on ...

## Installation instructions update

The install instructions are one of the first points of contact with CodeRefinery work. They can make or break someone's participation (and the breaking point can even happen weeks after the install!). They are also useful for people in general setting up for scientific computing.

Installation is also very important for general computing work. Everyone has to install some stuff when they start work, and different fields have adopted best practices (= what is most usable for them, and lets their people get started as soon as possible). We should follow those best practices, not invent new things ourselves.

Yet, they haven't been re-thought for a while. There are uncoordinated changes to fix problems and update for workshop formats. We can do better, so we will: we'll take some time now to do a complete re-thinking and revision (this is like we did for git-intro at at a Tromso meetup in 2024). The rethinking at is the important part to do at the AHM. The details can be written later.

The goals:

- For every operating system, think about how beginners, in 2025, are likely to get set up for git and conda. Practical, not pedantic.
- Also think of which ways are least likely to go wrong (there's probably overlap with the above, but still, it needs considering). Also, if things do go wrong, how to do it
- This may mean less command line than we would do. That's OK: practical, not pedantic.
- We should carefully study best practices for every operating system, university-managed computers, etc. How uniform can we make things? How user-friendly? How user-friendly without reading docs about command line stuff? Etc.
- For example, in the git-intro revision, we realized that almost everyone uses VScode, and that is a much more usable interface. So we went with that as the default local starting point. It's not perfect, but it's what people would probably learn anyway.

## Connecting to the RSE ecosystem

RSE training ecosystem: https://hackmd.io/@coderefinery/RSE_train

For researchers:

Where are we wrt FAIR Training materials (according to https://doi.org/10.5281/zenodo.3593258):

1. Share - GitHub ✔️
2. Describe properly - CFF but no full metadata 🛠️
3. Give unique identity - Zenodo DOI ✔️
4. Register online ❎
5. Define access rules - open ✔️
6. Use interoperable format - markdown, sphinx & GitHub pages ✔️
7. Make reusable for trainers - CC-BY & instructor notes ✔️
8. Make usable for trainees - audience, prerequisites & learning objectives ✔️
9. Welcome contributions - we do but no CONTRIBUTING file 🛠️
10. Keep materials up to date - before every workshop ✔️

-> Let's work on the **metadata** (https://zenodo.org/records/5276003) 8 lessons, 2-3 people per lesson (at least one should have taught that lesson before):

**Descriptions:** Text describing the topic. How the training materials are/were used and in what context.
**Keywords:** A short list of words that identify the training resource topics (maximum 10).
**Learning objectives:** A list in the form of dot points to highlight what people can expect to learn from this material. (these likely already exist in instructor guide)
**Requirements:** What is needed to follow the lesson. Knowledge & tools installed. See instructor and installation guide

-> Add to your lesson as PR or issue.

## Optimizing for the learner experience

-> collect what is important in groups of three

## What can we do in order to achieve that?

- Website
- Chat
- Workshop
- Materials
- Roles

---

## OLD: Collection of topics to work on

Please add topics you are interested in to the list, we will later decide which topics we will discuss:

- Manuals:
- Workshop roles
- Onboarding
- Bringing own classroom/team
- Lesson contribution guide
- Ongoing workshop discussion
- Core value statement
- Train the trainer
- Behind the scenes of a workshop tour
- Onboarding new people
- MOOC course using SUNET (https://sunet.instructure.com/courses/389)
- INstallation instructions hackathon (what is the best way these days to install the tools used in our workshop)
- Other than workshop roles and tasks
- Lesson maintainership
- CodeRefinery vs Carpentries: beginner & advanced, wrt to new(ish) RSE lessons also in Carpentries incubator
- Funding acquisition
- Optimizing for learning experience: What is the most important for learners to get right? -> Adapt workshop playbook!
- **add your ideas here**

## Longer descriptions