CodeRefinery team meeting and community calls

--- 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 (no AI notes bots allowed) - 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 1.6 ::: :::spoiler Working groups ## Working group ##### Installation instructions Lead: RD People interested: EG, RD, BL, SR, LF,.. 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#) ##### Behind the scenes tour Lead: BT 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." ##### 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) ##### Learner persona: Data Steward consideration for materials Lead: SW People interested: EG, DPilvar, (library contacts from partners), PR + nordic data stewards network, DP, FR (data formats) 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) ##### EVITA Lead: BL People interested: SW, ... More info: Find out what would be in it for CodeRefinery to submit lessons and what we would need to do to submit them. ##### JOSE paper Lead: HM, SW People interested: DP, ... More info: Find out what are the requirements and restrictions. Draft a paper on CodeRefinery workshops for JOSE, invite collaborators. Goal: workshop overview. ::: --- ## 2026-05-18 Attending: FR, SW - FYI: Bahar will bring a CodeRefinery poster to Nordic-RSE conference :tada: - FYI: NeIC is setting up 7 fora to discuss different topics of interest to the national e-infra providers. Suggestions for people to include from your organization? This is for the planners and discussers, the **big-picture people**; not (yet) the executors/receivers 1. Object Storage - upskill of technical staff competencies 1. Upskill of technical staff competencies 1. Security 1. Sensitive data 1. Nordic transparency 1. Nordic Scientific Computing 1. Nordic Research Software Engineering (NRSE) - FYI: Potential possibility to team up with CSC HPC experts for hackathon on RSE & performance optimization for HPC --- - Lesson editors/maintainers - https://coderefinery.github.io/manuals/lesson-editor/ - Monthly lesson specific meetings? Once per month, every second Monday of a month? - Could start with every lesson maintainer introducing their lesson, challenges - Sign-up for interest: * git-intro: DI, .. * git-collab: ..,.. * reproducible research: SW , .. * social coding: (RB), .. * AI coding: BT, .. * documentation: AM, MM, .. * testing: FR, .. * modular-code-dev: RB, FR ## 2026-05-11 Attending: RD, JH, MM, BL, BT, SW - GitHub CodeRefinery organization roles, who should have what rights? - Separation of lesson repos from other stuff? -> 2 organizations? - We have already: - https://github.com/coderefinery - https://github.com/cr-workshop-exercises - Learners should not appear in the main CR repo, should be easy to reset - Member types: - Organization member - general rights? - teams rights? - **NeIC team** - **Collaborators** (active instructor, or chance they will teach, access to all lesson repos) - maintainers - Outside collaborator - Owner - Default permission for all org members: Read-only or also push rights? - Aalto: team for maintain access - Instructor experience: Nice to fix things directly, but also ok to make PR. More efficient to have access early on. - Agreement on self-push vs PR, intention was that someone else should look before merge - RD: my idea: make team `neic-staff` and `staff`, `staff` gets write access to all lessons/manuals/etc. `neic-staff` gets write to important user-facing stuff such as coderefinery.org. - "Projects base permissions"=write is the main setting to be updated. This means all members can write to every repo. Change to "read" and then we *have* to use teams. All else looks good. - Policy? -> Add instructors as collaborators when instructors are set - PR first, self merge when approriate - Document how to get added to the team, how to get acknowledgement - [Post workshop survey](https://github.com/coderefinery/2026-post-workshop-survey/blob/main/README.md) - Open tasks: - MM is interested, SW to check about sharing, done and shared - move data to lesson issues, SW - Blogpost, SW - Lesson editors/maintainers - https://coderefinery.github.io/manuals/lesson-editor/ - Monthly lesson specific meetings? Once per month, every second Monday of a month? - Could start with every lesson maintainer introducing their lesson, challenges - Sign-up for interest: * git-intro: DI, .. * git-collab: ..,.. * reproducible research: SW , .. * social coding: (RB), .. * AI coding: BT, .. * documentation: AM, MM, .. * testing: .., .. * modular-code-dev: RB, .. ## 2026-05-04 Attending: RD, DI, BT, HM, SW, HF, AM - GitHub permissions: - Create teams -> SW - Staff - Instructor team - Learner team - Write in manuals -> SW (proposal: new page /github-organizations, toctree under "About CodeRefinery", make sure linked from the onboarding page) - Peek into post workshop survey answers - Same analysis as for last survey: https://coderefinery.org/blog/2024/08/10/post-workshop-survey/ - Collect topics for potential seminars - Add lesson related things as issues - Videos: what to do in future? raw vs processed - AM: Working on a more automated process for Mimer, LLM to go last mile, will update when ready - Tell instructors to say some codeword? - Easy to forget - Weird - Instructors may want some parts to be removed before published - Surprise about time saved, people say few hours, but other answers suggest more - Difficult to quantify ## 2026-04-27 Attending: RD, BT, DI, HM, AM * next workshop in Septmber * Same coordinators as before, DI as registartion and EG as instructor * Instructor training times (RD): * Lesson editors? * https://coderefinery.github.io/manuals/lesson-editor/ * These are people who would be overseeing contributions and instructor onboarding for the lessons * Proposed editors: * git-intro: DI * git-collab: * reproducible research: * social coding: RB * AI coding: BT * documentation: AM * testing: * modular-code-dev: RB * How to enforce the role of the editor? * Use Github teams (see below)? * Use [.github/CODEOWNERS file](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)? * Github teams for repo permissions? * Different teams under the organization * Staff team (almost full access to everything, official collaborators, admin/maintainer access on repos) * Instructor team (write access to the lesson repos, workshop repos, other frequently updated places?) - anyone who is teaching with us or other close help for workshops. * participant teams (for git-collab, in organization cr-exercises). * we ask SW * Date for Python for SciComp * We should try to decide this soon but can't do it now. ## 2026-04-20 Working groups Attending: SW(host), DI, SR, BL, EG, BT, RD, HM ... Project plan, FYI: https://github.com/coderefinery/reports-and-proposals/blob/main/phase-4-project-plan/CodeRefinery-phase-4-project-plan.pdf - Existing working groups: How did you organize the group? What would you do differently next time? - Open topics from active working groups; what do you need to proceed? - Social coding - SR - plan: talk with an expert as supplementary material, focus on AI - wants to continue - :tools: Data steward - SW - in progress with Tampere data steward course - EG: maybe this will turn into an open source book? "Data Science for Data Stewards" - AI lesson - EG - AI lesson exists now :) - Being updated tomorrow since I have a workshop on Wednesday... - more compressed - Things are changing rapidly - Lesson dev will continue after summer - good for raising awareness - :arrow_right: Advanced git - SW - moved to Carpentries community (?) - would be good to to have something under CR too - we could revisit - TTT/ instructor prep - RD - Went well, awaiting next cohort for small modifications. - No separate TTT at this moment, but small sessions before workshop - Continue small updates - Most important: set dates for the onboarding and practices early - Lesson template is used much - Workshops on how to use? - SR would have a place to show it again - How to give credit to CR - Lesson for other project people about "things we have available" , invite to workshop, share about lesson template - TTT could provide certificate, including teaching - people could use it for their portfolio - Could be formalized? and get an official certificate that lecturers/academics can use in their careers - Also helpers could get certificate (they can ask for it), separate from instructor - RD can always be invited to give a talk about our setup and things available - :tools: More R to lessons - SW - issues created, some done, others open - done - AI info boxes - EG - EG: I don't remember what this is about :sweat_smile: - :tools: Citable lessons - SW - DOI per lesson done (manually) - automation - metadata - mention more prominently - MOOC - AHM - stuff already there on test platform - continuing - Install instructions - RD - interactive chooser for finding what to do as participant was presented as prototype - do we still think the chooser is a good idea? - Could still pilot it for next workshop? - Keep thinking about it - - Ideas for new working groups? Cannot do all, so just a collection for now. ~~ - Behind the scenes tour (from last round, did not have a lead)~~ - CodeRefinery info package (presentation/poster/video/social media posts/places to present..?) - https://zenodo.org/communities/coderefinery/records?q=&l=list&p=1&s=10&sort=newest - https://github.com/coderefinery/presentations - Short posts for social media of stuff we have available (text + image) - Lesson contribution guide + lesson maintainership process - https://coderefinery.github.io/manuals/lesson-contribution/ - Event page template update - https://github.com/coderefinery/template-workshop-webpage/ - CodeRefinery workshop definitions & what can be hosted: - https://hackmd.io/@coderefinery/CR_def - CodeRefinery JOSE paper - https://jose.theoj.org/ - Citable reference for the project and workshop - EViTA submission of CR lesson(s): interest: BL - TTT (see above) - LEsson template and sharing about it - .. - Active working groups with lead: - Social coding - SR - Data steward - SW - AI lesson - EG - Mooc - AVM - Install instructions - RD (unless someone else wants) - Evita - BL - Behind the scenes tour - BT - JOSE - HM - What's next? - SW will reach out to working group leads about proceedings for the working groups ## 2026-04-13 Ambassador meetup Attending: SW (host), MT, JH, FR, SR, VH, BT, OT, RD, TP - Welcome - Intro round - Connection to CodeRefinery - What would you like to get out of this meeting? - Catching up :) - Reconnecting - Learning - News from the project - Spring workshop - any questions/feedback? - Working group updates - see https://hackmd.io/W4VDMDiWQ4eiyZ9Xk9hVzw?view#CodeRefinery-working-groups-updates - any questions/interests? (add your initials to the Working group you are interested in) - Questions to you: - We heard that some organizations cannot share info about workshops that do not include their organizations logo, is this an issue for you? - What channels? mailing lists, info screens, - Should not be an issue for uni, non-profit, free - Libraries seems to be a good way to go (mailing list) - Piggybacking on existing projects, not send own -> offer as something good and free - Offer to give something (name on website, logo?) - Bulletin board vs official e-mail : different expectations/news - internal channels to share about special issues/conferences, chat? - infiltrating chats etc :) - careful with too many e-mails to same people from different channels - "talk about it", make easy to show, share internally, offer them something - share also what we do beyond the workshop - suspicious about free stuff, make them pay? - classroom as paid option with extra - make clear that people understand it is publicly funded - website, event page - > Actionpoint for SW: Make possible to add logo/name for supporters - > Actionpoint for all: Share wherever you can, check inofficial channels, chats, boards etc - > Actionpoint for SW: Working group for info package - Any topics that it is hard to find materials/courses about, that would fit the CodeRefinery project? - (from chat) Security for research software - (from chat) LaTex - performance problems: profilers (some good resources from LUMI, missing semester in CS), wrong data layout - intro course on HPC: general -> Aalto HPC kickstart: https://scicomp.aalto.fi/training/scip/kickstart-2026/ - intro to software design, philosophies etc - > Actionpoint SW: Check feasibility, linking of materials/events we know of - AOB - Maintainathon happened in January for the CAA [Special Interest Group for Scientific Scripting Languages in Archaeology](https://sslarch.github.io/), next year they would like to extend the event to more associations and groups (contact Matteo if you are part of some group that would like to join this effort) - Also created a page of resrouces for the event which is super useful https://sslarch.github.io/maintainathon/resources.html --- Older meeting notes: https://github.com/coderefinery/meeting-minutes/blob/main/archive.md