---
title: nf-core/core team meeting notes
tags: meetings,notes,core
---

# nf-core/core team meeting notes

<!--

## TEMPLATE [DO NOT USE FOR TAKING MINUTES - USE NEXT MEETING BELOW]

### Attended

- [ ] Chris
- [ ] Edmund
- [ ] Fran
- [ ] James
- [ ] Jose
- [ ] Júlia
- [ ] Ken
- [ ] Marcel
- [ ] Matthias + Flora
- [ ] Maxime
- [ ] Nicolas
- [ ] Phil
- [ ] Rike
- [ ] Sateesh

### Agenda and Minutes

ADD YOUR NAME TO AGENDA POINTS

- [ ] **REGULAR: review last meetings's action items**
- [ ] **REGULAR**: team update summaries
- [ ] **steering**
- [ ] [**infrastructure**](https://github.com/orgs/nf-core/projects/73)
- [ ] **outreach**
- [ ] **maintainers**
- [ ] **docs**
- [ ] **OSSF**
- [] **REGULAR** Review RFCs and Pipeline Proposals
- [ ] <REPLACE ME WITH TRADITIONAL POINTS>

### Action Points

- [ ]

-->

## 2025-11-18

### Attended

- [ ] Chris
- [x] Edmund
- [x] Fran
- [x] James
- [x] Jose
- [x] Júlia
- [ ] Ken
- [ ] Marcel
- [x] Matthias
- [x] Maxime
- [x] Nicolas
- [ ] Phil
- [x] Rike
- [ ] Sateesh

### Agenda and Minutes

- [x] **REGULAR: review last meetings's action items**
- [x] @mribeirodantas Find a time for a dedicated "the future of hackathons" meeting
- [x] **REGULAR**: team update summaries
- [x] **steering**
- No members present, no update
- [x] [**infrastructure**](https://github.com/orgs/nf-core/projects/73)
- Releasing 3.5 RIGHT NOW (jk), hopefully today
- Cloudflare is the weak link
- We have write-access to nf-test repo 🎉🎉🎉 (Edmund, Nicolas, Sateesh, Maxime)
- We will get rolling again soon
- prek to replace pre-commit (rust version of pre-commit (everywhere but modules for now))
- Nextflow lint is coming soon
- Nextflow format we're waiting on Harshil align fix
- topics
- working with dev on modules
- waiting for a tools release for the pipelines
- spring we will have 25.10
- nf-core-utils could be used
- [x] **outreach**
- Bytesize booked (close to) every week until Feb!
- Waiting for a review from Edmund on abstract/title on his upcoming bytesize
- Maxime volunteered to take Fran's responsibilities for bytesize in the future
- Hackathon debrief would be nice, but not planned
- Matthias thought it went AMAZINGLY WELL
- James thought more business-like/less socialable, but more productive (projects plus more expertise everywhere)
- [x] **maintainers**
- No updates, Maxime starting new job and Rike in the metro
- Rike: New people pixelgen joined so we’ll start discussing with them about release
- Weekly helpdesk
- merge AMER and EMEA
- -> AMEREA?
- RIKE is in charge of the reboot
- [x] **docs**
- [ ] Chris made`v2` branch, [draft style guide](https://docs-v2--nf-core-docs.netlify.app/docs/contributors/documentation) -> James to start testing, discussed copilot LLM help
- Maybe a presentation around hackathon time (26-03)
- [x] **OSSF**
- No Phil, so no news
- [x] ➡️ **James** Does anyone have time to review Chris Wyatt's BBSRC grant?
- No volunteer, too short time-wise for anyone
- [x] ➡️ **Júlia** `#ask-core` - what should the channel scope be?
- Rename `#request-upload`
- AWS
- quay.io
- Zenodo
- Transfer repo
- We should have a form
- and description saying what is allowed
- emojis/reaction to direct people to this channel
- Add to welcome pack
- Announcement
- [x] ➡️ **Jose/Júlia/Rike** Cedric wants to write a new paper:
- Title: "10 good rules for how to write best practice nextflow pipelines"
- Do we want to participate?
- Jose is in
- Maxime is interested too
- Júlia
- Marcel?
- [x] ➡️ **Júlia/James** Create new repository for accepted pipelines or leave it for dev (conflicting docs)?
- Set it up on nf-core via bot and put it outsite of website until mature enough?
- Update docs (TODO Júlia)
- [x] ➡️ **All** Retreat tasks updates -> who has done what?:
- https://github.com/orgs/nf-core/projects/141/
- [x] Education SIG (FBo)
- Eduction SIG might die because of lack of initiatives
- Initial message from Francesco was heavy
- We should reply FINALLY in a diplomatic way
- Maybe send Phil to support Marcel
- [ ] ➡️ **REGULAR** Review RFCs and Pipeline Proposals (**James**: Is this working to do this in this meeting?)
- [ ] Reviews before meeting, and only discuss the problematic ones.

### Action Points

- [ ] When GG healthy/@mribeirodantas not busy - Find a time for a dedicated "the future of hackathons" meeting
- [ ] Look and update https://github.com/orgs/nf-core/projects/141/ (ALL)
- [ ] Reply to Francesco in Education (PHIL, or JAMES, or last case MAXIME)

## 2025-10-25

### Attended

- [x] Chris
- [x] Edmund
- [x] Fran
- [x] James
- [x] Jose
- [x] Júlia
- [ ] Ken
- [x] Marcel
- [ ] Matthias + Flora
- [x] Maxime
- [x] Nicolas
- [ ] Phil
- [x] Rike
- [x] Sateesh

### Agenda and Minutes

ADD YOUR NAME TO AGENDA POINTS

- [x] **REGULAR:** review last meetings's action items
- [x] **REGULAR**: team update summaries
- [x] **steering**
- [x] [**infrastructure**](https://github.com/orgs/nf-core/projects/73)
- Release was smooth this time!
- Next priority is topics (kicking off during hackathon) with small release
- [x] **outreach**
- @maxulysse volunteered to host the bytesize once Fran is gone
- practical hackathon stuff was discussed in the last meeting
- we have 12-ish projects on the website now
- about 100 participants have signed up
- [x] **maintainers**:
- no updates, just new members
- [x] **docs**
- IA planning and first steps
- Edmund has opened [PRs](https://github.com/nf-core/website/pulls?q=is%3Apr+is%3Aopen+vale) for Vale integration
- [x] **OSSF**
- [x] **REGULAR** Review RFCs and Pipeline Proposals
- [x] Discussion on the future of the types of hackathons we host
- bad experience of online users may outweigh the gains of on-site users
- how would we combat that?
- we need to have this conversation again in a dedicated meeting

### Action Points
- find a time for a dedicated "the future of hackathons" meeting @mribeirodantas

## Pre-retreat

- [ ] Set up stalebot (maybe for all templates)
- [ ] (Retreat) Discuss whether or not to add freelancers & job offers to the website / create a slack channel

## 2025-09-12

### Attended

- [x] Chris
- [x] Edmund
- [ ] Fran
- [x] James
- [x] Jose
- [ ] Júlia
- [x] Ken
- [x] Marcel
- [ ] Matthias + Flora
- [x] Maxime
- [x] Nicolas
- [x] Phil
- [x] Rike
- [x] Sateesh

### Agenda

ADD YOUR NAME TO AGENDA POINTS!!!!

- [x] **REGULAR: review last meetings's action items**
- [ ] **REGULAR**: team update summaries
- [x] **steering**
- [x] [**infrastructure**](https://github.com/orgs/nf-core/projects/73)
- Seqera containers migration
- 3.4 release coming soon
- [x] **outreach**
- Focus on hackathon projects recently
- Maxime + Fran not attending hackathon in person
- [x] **maintainers**
- [x] [name=Maxime] Migration to topics ([RFC issue approved](https://github.com/nf-core/proposals/issues/46), [RFC PR in](https://github.com/nf-core/proposals/pull/76)). Next steps: nf-core/tools, discuss further after that.
- [x] [name=Maxime] Migration to Seqera containers
- [x] [name=Maxime] workadventu.re to replace gather.town
- Been using it for help desk etc. for a few weeks, working well so far.
- Cheaper than Gather Town, based in the EU
- Consider for next remote hackathon
- [x] [name=Maxime] ⚠️ Chris Cheshire blocking cutandrun dev
- Slow to reply, template merges blocking other development
- Maxime has emailed forcefully about getting stuff in
- Wait 1 week for a reply, then will push ahead with template merge
- [x] **OSSF**
- Will get updated from Lina during nf-core retreat
- [x] **REGULAR** Review RFCs and Pipeline Proposals
- [x] [name=James] Problem with conflicting proposals! Procedure for resolving?
- Pipeline proposals coming in where we don't have expertise
- 2 cases of infighting: nanoraredx (2 done) paxomatic (1 done)
- In some cases devs have made decisions that the other group disagrees with
- [name=Ken] We should choose what is best for our users. Short term _and_ long term.
- [name=Phil] If disagreements, try to get a third party for external input?
- [name=Phil] If a pipeline is already done, make sure that devs know that others can contribute
- [name=Edmund] Key is mentality around ownership
- [name=Ken] Organise a meeting between devs? Include 1 or 2 core team members?
- Preference for thinner pipelines in general, with shared components
- Let's decide these two problems in core team slack, whole core team ASAP
- Guidelines - defer to retreat
- [ ] https://github.com/nf-core/proposals/issues/64
- [ ] https://github.com/nf-core/proposals/issues/63
- [ ] [name=James] ⚠️ More ideas for Chris Wyatt's SSI grant?
- i.e. if you got funding for 2 years for 2 or so people in the UK to work on nf-core, what would we want them to do?
- Application document: https://docs.google.com/document/d/1es-g-5IOmjvSaLAkNHzXMRPjuT395WYx2MTSV6x4nlA/edit?usp=sharing
- [ ] [name=James] general point: we need to describe what our current vision/direction/2 year plan/focuses , as this will help people tryi

- [x] [name=Maxime] Booking Aifur on Tuesday for retreat
- Maxime will send an email with instructions for choosing a meal
- [x] [name=Phil Ewels] Email from Johan Dahlberg about pressure coming from slow release reviews.
- [name=Edmund] Stringency on PRs into dev, not the release. Can we lower the requirements on review for releases?
- [name=Sateesh] Need more unit tests
- [name=Rike] Separate guidelines for first review (no reviews on dev prior to v1)
- [name=Rike] Need to ensure that reviews are proper and not only internal
- Phil can invite him for a quick fika / breakout if he wants
- [x] [name=Phil Ewels] Hackathon / Summit
- Hackathon project leads who are remote? No. Can join others though.

### Action Points

- [ ] @L3ZVKW4rSL6UdvjP7M_39A to write blog post about RFCs (with Phil)
- [ ] All of core team to come to conlusion about 2x current pipeline arguments
- [ ] All of core team to read SSI grant text if possible

## 2025-08-08

### Attended

- [ ] Chris
- [x] Edmund
- [x] Fran
- [ ] James
- [x] Jose
- [ ] Júlia
- [x] Ken
- [x] Marcel
- [ ] Matthias + Flora
- [ ] Maxime
- [x] Nicolas
- [ ] Phil
- [x] Rike
- [x] Sateesh

### Agenda

- [ ] **REGULAR: review last meetings's action items**
- [x] **outreach**
- hackathon is coming up, but there is not much done in terms of organisation
- probably should discuss this next week in the outreach meeting
- Outreach meeting next week to discuss hackathon agenda
- @FranBonath If you can join and help organise, please join
- [ ] **maintainers**
- [x] Maintainers leads: tell maintainers team to experiment with dev in `nf-core test-datasets` command in `dev`
- next time
- [x] Infrastructure leads: already start warning pipeline devs about upcoming pipeline-level nf-test tests in template
- next time
- [ ] Everyone: check hackathon kit document (see outreach meeting notes from last time)
- Need volunteer to fix links. @mribeirodantas to review
- Link: https://docs.google.com/document/d/1Hb92_HOUxJZ3yS9RDRliBx_gFWSRcQxyqKPdsCChYwU/edit?tab=t.0#heading=h.bf4umx5r7p7e
- [x] ???: Someone to RFC templates for proposals
- Suggestions for improvements from @L3ZVKW4rSL6UdvjP7M_39A
- Need more regular votes from core team members
- Proposal to add to core team agenda and vote once a month
- Added in a new flag: "needs-work" for any RFC that is not declined but needs details or some technical demonstration before approval
- https://github.com/nf-core/proposals/pull/45
- [ ] Set up stalebot (maybe for all templates)
- RFC? next time @jmir
- [ ] Docs + blog post for new RFC system
- :checkmark: Docs
- Someone to write a blog post @L3ZVKW4rSL6UdvjP7M_39A
- [ ] RFCs: issues or PRs?
- Issue by habit
- [x] Add to guidelines: teams will be reviewed every 18 months at nf-core core team retreat
- @FriederikeHanssen add to the retreat agenda

### Action Points

- [ ] @L3ZVKW4rSL6UdvjP7M_39A to write blog post about RFCs (with Phil)
- [x] @FriederikeHanssen to add agenda items to retreat agenda: review of members, open RFCs that were discussed
- Rike is doing it now
- [x] @ewels to review the bot improvements for the proposal repo: https://github.com/nf-core/proposals/pull/45
- Merged
- [x] @mribeirodantas to review https://docs.google.com/document/d/1Hb92_HOUxJZ3yS9RDRliBx_gFWSRcQxyqKPdsCChYwU/edit?tab=t.0#heading=h.bf4umx5r7p7e
- Reviewed, Fran created another new document with updates.

## 2025-05-09

### Attended

- [x] Chris
- [x] Edmund
- [x] Fran
- [x] James
- [x] Jose
- [x] Júlia
- [x] Ken
- [ ] Marcel
- [x] Matthias + Flora
- [x] Maxime
- [x] Nicolas
- [x] Phil
- [x] Rike
- [ ] Sateesh

### Agenda

- [x] **REGULAR: review last meetings's action items**
- [x] NONE (previous meeting replaced with special outreach)
- [ ] **REGULAR**: team update summaries
- [x] **steering**
- Nothing much, a couple of grant things (one in UK via RSI)
- [x] [**intrastructure**](https://github.com/orgs/nf-core/projects/73)
- Small patch release
- New test-datasets command (maintainers should experiment)
- Next template release big change via nf-test
- [x] **outreach**
- Planning boston hackathon, registration down because 'mysterious political things' (28 people) + Chris Wyatt & Fernando Duarte from UK
- Hackathon kit in preparation -> everyone should check document to fill out
- [x] **maintainers**
- `CODEOWNERS` in pipelines
- We should make sure allow some cutomisation, so can be stricter or less strict (notificaitons vs mandatory review)
- Blog about setting up a stalebot [here](https://github.blog/open-source/maintainers/announcing-the-stale-repos-action/) - ping `#infrastructure` for help?
- Upcoming: test-data working group (theme of next meeting)
- [x] **OSSF**
- No updates
- [x] @Kenbrewer Better decision making and communication improvements, [ideas](https://nfcore.slack.com/archives/C072TAN9RDE/p1745487583998579):
- [ ] A dedicated ~~(core?)~~ decisions voting only slack channel - _as first triage for RFC?_
- [x] Use nf-core/proposals for decisions
- [ ] Defined time-range/deadlines for different types of discussions/decisions (if we can define these
- [ ] Explicit method for running decision polls
- [ ] Generally more documented what our decision making and communication processes are
- [ ] Explicit quorum requirements for different decision types (if we can define these)
- [ ] Implementing RFC ~~/ADR~~ (-like) systems for decision making, adopting the [Astro type system](https://github.com/withastro/roadmap)
- [x] ✅ Set up standing 6monthly roadmap extended core meeting
- [x] @jfy133 : Should we explicitly say in our core/steering/etc [guidelines](https://nf-co.re/governance#core-team) **when** each team gets reviewed (yearly)
- Reason: to show that there is a explict 'concept' for ensuring turnover and don't get stuck with 'old people', but without giving explicit mandate 'terms'
- [x] @jfy133: when should we address survey results?
- nf-core retreat
- [ ] ~~@jfy133 I want a golden duck!~~
- [ ] Event structure: Barcelona and beyond
- Barcelona: online-only summit talks, followed by nf-core hackathon (with poster session) and training
- Talks pre-recorded, live Q&A
- Timings
- Talks: Thurs + Fri (online), half days
- Hackathon training: Monday - Weds (BCN)
- Pros
- Feels like a single event
- Cons
- 7 days instead of 5
- Stop / start - lose momentum from talks?
- Bigger gap between talks + hackathon? (mon+tues, then mon-weds?). Gives time for recovery? (weds-thurs?)

### Action Points

- [ ] Maintainers leads: tell maintainers team to experiment with dev in `nf-core test-datasets` command in `dev`
- [ ] Infrastructure leads: already start warning pipeline devs about upcoming pipeline-level nf-test tests in template
- [ ] Everyone: check hackathon kit document (see outreach meeting notes from last time)
- [ ] ???: Someone to RFC templates for proposals
- [ ] Set up stalebot (maybe for all templates)
- [ ] Docs + blog post for new RFC system
- [ ] RFCs: issues or PRs?
- [ ] Add to guidelines: teams will be reviewed every 18 months at nf-core core team retreat

## 2025-04-11

REPLACED WITH SPECIAL HACKATHON DEBRIEF

## 2025-03-14

### Attended

- [ ] Chris
- [ ] Edmund
- [x] Fran
- [x] James
- [x] Jose
- [x] Júlia
- [x] Ken
- [ ] Marcel
- [ ] Matthias + Flora
- [x] Maxime
- [x] Nicolas
- [x] Phil
- [x] Rike
- [x] Sateesh

### Agenda

1. **REGULAR: review last meetings's action items**
- [x] Maxime to ask Arthur about becoming maintainer
- "Contact me later once settled in a new job"
- [ ] @jfy133 / @mashehu to bulk out existing issue on website repo
- [x] @jfy133 to announce survey on monday
- [ ] Everyone: [list of locations](https://hackmd.io/@nf-core/rkjcbtOYJe) for advertising
- [x] @jfy133 ask maintainers if they want a special Tshirt
- TODO: Rike & Phil to buy more swag
- [x] @nicolas to nudge evexplorer dev
- [x] Everyone: shout out ASAP if retreat dates are bad (22nd September????)
1. OSSF update
2. @maxulysse: **We should have frequent reports about what is happening in meetings/team that are in direct relation with core - some teams seem to work amongst themselves, unclear to other members of core (steering, infrastructure, outreach, maintainers)**
- **REGULAR**: team update summaries
- **steering**
- **intrastructure**
- https://github.com/orgs/nf-core/projects/73
- **outreach**
- **maintainers**
- **OSSF**
3. @maxulysse: **We should have frequent reports about what is happening in core towards our community.**
- We do reports after IRL meetings and changes in member, and I feel it's the most important stuff that happens, but
- Proposal:
- New section for meeting minutes
- Infrastructue roadmap - quarterly blog post
- Versioned nf-core specs for modules etc.
- Can have release notes for new specs (ADRs)
4. @jfy133 **Dedicated slack channel for tracking/trading release reviews?**
- More familiar to users/integrates better into their own workflow
- People added when creating a new pipeline
- Added to the release checklist
- Normal #request-review is too noisy, gets lost
- Pins / canvas on a different tab, people won't look
- **DECISION**: make #request-review-pipeline (James)
5. @jfy133: **we need better assignment of monitoring of things that involve tracking/discussions (particular person, with a backup or assigned to a particular team's leads?)**
- New pipeline proposals (James + Jose)
- New special interest group (Fran + Jose)
- Release review trading (see how it goes)
5. Maxime - github repo for new pipeline proposals
- Board happens for free, more traceable
- Can auto-close / prompt discussions that have gone cold
- Use an issue template
- Start with pipelines and see how it goes
- New repo: `nf-core/proposals`
6. @nvnieuwk **Updating the AWS test upload checklist + add more guidelines what/when things go there?**
- Don't use the iGenomes bucket now, we have plenty of credits
- Improve CLI command instructions for how to do the upload, next time that someone has to do this.
- Files that are uploaded: only when source place is regularly unreliable (e.g. for full-tests, pipeline devs should use reliable public sources sich as ENA/SRA as far as possible)
- TODO: Nicolas to update philosophical life guidance
8. ~~@jfy133 **Add entire community to weekly-helpdesk (With message people can leave), so we reduce spam on announcements (and add as default channel everyone added to)?**~~
- @ channel if ahead of time
- @ here when it starts
10. @jfy133: **initial results from survey**
- Defer to after meeting
12. @FriederikeHanssen: Permission on Seqera Platform. AWS Account
- Downgrade everyone down to view
- Upgrade some pipeline maintainers to launch
- Core team + extras to owners
- Nuke all CEs and see if anyone complains
- Add roles to the core team checklists
15. Spring cleaning - AWS results (Julia)
- First ask the pipeline maintainers
- Then #aws-megatests
- Then core team
- Then Seqera
- If in doubt: Rike is point-person.
17. @maxulysse: modules on modules
- Environment modules (HPC)
- KISS

### Action Items

- [ ] make #request-review-pipeline (James)
- [ ] new repo: nf-core/proposals (James/Maxime)
- [ ] Update AWS test upload checklist (Nicolas)
- [ ] Clean Seqera Platform/AWS account (Rike)
- [ ] Add a checklist too
- [ ] James report on survey
- [ ] Clean notes and put on the nf-core website (Phil)

## 2025-02-14

### Attended

- [x] Chris
- [x] Edmund
- [x] Fran
- [X] James
- [x] Jose
- [x] Júlia
- [x] Ken
- [x] Marcel
- [x] Matthias + Flora
- [x] Maxime
- [x] Nicolas
- [x] Phil
- [ ] Rike
- [x] Sateesh

### Agenda / Minutes

1. Last meeting's action points
- [x] Phil to announce core team change and update website
- [x] James to prepare with Marcel the basic survey (**Update:** Almost ready!)
- [x] Reach out to US Sites (Yale, Lorena for Boston with Geraldine)
- [x] Fran to post on socials with rike's bytesize
2. Q: @maxulysse references
- GRCh38 for #rnaseq needed
- Will "soft-launch" the new #references by providing just these in near future
- @maxulysse to share presentation / write a document or something
- Future: needs discussion with infra, schema, seqera...
3. Q: Reviews of first-releases
- Regulars in order of regularity: James, Sateesh, Julia, Matthias, Nicolas, Edmund
- Suggestion:
- add [reviews board](https://github.com/orgs/nf-core/projects/39/views/1) to the first release checklist
- get up to date with current first releases
- can we automate pings so that James doesn't have to hassle everyone
- Provide link to guidelines etc.
- How can we upskill more people to be in this group?
- Docs: do we have instructions for new pipeline review?
- Can we sequence reviews: maintainers first, then once a first approval core team
- Add to the instructions if we agree
- Leverage helpdesks to do paired reviews, booking time off
- If folks turn up for questions then they get priority
- If not then time is well spent on nf-core reviews
- Also good for upskilling / pair reviews
4. Q: @jfy133 how to help Arthur Gaymer set up APAC helpdesk? (did someone ask him to be a maintainer again?)
- Chris + Arthur will start APAC helpdesk (3PM NZ)
- Blog post, advertise with BioCommons + APAC hackathon
- Create an #apac channel (`#amz`), `#gdaynfcore`
- **ACTION**: Maxime to ask Arthur about becoming maintainer
5. Q: We really should set up a website page/calendar for regular events...
- Helpdesks etc. aren't on event page, don't get the header on the homepage
- Dev meetings (sarek etc.) also
- Automation of social posts for these events :point_up:
- **ACTION**: @jfy133 / @mashehu to bulk out existing issue on website repo
6. Q: @jfy133: Can we get one last check/test of the community survey and announcment draft?
- Survey: https://seqera.typeform.com/2025-nf-core
- DONE
- Announcement https://hackmd.io/f2blo9nXTo-JCivRUwWr-w
- TAKE ASYNC
7. Q: @jfy133: Can we brainstorm a [list of locations](https://hackmd.io/@nf-core/rkjcbtOYJe) (mailing lists, slacks etc.), where we can actively advertise events (in addition to our own social media)
- e.g. Bioinf societies, bioinf. slacks, larger communities
- Could be task of outreach team/person to do the mailshots?
- TODO: EVERYONE GO EDIT THIS TO ADD MORE
8. Q: @jfy133 shall we open ordering of exclusive core-team Tshirts in preparation for the hackathon?
- https://nfcore.slack.com/archives/C072TAN9RDE/p1736626496690929
- Or does anyone know if we can do a hidden order?
- Log in as admin and order yourself
- TODO: ASK MAINTAINERS IF THEY WANT THIS
- TODO: LOOK INTO BULK ORDER FOR CORE RETREAT
9. What to do with solo developers not familiar with nf-core?
- evexplorer running alone without following nf-core best practise
- how do deal with it?
- **ACTION**: Nicolas to nudge to go to helpdesk to run through everything
11. CORE TEAM RETREAT
- Minimum Mon-Weds, Thurs to work if people can make it
- Steering group joins for some of to?
- TODO: Shout asap if dates are bad

### Action Items

- [ ] Maxime to ask Arthur about becoming maintainer
- [ ] @jfy133 / @mashehu to bulk out existing issue on website repo
- [ ] @jfy133 to announce survey on monday
- [ ] Everyone: [list of locations](https://hackmd.io/@nf-core/rkjcbtOYJe) for advertising
- [x] @jfy133 ask maintainers if they want a special Tshirt
- [ ] @nicolas to nudge evexplorer dev
- [ ] Everyone: shout out ASAP if retreat dates are bad

## 2025-01-10

### Attended

- [x] Chris
- [ ] ~~Harshil~~
- [x] Edmund
- [x] Phil
- [x] Fran
- [x] Rike
- [x] James
- [x] Jose
- [ ] Matthias
- [x] Maxime
- [x] Júlia
- [x] Marcel
- [ ] Geraldine
- [x] Nicolas
- [x] Sateesh

### Agenda

1. Last time's action points:
- [x] Finish + merge authorship contribution docs [#2839](https://github.com/nf-core/website/pull/2839)
2. Core team update steps - who gonna lead?
3. State of [nf-core survey preparation](https://hackmd.io/PzwJH_PzSyefPn80s3zNeg?both)
4. Hackathon prep status?
5. Community event assets

### Minutes

1. Last time action points: Done!
2. Core team update:
- Remove Harshil + Geraldine
- Add Ken
- Phil will do announcement
- [docs](https://nf-co.re/docs/checklists/community_governance/core_team#new-core-team-member-onboarding)
3. State of nf-core survey
- Simple survery, test temperature of community
- James to set up the simple one in TypeForm, collab with Marcel?
4. Developer survey
- Based on Edmund's work from 2024.
- Send out separately at a later date.
- Get maintainers to fill this one in (at least)
6. Hackathon prep status?
- Physical site assets? A4 poster, stickers
- Website pages for local sites
- Put up hackathon event pages for each site ASAP
- Post on socials linking to Rike's bytesize (thanks Fran)
- TRAINING - need to have a plan + dates for videos
7. Community event assets
- Would be nice to have a resource pack for folks organising their own separate events.
8. Mentorship programme
- Amazon gift vouchers were ok-ish
- Recommendation: force Amazon if possible.
- TODO: Ask Ken if he can run mentorships
- Timeline: after March hackathon at earliest
10. Bytesize talks
- Nicolas to do JSON schema talk

### Action Points

- [x] Phil to announce core team change and update website
- [ ] James to prepare with Marcel the basic survey
- [x] Reach out to US Sites (Yale, Lorena for Boston with Geraldine)
- [ ] Fran to post on socials with rike's bytesize