---
tags: meeting note
---

# CodeRefinery team meeting and community calls

:::info
- Date: **Every Monday**, 14-14:30 CEST / 15-15:30 EEST
- Ambassador calls +- once a month, 14-15 CET, same Zoom link
- Invited: Everybody welcome
- This document: https://hackmd.io/@coderefinery/team-meeting
- Zoom connection details: https://cscfi.zoom.us/j/66165768646
- To-Do list: https://coderefinery.org/tasks/
- New people onboarding: https://coderefinery.github.io/manuals/onboarding/
- Archive of older meetings: https://github.com/coderefinery/meeting-minutes
:::

:::warning
## Special meetings
### Ambassador meetup
19.1
30.3
1.6

### Working Group on CodeRefinery MOOC
15.12

:::

:::spoiler Working groups

## Working group

##### Installation instructions
Lead: RD
People interested: EG, RD, BL, SR, ..
More info & materials: [Notes on installation instruction rethinking session at NeIC AHM](https://hackmd.io/@coderefinery/2025installation-rethink)

##### CodeRefinery MOOC
Lead: AVM
People interested: YW, DI, EG, HM, ...
More info: See ~~[here](https://hackmd.io/@coderefinery/CR_NeIC_AHM25#Coderefinery-MOOC)~~ [for now, here](https://hackmd.io/@ashwinvis/coderefinery-git-intro-mooc) for details & [Norwegian Ai cloud report on different platforms](https://md.sigma2.no/s/kOtXo2lFa#)

##### Citable lesson continued; metadata
Lead: SW
People interested: RD (automation), AM, DPilvar, JH, ...
More info: [Blogpost on citation.cff](https://coderefinery.org/blog/2024/07/30/lesson-cffs/) and [discussion on FAIR training in chat](https://coderefinery.zulipchat.com/#narrow/channel/136238-lessons/topic/FAIR.20training/with/538551248) and [dicussion on citable lessons](https://coderefinery.zulipchat.com/#narrow/channel/136238-lessons/topic/citable.20lessons/with/537447857)

##### AI "info boxes" to existing lessons
Lead: EG
People interested: BL, OT, ...

##### R examples/updates to CodeRefinery lessons
Lead: ?
People interested: HJ, AM, RB , AV, ...
More info: We have R experts, we need coordination

##### CodeRefinery Train the trainer organization
Lead: RD
People interested: ...
More info: Whats the future of CodeRefinery train the trainer?

##### Behind the scenes tour
Lead: ?
People interested: RD, ..
More info: Quote from RB: ""behind the scenes" presentation/thing/movie/blog that shows how a training event is made. a bit like behind the scenes where they show how a TV show is made, with interviews with cast and directors and fun anecdotes."

##### Advanced git
Lead: SW
People interested: RB, (all from first meetup), BL, MM, EH,
Mor info: [First session blogpost](https://coderefinery.org/blog/open-house-git-masterclass/) and [notes for second blogpost](https://hackmd.io/@coderefinery/adv_git_blog), would be great to organize another open house on this! We had lots of people from other organizations join the first one

##### AI from user perspective lesson development
Lead: EG
People interested: BL, AM, JH, AV, HM, IP, OT, ...
More info: Additional lesson on use of AI for research, not AI development, linked to https://coderefinery.zulipchat.com/#narrow/channel/119815-general/topic/responsible.20computational.20research

##### Learner persona: Data Steward consideration for materials
Lead: SW
People interested: EG, DPilvar, (library contacts from partners), PR + nordic data stewards network
More info: How would a CodeRefinery workshop for non technical people in data support look like?

##### Social coding lesson updates + supplemental material
Lead: SR
People interested: SR, EG, BL, ...
More info: Making the lesson legally sound + supplemental interview/podcast, see also [Zulip discussion](https://coderefinery.zulipchat.com/#narrow/channel/136238-lessons/topic/social.20coding.20lesson/with/542554648)

:::

---

## 2025-01-07 Open team meeting discussion (unhosted)

## Holiday break until January 7

## 2025-12-15 Working group: CodeRefinery MOOC

Attending:

Tentative agenda: https://hackmd.io/@ashwinvis/coderefinery-git-intro-mooc
- Introductions (if new members)
- What has been done
- What is the plan
- How to work

Other:
- NoBSC (RSE / SciComp teams) meetup in Helsinki, 2-4 february: https://aaltoscicomp.github.io/NoBSC/

---

## 2025-12-08 Working group: hands-on AI topics to CodeRefinery

Let's work on a dedicated document:
https://hackmd.io/@coderefinery/codingwithai

## 2025-12-01 Team meeting

Attending: AM, OT, DI, BB, TP

- Lesson contribution guidelines:
Please review and comment on the lesson contribution guidelines, which are a mixture of our old guidelines and an example provided by Enrico: https://github.com/coderefinery/manuals/pull/280 (some more context in the PR).
- TP: Comments added in the PR

- Welcome to BB:
- The next workshop? 17.-19. and 24.-26. of March 2026
- Useful links:
- This current doc
- https://coderefinery.github.io/train-the-trainer/co-teaching/
- Teaching is via Zoom and then streamed to Twitch
- Feel free to browse the manuals and the "train-the-trainer" docs
- What is Coderefinery: collaboration or ...?
- A NeIC project
- NeIC provides funding for keeping the project alive

## 2025-11-24 Team meeting

Attending: JH, SW, OT, HM, DI, SM, RD, AM ...

- Anything to share from your work or our working groups?
- Mooc, starting soon
- git masterclass meeting coming up next friday, join if you want to
- AI topics will meet Mon 8.12 team meeting time
- R to CodeRefinery team at CSC will meet Wednesday to create issues on where to add more R to lesson repos (except modular code dev, RB working on that for now)
- Build systems course organized by NAISS (held in Nov 24, with CR partners, Nov 25 iteration called off) -> Question if it should be rescheduled to spring, look for call for instructors in chat!
- sidenote NAISS moving to GitLab
- Python4SciComp this week
- addition of uv in progress
- Congratulations to Ashwin for becoming MIMER AIF training coordinator!
- Congratulations also Uni Iceland is now LUMI AI Factory antenna!
- HM part of COST action paper related to research code and data sharing, we are excited to see the paper once it is out :)
- Short look at project plan (WIP but with steering group now):
- Highlight to "CodeRefinery, in its core, will continue to focus on enhancing training in robust research software engineering tools and techniques, "
- AMs colleague working on ISC workshop proposal on teaching HPC:
- HM interested in joining for CodeRefinery
- Streaming setup and handling: now more people at Aalto able to do it.
- RD can teach others how to do it (in-person preferred)
- Erasmus+ opportunity? :)
- Note on PEARC, new in 2026: RSE track!
- Good place to showcase your work and/or CodeRefinery -> contact SW if you are interested in submitting something. DL in Feb26
- Topics or Volunteers to host and prepare December meetings?
- Mon 8.12: AI topics to CodeRefinery

---

## 2025-11-17 Ambassadors + team: CodeRefinery workshop and materials discussion

Attending: DP (EE), JH, EH, MT, OT, MM, HM, SW, DP (NO), TP, DI

:::info
**FYI:**
- Next CodeRefinery workshop: 17.-19. and 24.-26. of March 2026, let us know if you want to bring your own classroom!
- Git masterclass discussion continues on 28.11 at 11 CET: https://hackmd.io/@coderefinery/git_masterclass_cont
- Python4SciComp 25.-27.11: https://scicomp.aalto.fi/training/scip/python-for-scicomp-2025/
- Please advertize :)
:::

Let's discuss preliminary definitions for:

- What materials belong under CodeRefinery?
- What “being under CodeRefinery” means (visibility, maintenance, governance)
- What is a CodeRefinery workshop?
- Who can run a CR workshop?

-> Proposal: https://hackmd.io/@coderefinery/CR_def

For this, we disregard what is currently hosted by CR and what not and how this is set up. Some of the things mentioned are a WIP for us (maintainer, working review system,..).

These definitions will be written into the CR4 project plan (which we can directly control).
Everything else goes through the project owner and steering group.

Summary of the definitions:

### When can you call your workshop, a CodeRefinery workshop?

A CodeRefinery workshop is an educational event that teaches research software skills using open, collaborative, and reproducible teaching practices. These workshops follow the CodeRefinery teaching approach, combining live coding, practical exercises, and inclusive, learner-centered instruction. Being an official CodeRefinery workshop means you gain visibility, access to shared infrastructure, support from experienced instructors, and recognition within the community, while contributing to the sustainability and quality of CodeRefinery.

### What it means to host materials under CodeRefinery

Hosting materials under CodeRefinery gives your lessons a home in the CodeRefinery project, providing visibility, infrastructure, and stewardship by the community. Materials must be open, maintainable, and aligned with CodeRefinery’s teaching philosophy, but in return, they benefit from GitHub hosting, community review, contribution support, and coordination with partners. This supports that your resources are discoverable, reusable, and part of a shared effort to promote sustainable, reproducible, and collaborative research software practices.

Comments and notes on the proposal:

From meeting (mainly comments on summary):
- [x] - what is CodeRefinery ecosystem? -> CR website, update wording
- [x] - Definition of CR workshop very similar to Software Carpentry
- [x] - Differences: kind of materials used (similar philosophy, CR more succint; more instructor friendly), online
- [x] - Would a software carpentry be a CR workshop? -> Should be in summary!
- [ ] - CR hosting inviting for others to host, what kind of material? -> Should be in summary!
- [ ] - Invitation to project member organizations or others
- [ ] - Readability of summary: List as bulletpoints! rather than long sentences
- [ ] - Hosting uder CR: can be developed and tested and get feedback from large community of people
- [ ] - CodeRefinery community: How big is it, more description.
- [x] - Format: Could other tools / formats be used?
- [x] - If we do accept more: Have some formatting setting that we would like to be used? -> Corporate identity? Look & feel
- [x] - More flexibility: more likely that people contribute (come with "any format"-> get support porting?)
- [x] - Using format is encouraged, should be interoperable!
- [x] - from chat: I'm a bit of two minds. Sticking with one stack/approach has the benefit of L&F but also let's you become you looking "old fashioned" at some point. While allowing a large variety leads to a lot more "maintenance ballast".
- [ ] - When should material not be hosted under CodeRefinery?
- [ ] perhaps this "cohesion" argument could hold:
- [ ] - Probably, material that would be referenced in existing CR material should be hosted under CR
- [ ] - Material that would only reference existing CR material but not be referenced in it should not be hosted under CR
- [x] - Make sure that intent of this defintion, "when someone asks" vs advertizing it, is clear.
- [ ]

## 2025-11-10 Team meeting

Attending: BL, HM, YLW, JH

- Short meeting. Brief updates on status of events in November
- Discussion on what events are planned for first half of 2026

## 2025-11-03 Instructor debrief

-> Separate Notes document: https://hackmd.io/@coderefinery/CRfall25_instructor_debrief

## 2025-10-27 Workshop classroom debrief

Attending: YW, AM, RD, BL, MM, HM, EH, AV, AJ, JSH, DI, JSJ, EP, RL

-> Separate Notes document: https://hackmd.io/@coderefinery/CRfall25_classroom_debrief

Thoughts for next time: Breakoutroom discussion on an issue, like no shows, advertising (sharing value of in-person), etc?

## 2025-10-20 Team meeting

Attending: eh, bl, ot, rd, sw, dp, yw, sr, eg

- (A topic you would like to discuss here)
- Date suggestions for the compact format CodeRefinery spring workshop: **17.-19. and 24.-26. of March 2026** -> https://coderefinery.zulipchat.com/#narrow/channel/316508-coderefinery-tools-workshop/topic/Spring.202026/near/545549808
- Format: 6 half days (Tue-Thu) in 2 consecutive weeks
- Exercises:
- Week 1: yes
- Week 2: not unless more time?
- Comments: extend a bit and do exercises, exercises are good, have one simpler and one more complicated exercise, instructors need to take into account to have good exercises to do (not just a "follow the instructions"), some topics are more lecture and others more exercise -> identify which exercises were liked and keep these (exercises should be more in first part when people still have energy)
- Extend by half an hour for week 2
- How about the one hour break?
- shorten to half an hour
- Sessions: as before, but replace Jupyter with AI use in research session? "responsible coding with AI tools"
- Enrico can provide a sceleton of his original lesson
- Working group (see above to sign up) exists and can work however you want, contact the lead -> Enrico
- Python for scientific computing, instructors wanted: https://coderefinery.zulipchat.com/#narrow/channel/298221-python-for-scicomp/topic/2025.20run/with/545236832
- event page: https://scicomp.aalto.fi/training/scip/python-for-scicomp-2025/ -> will also be streamed, ie classrooms may be a possibility

---

Older meeting notes: https://github.com/coderefinery/meeting-minutes/blob/main/archive.md