---
# System prepended metadata

title: nf-core/core team meeting notes 2022-2024
tags: [meetings, notes, core]

---

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

# nf-core/core team meeting notes 2022-2024

## 2024-12-13

### Attended

@maxulysse , @FranBonath , @sateeshperi , @jmir , @nvnieuwk , @jfy133, @JoseEspinosa , @emiller , @ChrisHakk , @mribeirodantas , @ewels , @mashehu 

### Agenda

- [x] Quick recap: 10x genomics software
- [x] Setting a tentative date for next core retreat
    - Sweden?
    - Time it around the Seqera company retreat as folks will be in Europe? (June 9-13)
    - :x: March 11-20
    - :x: March 24-6 is nf-core hackathon
    - :x: May 12-16 is Boston summit
    - :x: June 2-6th is bad as Elixir hands-on
    - ✅ 22-26 September tentative!!!!!
- [x] [James/Marcel/Chris] Discussion on making guidelines for authorship on nf-core publications
    - Proposed changes are good, but language should not be too strong as this is not something that we can or want to enforce or regulate directly. Ultimate responsibility lies with the individuals involved.
    - Could add a sentence to the code of conduct about this (Should be short)
    - Add to admonition reminder about this in the first-release checklist
- [x] [Maxime] Better address increasingly competeing/overlapping pipelines after acceptance
    - Scope creep after proposal acceptance
    - Also we need to allow for smaller pipelines and meta pipelines with easy chaining for end users
    - Coming in 2025
        - Effort to work on Nextflow syntax to unclock pipeline chaining
        - New QBiC student will hopefully work on metapipelines
    - TODO: Discussion point at the next nf-core retreat
- [x] [@mashehu/@jfy133] Bring balance back to ~~the Force~~ core
    - Harshil to visit ~~Valhalla~~ the steering committee
    - Ken / GG swap? Community team to discuss.
    - Add core team members from APAC?
- [x] Workload handling new pipelines / first-release pipelines
    - Could have a dedicated small team for this?
    - Backburner project: to plan people and working plan
    - Think about training people up for this (avoid burnout)
    - Sub-team within maintainers?
    - Come back to this in the future to plan more
- [x] [Maxime] more control over modules CI and actions
    - More docs
    - [Codeowner requirement on `.github`](https://hackmd.io/_uploads/ryYUuhF41e.png)
- [x] [Fran] updates from Outreach
    - Had meeting about hackathon (notes [here](https://hackmd.io/U3CXba0dTKqw2A_P8goU5w))
    - Updates from Ken about sign-up form for sites?
        - Need to review whether feedback was handled
        - Need to get this out ASAP
        - Ken was away, now back and will continue
    - Aim to get out start of next week (Dec 17th ish?)
- [x] Maintainers - spring cleaning in Q1 2025
    - Clear out spring cleaning

### Action points

- [ ] Finish + merge authorship contribution docs [#2839](https://github.com/nf-core/website/pull/2839)

## 2024-10-11

### Attended

@ewels, @vdauwera, @ChrisHakk , @speri , @oRVLyAzyS6SABKri_BFj5w , @maxulysse, @jmir, @mashehu, @FranBonath, @jfy133, @emiller, @JoseEspinosa 

### Agenda

- None in advance...

### Notes

- Q: from marketing team
    - Could we replace gather.town with a cheaper alternative?
    - Gather is very expensive when >10
    - Options:
        - https://zep.us/
        - https://www.kumospace.com/
        - https://sowork.com/ (from new Seqera marketing)
- Training material update from Geraldine
    - [Core Nextflow material](https://training.nextflow.io/#applied-training) is mature now, can start moving onto modules etc.
        - Trying to have a module concept
        - Be able to switch between different domains (e.g. same topic but different use case)
    - Will teach this new material in the summit
    - Have a chat in near future to see how to harmonise with nf-core
- Hackathon updates
    - 60 people training lead by Geraldine and Ken, but looking for expert volunteers :eyes: 
        - Also so Ken can join the hackathon for a bit
        - Marcel will also help with training
    - Hackathon: 116 tickets sold :scream: 
        - We will all be very busy
            - Make sure to walk around and that no-one is getting lost
        - Current projects submitted for hackathon: 12 on the website
        - Socials:
            - Bingo - physical this time? We need PDFs to print!!! @mashehu is on it
            - shop now life-ish, not advertised 
                - blogpost? 
            - Sock hunt! Maxime to 'vandalise' places
            - Challenges on slack? 
        - Do we need another meeting just for hackathon stuff?
        - If you are in BCN in Sunday, help would be welcome for setting up with @ewels
    - Summit: 260 people
- Nextflow updates
    - 2 more Nextflow developers (Tom and Jorge)
    - Nextflow team: Paolo, Phil (Product Lead), Chris (docs), Ben, Tom, Jorge
- Steering committee updates
    - New 'Open Science Software Foundation' ready to be announced! https://openscience.software/
- Seqera marketing team is going to be more 'forward looking' with finances
    - Planning in advance, rather than on the fly
    - So try to send to Geraldine in advance what we want to spend money on in the future
    - e.g. Hackathons getting bigger each time (30% more each time)
    - Maybe focus on getting non EMEA timezones? -> would require budget requirements
        - For Pacific, via Australian Biocommons
        - Maxime wants to go to Japan (Geraldine has some contacts in Japan)
        - James wants to go to Australia
        - Sateesh will be runnign some training events in India soon
    - 

### Action points

- @maxulysse and @jfy133 to test the different gather alternatives
- EVERYONE: join outreach meeting next week

## 2024-09-13

Joined: Phil, @jmir, @FranBonath, @JoseEspinosa, @ChrisHakk, @mribeirodantas, @maxulysse, @emiller , @jfy133 

### Notes

* Foundation update
    * hope to announce the plans during the Summit
* Summit / hackathon update
    * Hackathon: 103 out of 150 booked
    * Summit: 177 out of 200-250ish
        * https://summit.nextflow.io/2024/barcelona/travel/
    * Hackathon projects
        * Now put out a soft deadline for proposals
* Future training
    * Should we put something in the calendar for Q1 2025
    * Two separate training events back to back
        * Seqera - Nextflow
        * nf-core - nf-core
    * Previous notes
        * YouTube strategy
            - _Unlist old videos (per-language)_
            - _New Nextflow training to go on the Nextflow Channel_
    - TODO
        - Pick a date, find some people
* Shop
    *  Volunteers?
    *  TODO
        1.  Fix merge conflicts on [PR](https://github.com/nf-core/website/pull/2340)
        1.  Review products on EU store (@jfy133 will check EU store)
        2.  Also do this for the US shop
        3.  Write a blog post
        4.  TEST BUYING VOUCHERS
        5.  LAUNCH AT SUMMIT
    5.  Maxime needs to fix transparency on the dark mode Sarek logo
* Independence messaging
    * Ambassadors - maybe already done
* Tools v3 release
    * Wait until Matthias is back - Sept ~~23rd~~ 26th  onwards
    * Will have blog post + bytesize
* Seqera Containers migration
    * Everyone reviewed? [PR](https://github.com/nf-core/website/pull/2654)
    * Part 2 - go out later, not sync publish
* Training materials
    * Domain-specific training examples
    * Have GitHub Codespaces as an alternative
* Office hours
    * RIKE WILL DO THIS SHE PROMISES I HEARD HER SAY IT
    * Short blog post and bytesize?
        * Scope is changing
    * Monthly advertising etc. on socials
* Tube map poster
    * Printed for summit? Phil to check.

## Next meeting - 2024-07-12

Joined: @JoseEspinosa, Nicolas, @jmir , @sateeshperi, @mribeirodantas, @maxulysse, @jfy133, @FranBonath, @FriederikeHanssen, @mashehu @emiller,  
Apologies:

### Agenda

- [x] Previous meeting action points
    - [X] nf-core shop: custom pipeline logos?
    - [X] nf-core shop: Fran takes first cut(?)
- [x] Oct Hackathon planning?
    - JFY: Should we have a dedicated core team mini-event (one afternoon or something?)
- [x] Pipeline name squatting
- [x] Outreach: general updates

- https://nfcore.slack.com/archives/C072TAN9RDE/p1715679003896129

### Minutes

- Hackathon:
    - For the social, no cooking this year. Instead food/drinks at Hard Rock Cafe (together with people in the training session)
    - About 40 registrations to the hackathon so far
    - No further discussions today because missing Chris etc.
    - General feeling: we should make sure it's a bit less directionless -> clearer group goals
        - A bit harder due to range of experience
        - Hopefully parallel training sessions  will pull away beginners from the experienced people -> more progress
        - Can't expect core team to be able to 'work' "full time" as our responsbility is to help out/organise
        - Make sure to limit scope to nf-core, Boston had a lot of custom pipeline stuff 
        - More specific groups aims/objectives may help
            - For pipelines: define a key 4 'focal' pipeline developers who can be more prepared with lots of modules/issues for not-beginners but newcomers (e.g. from maintainers)?
            - Modules: nf-test? Stubs?
            - Infrastucture: (later project), new features for schema, config-builder?
            - Task-forces (Simon - test data?)
            
- Pipeline name squatting:
    - People who have a proposal accepted, but never finish it/relase - blocks incoming contributors (example scflow)
    - We should have a guideline on the website visible
        - Suggestions:
            - Must be moved to in nf-core in 6mo?
            - Must be released in 6mo?
            - Must have active dev in 6mo?
        - Ideas guidelines:
            - Once template made, must immediately be transferred into nf-core (allows us to have control, and allow us to monitor activity)
            -  Every spring-cleaning if no activity for one year, then lose the right to 'name/pipeline' (archived (if some work incorporated)/deleted (if nothing)/transferred to new pipeline maintainer)
                -  We need to make clearer maintainer doesn't 'own' the pipeline, nf-core _community_ owns it!
            -  We should stop people working in their own organisation (faster review in own organisation is bad argument), hides development too -> while they can do what they want on 'dev', hopefully will help promote new people to good PR practise (even if self merge)R
- Outreach
    - General overhaul of team incoming, but few people responding (onle 3)!
    - Need to start from scratch, maybe update leads (e.g. less seqera)
    - Potenial new team lead: Raquel(? has not been asked yet!)

### Action Points

- [ ] @ewels to follow up shop (Logos activated/locked in?)
- [ ] @FriederikeHanssen to make a draft guideline about namesquatting stuff

## 2024-06-14

Joined: Maxime, Rike, Phil, Júlia, Chris, José, Marcel, Franziska, Edmund, Geraldine, Sateesh
Missing: James, Nicolas, Harshil, Matthias

## Agenda

- WorkflowHub integration now live
- nf-core shop, can we go live?
    - Work required: cleaning up the product list
        - Stick with mostly white + black colours
        - Requested swag: male and female cut, cups, stickers, cushions?, long sleeve, short sleeve
    - Sync EU and US sites
        - Start with EU then copy over to US when happy
    - Everyone seems generally happy, so let's go with it
    - Custom pipeline logos
        - James assigned to this in absentia
    - Fran will take a first cut
    - [Deployment preview URL here](https://deploy-preview-2340--nf-core.netlify.app/shop)
- Wave?
    - [Planning document](https://docs.google.com/document/d/1lar-X-_Bx-nvGema6VaVx7tOqqadZXtMowyaazMkx0k/edit#heading=h.xg76n5inp3za) for discussion
- FYI: Office hours are happening now:
    - Tuesdays 8pm CEST/ 2pm ET
    - Thursdays 11am
    - Are we tracking attendance metrics?
        - Organisers of each session to record numbers of who joins
        - Number of people doing "real" work
        - Chris to look into automated number analytics from Gather Town ([this maybe](https://support.gather.town/hc/en-us/articles/15910327367188-Insights-Premium-Office-Feature))
    - Outreach
        - Blog + socials done. Nothing on Slack yet.
        - `#announcements` without ping
        - `#maintainers` and `#pipeline-maintainers` with `@channel`
        - Chris to take it
- Ontologies / EDAM?
    - bio.tools?
        - identifiers: biotools + doi
        - bibtex?
- Pipeline chaining
    - Maxime has made a variant annotation pipeline locally
        - https://github.com/maxulysse/nf-core_variantannotation
        - https://github.com/nf-core/sarek/pull/1561
    - Imports the pipeline into another (sarek)
        - Copies code, the same way we do with modules
    - Nothing changes within Sarek
    - Ben's POC: https://github.com/bentsherman/fetchngs2rnaseq
    - What should we call these things?
- nf-core ontologies to reduce variation between pipelines
    - Standardised list of parameters for all of nf-core
    - Meta map
    - Sample sheet fields
- Updates from outreach / new nf-core tutorial
    - Had a meeting with outreach TL + guests 👀
    - Overlap with nf-core material with Seqera nf-core training
    - Decisions
        - Have some kind of version controlled / stable docs then fine to have it on the nf-core website
            - Start with: Changes go into `docs_staging` branch
            - Can set up a `CODEOWNERS` file + team
                - Edmund to work with Rike on this
        - Seqera will take the lead on the material, with inputs from community
        - Will host on <http://nf-co.re> eventually
    - Working deadline
        - July (BOSC): Overview of new beginner friendly materials (poster)
        - [WIP improvements](https://github.com/nextflow-io/training/tree/update-nf-training)
        - [nf-demo](https://github.com/nf-core/demo/pull/4)
    - Current work on the nf-core material on hold until after the summer when we will consolidate material
    - YouTube strategy
        - Unlist old videos (per-language)
        - New Nextflow training to go on the Nextflow Channel
- Events
    - Maxime presenting nf-core at JOBIM
        - Plus Reproducibility workshop at JeBiF@JOBIM
        - Plus Chairing the "Workflows, reproducibility and open science" session
    - SBW Sweden
        - Phil giving a keynote
        - Fran + Maxime (+Phil) giving workshop
- Test data & References
    - Data is not immutable
        - Could use hash-based IPLD storage instead of regular blob storage
        - <https://ipfs.tech/>
        - Next step: Get a written document to discuss
- Test data
    - To make a new bucket or not to make a new bucket
    - Which AWS account does the bucket go in? `ngi-igenomes` -> `references`
        - AWS-megatests
    - Collab with Snakemake folks?
        - <https://github.com/compsci-commons/>


## 2024-05-10

Joined: James, Maxime, Júlia, Sateesh, Nicolas, Harshil, Geraldine, Jose, Edmund
Missing: Phil, Marcel (powercut), Chris, Franziska, Matthias, Rike

### Agenda

- Hackathon requests from Marcel
    - [Who will be there in person or online?](https://nfcore.slack.com/archives/C072TAN9RDE/p1715180760289319)
    - [Do we need teams?](https://nfcore.slack.com/archives/C072TAN9RDE/p1715180829379609)
    - [How will we run _Barcelona_ event?](https://nfcore.slack.com/archives/C072TAN9RDE/p1715180886645569)
    - [Can re-use previous instruction/hackathon info/orientiation](https://nfcore.slack.com/archives/C072TAN9RDE/p1715180986792769)
    - [Quiz again but without core](https://nfcore.slack.com/archives/C072TAN9RDE/p1715181047727439)

### Minutes

- Welcome to new core members!
- Zenodo turned off... again...
    - Maxime to follow up with Rike (James vaguely remembers Rike worked out the issue)
- Hackathon preparation
    - Project board is empty
    - Training: Geraldine primary teacher (with support for Chris and Marcel assisting)
        - Sateesh happy to help out
        - Geraldine would like occasional people helping
        - 30 people signed up (possible couple extra)
        - New training: 
            - first day: hello world, then transitions to more biofin. example (with GATK) 
            - second day: intro to nf-core by Chris (navigate and use resources), then writing pipeline with nf-core template
        - Participants of both training and hackathon will still be together for coffee/lunch for networking
        - Swag???? Yes!
    - Hackathon:
        - 30 signed up
        - A few people said they couldn't justify their bosses coming to another in <6 mo
        - Most sci-dev will be there
    - Teams/projects?
        - Sateesh interested in having an nf-test team for implementing at pipeline level
            - Would need e.g. Júlia, who will attend the mornings online 
            - Adam has opened PRs to start this already
        - Maxime: nf-core/references
    - Quiz:
        - Geraldine to write local-boston related questions
        - Matthias not in this time because :baby: 
        - Two versions: easy (no-core), and then hardcore (core allowed)
- Bytesize
    - Kübra (and Nicolas in support) will do intro of template merge with 2.14.1 instead of Phil's
- Barcelona Summit
    - A little hard to say because of no numbers of people yet (e.g. 20 people vs 200)
    - General groups, but allow organic formation of groups to work on specific projects
    - Simple stuff: updating modules to nf-test; subworkflows
    - Important to fill in project board beforehand?
        - How useful is it? Dumping ground for a lot stuff that don't
        -
- Boston
    - Important to fill in project board beforehand?
    - Should be more curated (clear easy tasks etc), maybe search open issues on pipelines that the attendees are interested in/working in the area?
        - Check registration sheet for what people are working on?
    - Ask all pipeline-maintainers (on #pipeline-maintainers) for 2-3 issues for people to work 

### Action points

- HACKATHON
    - [ ] Populate https://github.com/orgs/nf-core/projects/65 (By ALL)
      - [X] Ask all pipeline-maintainers (on #pipeline-maintainers) for 2-3 issues for people to work (@maxulysse )
  - [ ] Spring cleaning on https://github.com/orgs/nf-core/projects/65 
    - [ ] Boston Hackathon/intro by (@maxulysse )
    - [ ] Add more details about the Schedule: https://nf-co.re/events/2024/hackathon-boston
    - [ ] Add Barcelona Hackathon to https://biohackathons.github.io/
- OTHER
    - [X] Zenodo? (@FriederikeHanssen and @jfy133)
        - [ ] Check Zenodo again (@maxulysse )


## 2024-04-12

Joined: Phil, Rike, Maxime, Julia, Edmund, Chris, Franziska, Matthias, James, Marcel

Missing: Harshil (holiday), Gisela

- Hackathon debrief
    - Survey for site organisers?
        - @jfy133 - Simple post in the organisers channel. Can say about 2025 dates at the same time.
        - @FranBonath - to make a survey for 2025
    - Dates for 2025?
        - March 24-26 2025 (last week of March-ish, if no clash with Easter or daylight saving)
        - (Easter is April 20)
        - [ ] Check for clashes with Summit events?
        - [ ] Add to nf-core events website
    - Blog post for hackathon - WIP
- Developer Survey
    - @emiller - https://docs.stashpad.com/document/doc-MeP3AF1kWfzi5cxel4rphVZs
    - Once agreed on, move into Seqera Typeform (Chris / Marcel)
    - No rush, but nice to keep momentum
- Bytesize scheduling
    - Reduce frequency
        - Drop to Biweekly, see if we can keep it up
    - How to get more speakers?
        - Missing pipelines
        - Revisit old talks that are outdated
        - Ask #maintainers group for topics
        - Ask on developer survey
        - Intro to new SIGs (Björn)
- SIGs talks + meetings
- Slack vs Discourse
    - What to do with posts that turn up on the forum organically
    - Do we want to do actively push for this? Against it?
    - Existing users / new users
        - How does someone know when they should join Slack?
    - Notification of discourse activity to Slack
        - Not to respond in Slack
    - Moving Slack threads to Discourse?
        - Not for now
    - Actions today
        - Start using nf-core tags in Discourse
            - Auto-forward these into Slack
            - Go into the main pipeline channel
        - Social stuff stays on Slack
- Who should be in core-team?
    - Seqera <= 50% majority (core vs steering)
        - Proposal
            - core team <= 50% Seqera
            - Steering: < 50% Seqera
    - Rotation of core team members?
        - Phil to go and talk to 5 people
- Potential outreach discussion
    - Core team to stop joining the outreach meetings
        - Delegate more tasks & responsibilities to non-core-team memebrs
    - Spread activities throughout the year
        - Try to avoid having bursts + lulls
        - TODO: Come up with ideas 👆
    - Hackathon responsibities delegation?
        - YouTube streams
        - Gather Town
        - Other small tasks - more regular meetings?
    - Rotate membership
        - Maxime to drop from outreach: https://github.com/nf-core/website/pull/2456
        - Edmund could as well?
        - Add people
            - Kübra / other local hub organisers?
            - Jonas?
            - Nextflow ambassadors?
            - Americans? Carson Miller?
            - Australians? Luke Pembleton?
        - TODO: Chris + Fran + Marcel to meet and come up with shortlist of names
- QuantMS
    - Remove from nf-core as not following the guidelines
    - Communicate expectations. To stay in nf-core.
        - Write list of guidelines that are being broken
        - Must move the pipeline docs
        - Must remove referencea to bigbio for the pipeline
        - @mashehu + @emiller to take this forward
    - If they can't meet these changes
        - Archive the repo with notice on the readme, redirecting
- scflow
    - Archive scflow and start from scratch
    - State this plan, see how much scflow devs complain. Discuss again if a strong reaction.
    - @rike to contact Nico for an update
    - Someone else to communicate on scflow channel, or wait until June for Rike to do it.

## 2024-03-08

Chris, Julia, Rike, Maxime, Jose, Edmund, Matthias, Marcel

- Hackathon:
    - Gather town: Decide which room to use (Reuse office or create new space). Worst case pay for both spaces for a couple of months
        - Maxime and Chris are on it
        - How many seats: 100 online only, 292 at sites, 7Eur/person -> purchase 200? and update on demand
        - Have a desk in the middle for help/company (especially for beginners only)
    - Gift cards:
        - Save Chris, not useing credit cards this time
        - Trying to purchase gft cards instead with costs for pizza for anyone registered
        - 
    - Group leaders:
        - Maybe Laurence also for Pipelines
        - we have a LOT OF beginners: need a European group here as well:
            - Nextflow beginners: Send to do the community training
            - Beginners to nf-core & hackathons: point to group leaders 
            - Beginners at local sites will also have guidance there
            - Online-only beginners: Help desk, send to training. Chris & Marcel will hang out at the help desk. 
    - ✅ Slack channels: Rike
    - Kick-off and Syncs
        - Intorduction / kick-off
            - Introduction
                - Recorded and shared @ewels
            - Group leaders
                - Short vidoes recorded and shared
                    - ✅ Make Slack group for group leaders
                    - Needed by end of next week
                    - ✅ Send message to group leaders @FriederikeHanssen (also populate project board)
        - Sync
            - Daily at 4 pm CET
            - Group leaders talk through minimal slides
            - Aim to keep short but collect all relevant info
            - Record and share 
        - Wrap up
            - Record and share (similar to syncs)
    - Socials
        - Quiz
            - Online: Europe with East Coast
            - Optional: West Coast + APAC
        - Sock hunt
            - Chris will organise
        - Scavenger hunt
            - Need to invite everyone into dedicated channel
            - Push with site leaders to have sites be invovled
    - Update the website with the above @ChrisHakk 

- No update on Office hours (time)
- Special Interest group PR
- Blog will become more prominent
- 

## 2024-01-12

👉🏻 **NEW MEETING SLOT**: 3pm Friday CET

- [**Retreat planning**](https://docs.google.com/document/d/1eSIZb3cjHGtt9Ew7RhA9taGmf-UVWg_t-4BLJ97gW2o/edit#heading=h.7xyz2slkkfh3)
    - How many people?
        - Monday: 16
        - Weds: 10-12?
    - Agenda
        - Started, keep adding things please
    - Social
        - Got some ideas going, continue planning
        - Escape room + Aifur dinner + something?
- **Online hackathon**
    - https://nf-co.re/events/2024/hackathon-march-2024
    - March 18-20
    - Core team to add local sites ASAP (even if tentative)
    - Hoping to have some support from Seqera, should have an idea on funding end of today.
    - Write some more docs on the event page for people interested in hosting
        - How to do a PR / create a page
        - Can do training as part of the event if people want
        - Custom schedules
        - Flexible
        - Support we will offer (and will not offer)
        - [30% discount code for Gather Town](https://support.gather.town/hc/en-us/articles/15910464152980-Discounts-and-Sponsorships).
    - Aim to open registration for sites ASAP (PRs)
    - Open general registration Feb 1st (form)
    - We know about:
        - London - Cosyne (Regina Reynolds + Grant Neilson)
        - Ardigen
        - Heidelberg (DKFZ/Schapiro Lab (Kübra Narci, Florian Wuennemann))
    - **Maxime:** Will contact organisers from last year
        - Done and adding the people to the `#hackathon-mar-2024-siteorganizers` nf-core Slack channel when they reply positively
- **Community training**
    - Languages?
        - Aim to do this for the 2nd 2024 community training
    - Foundational / Advanced?
        - Foundational: yes
        - Advanced: no - yes for 2nd 2024 event (not multi-lingual)
        - Hands on: no
        - nf-core: 2nd training event?
    - When + who?
        - Seqera community team
        - When: defer, come back to this question.
- Boston hackathon / training
- nf-core communities
    - Nomenclature
        - Not community. Working group?
        - Pod
        - Orchard?
        - Spaces?
        - [bushels or pecks](https://globebag.com/blogs/blog/apple-picking-101-what-are-bushels-and-pecks)
    - Features
        - Community talks
        - Webpage
    - Examples (founding groups?)
        - Animal genomics (FAANG)
        - EBP/similar (Sanger)
        - Human genomics (QBiC)
        - Surveillance (Edmund talked to several people in Boston)
        - Imaging (Florian)
        - Metagenomics (James)
        - Benchmarking
    - Metadata
        - Lead contact person
        - List of typical pipelines
    - Timeline
        - Decision: Weds 17
    - Next steps
        - Phil: Finish proposal
        - Website Pages

### TODO

- Everyone: Add local sites if possible
- Matthias: Write docs on event page for how to organise local events
- ~~Maxime: Discount code for Gather~~
- ~~Maxime: Contact local site leaders from last year~~
- Phil: Finish writing communities proposal. Share with steering group.


## 2023-12-04

👉🏻 **NEW MEETING SLOT**: 4pm Weds CET
- biweekly, alternate core / outreach
    - Core: 2nd Weds of the month
    - Outreach: 4th Weds of the month

### Retreat

- Dates: https://lettucemeet.com/l/B5RE3
    - All available: 29.January - 8. Feburary
        - Seqera team retreat 29th Jan - 1st Feb
        - Geraldine Uni Ghent training, 7-9 Feb
    - Tentative dates: 05-08th February: good for everyone:
        - Geraldine can join on Monday
- Who should come
    - Core team
    - Steering group (if available)
- Structure
    - Last year
        - 1 day social
        - 2 days at SciLifeLab
    - This year
        - Monday: meetings / strategy (start in the morning)
        - Tuesday: social
        - Weds - Thurs: hackathon
- Money
    - So far basically everyone can fund themselves

#### TODO:
- @ewels: inform everyone & block calendar
    - check everyone has funding
- @ewels: Start google doc with details + full schedule, ideas for social
- @FranBonath / @mashehu: Book rooms at SciLifeLab
- Swedes: Book social
- Everyone (after confirmed): book travel (if possible, fly in sunday)

### 2024 in-person events

- Split stream workshops / hackathon?
- Breakout rooms with relatively short focussed sessions
    - Split advisors, break up remit
    - Keep strong focus: eg. write a module, do nf-test etc.
- Last half day is pure hackathon? Or all join wrap-up?
- Need to sign up to workshops during registration
    - Can have more than possible to fit, pick the most popular
- Two tracks
    - Pure training
        - Training is about developing with nf-core
        - Lots of communication about online Basic NF training
        - Select participants? Questions in the application form.
            - Command line
            - Workflow manager
    - Workshops / hackathon
        - Workshop ideas: nf-test, how to write a module, wave, how to write a Nextflow plugin(Ben), nf-validation
- Travel fund to get helpers out for training?
- Mostly everyone likes the idea

### Online / distributed event

- March?
    - Clashes:
        - Avoid Seqera team retreats??
        - Easter
    - Slack poll maintainers + Ambassadors for best week in March?
        - @emiller is going to do the poll



## 2023-08-01

Attended: @FriederikeHanssen @FranBonath @mashehu @ChrisHakk @jmir @mribeirodantas 

### Hackathon
- ~50 registered in person + ~70 online
- Cooking for social activity
- First night no formal activity
- Discussion around a theme or speical (nf-test)?
    - Do we want a special group/theme?
        - nf-test?
            - Everyone agrees we should do this if possible
    - More groups because we are a bigger in-person event?
        - New pipelines
        - Existing pipelines
        - nf-test?
        - Infrastructure
        - Modules & subworkflows
        - Beginners
            - We won't have a designated beginners group
            - attendees are expected to know the basics
            - How to support beginners?
                - Point to training material 2 weeks before
                - They can still ask questions in the #nostupidquestions channel
                - Have a dedicated point of contact? Dedicated Slack channel?
                    - Rotate so no one person is responsible for the whole hackathon
    - Think about group leaders now
        - Ask #maintainers @FriederikeHanssen 
        - Try 1 leader on site + 1 online
    - Gathertown
        - Need to be paid and setup  
    - Spring clean?
        - 2-4 weeks before to collect/tidy issues
        - Talk to maintainers team + volunteers to organize
- Swag
    - Do we have enough stickers? @ChrisHakk to check
    - Other swag being investigated
- Social program
    - Quiz
    - Scavengerhunt online + in person
    - Sock hunt
    - Bingo
        - Not (too many) inside jokes
- Sponsor talk
    - Short talk(15 min)
- Introductory videos
    - Were helpful last time  
    - Record group videos for on-line + short talk for in-person
- Next core-team meeting will be a hackathon meeting!

### Summit
- Abstracts extended until August 11
    - Please re-share and promote as much as you can

### Put in grant for bursaries
- https://openreview.net/group?id=InvestinOpen.org/2023/OI_Fund
    - Mentoship 10k USD requested
    - Travel bursaries 25k USD requested

## 2023-07-04

Attended: @ewels @jfy133, @ChrisHakk  @maxulysse  @JoseEspinosa  @mashehu @FranBonath  @mribeirodantas @jmir 

### TODO

- [ ] Write up a new guideline for private pre-release (@ChrisHakk)
- [ ] Schedule first hackathon planning meeting (late Aug / early Sept) (@rike)

### Agenda

- "Private" pre-first-release pipeline development:
    - Examples
        - [Pixelgen](https://www.pixelgen.com/) `#pixelator` - molecular pixelation (Startup; waiting for launch to make code public)
        - `#rnadnavar` (waiting for preprint to make code public)
        - `#nanostring` (@alex waited for BI to give legal ok, now public)
        - `#marsseq` (pre-release for preprint)
    - Discussion
        - Limited difference to people just turning up with complete pipelines
        - We _want_ people to develop _with_ nf-core, but we can't force it
            - :one: Develop in public
            - :two: Develop in private, with invited reviewers
                - Listed on new-pipelines project board, tracked
                - Public after first release
            - :x: Must be fully public after first release
            - :warning: Risk of not tracking status
            - :warning: Risk of pipelines never being released, but volunteer effort goes into it
        - No guarantee of review turnaround
        - Policy on nf-core "first planted flag" status?
            - eg. if another, public, pipeline turns up then we won't block the pipeline for them.
        - Pre-release strategy?
            - Next time: You can do whatever you like, just don't call it an nf-core pipeline (continue version number, don't restart). Use pre 1.0 for before nf-core.
        - :point_right: How does it bring value to the community?
- Governance update
- Summit / hackathon update
    - Website, registration and call for abstracts _about_ to go live. See [staging site](https://staging--nextflow-summit.netlify.app/).
    - Hackathon: regular planning meetings?
        - Ref: Trello boards for [Oct 2022](https://trello.com/b/bOdTFT9d/hackathon-october-2022-planning) and [March 2023](https://trello.com/b/nrzlvkfr/nf-core-hackathon-march-2023).
        - Mid to late august
    - Hackathon: nf-core website event page? Or part of the summit website?
        - nf-core website
    - Barcelona hackathon social: Paella cooking (hopefully!)
    - Talks:
        - Intro
        - 10 min sponsor talk
        - Daily wrap-ups
        - Anything else?
    - Socials
        - Quiz (Matthias H)
        - Sock hunt (gather town)
    - Groups?
        - Any changes to normal?
            - Documentation?
    - Hackathon challenges
        - Present in the wrap-up talk
        - Interest from sponsors (been clear they will be defined by us, on nf-core topics)
            - They can present theirs in the wrap-up?
        - Ideas?
            - "Jury's choice",
            - "Most issues closed"
            - "Most module PRs merged"
            - "Best Paella"
            - "Funniest Paella"
- Summit _**2024**_: week of Sep 23 or Sep 30??
    - [Americas Cup](https://www.americascup.com/37th-americascup-barcelona) (sailing competition) will be in Barcelona :boat: !
    - ![](https://hackmd.io/_uploads/rJW1pKWKh.jpg)

    - 24th September - Barcelona bank holiday
- New website
    - Please review review review!
    - Go live: Thursday 6th

## 2023-06-13

Attended: @mashehu @FranBonath @JoseEspinosa @ggabernet @ChrisHakk @jmir @FriederikeHanssen @YO3oG0hdSw2Gv5IWHc0nfA @ewels @maxulysse

### Agenda

- Hackathon + Summit
    - 2024: talks first, then hackathon?
    - Boston: 1.5 days talks, 1.5 days hackathon is ok 👍🏻
- CZI Funding / nf-core funding
    - Options:
        - [Opencollective](https://opencollective.com/nf-core) with Seqera as financial host.
        - Setting up a non-profit financial institution for nf-core (with or without opencollective).
        - Applying to be part of [NumFocus](https://numfocus.org/) (would be our finantial host, - takes 15% of all budget) 
- Slack?
    - Nextflow: move to https://community.seqera.io/
    - nf-core: stay on Slack for the short to medium term
- Updating tools / tools release
    - Maxime wants more frequent releases
    - Sarek: can't be downloaded now (Singularity images)
    - Fix: `nf-core download` (Matthias Zepper)
    - Fix: Linting for modules
    - Need a bunch of new linting for registries
        - Pushed to quay.io
        - Minimum NF version
        - Compatability with `nf-core download`
- Bumping the minimum version of Nextflow
    - `singularity.registry` only just came out
        - Only needed when not biocontainer http pulls
    - Three options:
        - Template
        - Lint for non-biocontainers in `nf-core lint`?
        - case-by-case basis
    - Need to push all non-standard docker images to quay.io?
- New website update
    - https://astro--nf-core.netlify.app/
    - Release: two weeks
- nf-core/bytesize
    - Current cadence of once per week is tough to maintain.
    - Consider dropping to once every 2 weeks?
    - We will think about this when building a schedule after the summer


## 2023-05-02

Attended: @mashehu @FranBonath @JoseEspinosa @jfy133 @ggabernet @ChrisHakk @jmir @FriederikeHanssen @mribeirodantas 

### Agenda

- Sponsorship challenge ideas?
    - virtual booth on gathertown
    - Find the sponsor logo (sock hunt)
        - Hide in the hotel?!
        - Talk to representatives?
        - Password??
    - Challenges
        - Concerns:
            - Don't want to pull people away from the actual hacking
            - Giving free labour to a company? (ok if nf-core)
            - Not doing it well (not getting enough people)
        - Cloud: Most credits spent? Most saved?
            - Proxy: CI minutes?
        - Sponsored projects (eg. Quilt Data?)
        - Projects we come up with?
            - Generic provenance plugin
            - AWS auto-scaling runners
            - Matthias to write userstats
        - Build challenges around what we're doing already
            - Metrics, metrics, metrics
- Boston Summit / hackathon
    - 28-29 Nov: Hackathon
    - 30th Nov: Summit
- Bytesize ideas
    - How to add write new stuff on new website
    - nf-core twitch stream of tools release
- ...

## 2023-04-04

Attended: @FriederikeHanssen @ewels @FranBonath @ChrisHakk @jmir @B3VesHOaRiiF4q1KSjQdBA 

### Agenda

- Hackathon
    - What went well
        - Local sites
        - Scavenger photo thing was good
        - Intro videos
        - Pizzas (but a lot of work)
    - What didn't go well
        - Documentation group didn't have the right team leaders!
            - A lot of mixture with other groups
            - Writing in isolation lead to errors
            - Idea: "Beginners support" ~~group~~ (not a group, part of all other groups), move doc issues to other groups
        - Organising local hubs & group lead was too much work
            - Need more volunteers!
        - Bingo - too many in jokes
- Training
    - 1.4k people registered!
    - More women! (who have better attention spans!) ~1/3rd women
    - Most people happy with pace & content
    - Next training: mid September?
        - Advanced training?
        - More nf-core? (Modules etc?)
        - More basic / beginner level?
            - Outside bioinformatics?
            - Running only, not development?
        - Let's not re-record the same videos
- Mentorships
    - Round 2 just finished
        - Went well, impressed with work
    - Round 3 needs to open... a few days ago? today?
        - 5 paid positions + unpaid
- Summit 2023
    - Dates now live
    - Keynote / invited speakers - need ideas!
    - Barcelona hackathon: hybrid
    - Boston hackathon: in-person only
- CZI EOSS
    - Money probably not going to be renewed.
    - Sponsorship? Events but maybe more.. salaries?

## 2023-03-07

Attended: @jfy133 @jmir @mribeirodantas @FriederikeHanssen @FranBonath @ggabernet  @ChrisHakk @ewels @mashehu 

### Agenda

- Proposition: Quick update rounds from the spring-cleaning teams 
    - Merge queue now implemented in modules! :tada: Works!
    - Review pipelines to archive:
        - Rike Todo: 
            - ✅ Ping Olga, Luis, and Casper about archiving pipelines
            - ✅ Get in touch with lncpipe if there are plans to continue it
            - Ping DSL1 pipeline devs about conversion
            - ✅ Clean up spreadsheet
        - James Todo: Ask Maxime CoproID ✅
    - About page updated - now includes maintainers + new teams.
    - ✅ Will clean up slack channels too
- AWS costs
    - Phil needs to meet with Boof
    - Reduce timeout to 3 days
    - Fusion v2 + NVMe
    - Look into cost-neutral S3 bucket for test_full test data (kraken2 db etc.)?
        - If standard database could be used by others, move to iGenomes (can be both reference genomes _and_ databases)
    - Gisela:
        - Adding labels to the runs -> need to clear up 
        - Pipelines outside of nf-core also use the data increasing egress costs
- Hackathon (27-29 March)
    - Will close **site** registrations on 17 March
        - :heavy_minus_sign: 1 site :heavy_plus_sign: 2 sites
        - Online will stay open
        - Gives Chris time to sort the credit cards for goodies
    - 260 Registrations
        - ~33% Online only
        - ~33% Wellcome Sanger :shocked_face_with_exploding_head: 
        - ~33% Other sites
    - Stickers sent to everyone that gave a postal address :mailbox_with_mail: 
    - Organise an outreach meeting for the week before
        - Can invite site organisers
    - nf-test
        - No response for now. On ice? Tweet!
    - Saba & Cris said in January they will be there
- Training (13-16 March)
    - 1017 registrations :chart_with_upwards_trend: 
        - ~88.5% English
        - ~4.5% Spanish
        - ~4.0% French
        - ~4.0% Portuguese
        - ~0.1% Hindi
    - Published on YouTube at 3 PM daily
    - Dedicated Slack Channels have been made
    - Extra helpers for questions :pray:
        - Ask for more helpers on public channels
        - `#training` for details + discussion, #announcements for visibility
- Summit 2023
    - SUMMIT: 18th - 20th October 2023, in Torre Glories - Barcelona
    - HACKATHON: 16 - 18th
- Boston 2023
    - Likely November 15th 2023 only
    - Tentative: Mon+Tues 13-14 Hackathon

## 2023-02-07

Attended: @maxulysse, @mribeirodantas, @mashehu, @ChrisHakk, @jfy133 , @FranBonath, @FriederikeHanssen (Rike), Harshil, @ggabernet, @jmir 

Chair: ~~@maxulysse~~ Mutiny by the junior core members, @mashehu is now captain 

### Agenda

World domination status update: 90% complete

- ☑ Hackathon
- ☑ Training
- Documentation Translations
- Full tests
    - AWS
    - Azure
    - Google
- Workshop for ISCB/ECCB
    - July in France (Lyon)

### Minutes

- Training
    - Pre-record all training and stream at the same time
    - 520 registrants so far
        - 87.5% English
        - 5% French
        - 5% Spanish
        - 2.5% Portugese
    - Chris to record first, for others to use as a reference
    - nf-core content session 4 ▶️ 2, as popular request: how to execute a pipeline (without dev content)
        - To help describe what a module vs a subworkflow is
        - General feedback: start nextflow cLI + executing an example nf-core pipeline (so session 1), then go 'heres how you build such a pipeline'
    - Note: all training moving from seqera to [nextflow training page](https://training.nextflow.io/) as makes more sense and easier to find
    - Archiving old training?
        - Link directly in the training material to the newest YouTube video sessions. Old versions could be unlisted, so links are not broken.
        - Add a discalimer to older videos
- Hackathon: https://trello.com/b/nrzlvkfr/nf-core-hackathon-march-2023
    - ~120 registrations so far
    - Chris has stickers locally and will send to hubs soonish
    - Decided group leaders
    - Goodies (e.g., Pizza order 🍕🍕🍕🍕🍕)
        - Seqera to support hubs with goodies
        - Chris is finding out how this will work with payments and receipts and will work with site organizers
    - Discussions about schedule, sock hunt, social stuff
- Documentation Translations
    - Becoming very popular request, also specific Mentor/Mentee request for a pipeline into arabic
    - How to implement on the website? And at what level (all nf-core docs, just pipeline docs?)? Just link out to external blogs etc?
    - Marcel
        - his experience is stuff like pipeline docs change much too often (so get out of date quickly, and get criticism/looks bad), 
        - translating training material is better as updates less often
        - better to link out to external material (with caveats out of date, no warranty towards accuracy etc. and use web archive to make sure we'll always have an online version of the translation)
- Full tests -> AWS/GCP/Azure
    - ...?
- Workshop in Lyon

### Action Points

- @ChrisHakk to record Nextflow CLI & how run a pipeline first (video ready by end of this week )
- @maxulysse to ask around Seqera for more Spanish translators 
- @ChrisHakk has 3 kg stickers to send out 
- @Harshil Check Edmund (❓)/Nicolas (✅) if they would be willing to run nf-test group
    - They could also check with nf-test devs if still active?
- @mashehu & @mribeirodantas  Translations: general agreement to link out to external stuff
    - Make sure to Internet Archive

## 2023-01-03

Attended: @maxulysse, @mribeirodantas, @mashehu, @KuylkJ0AS0-limIJRUVsnw 

### Hackathon planning:

- New trello board: https://trello.com/b/nrzlvkfr/nf-core-hackathon-march-2023
- Hybrid with local hubs
- Focus: Subworkflows
- Next meeting: new bingo cards

### Bytesize talk topics

- Take a break around training & hackathon
- Proposed topics in the trello board

---

## 2022-11-01

Attended: @jfy133, @maxulysse, Harshil, @mribeirodantas, @mashehu

- HackMD team plan - can we make 'private' notes for just core team? These notes are technically open...
- Google Calendars! in `outreach@nf-co.re`
    - one calendar for `maintainers`
    - one calendar for `core`
    - bytesize calendar should be created at the website level cc @mashehu
        - We tried that. It is a pain in the bum to autogenerate calendars :disappointed: But there is the rss if it helps
        - I'll look into it then, see if RSS can be used, otherwise, good old usual maxime bot
- Maintainers meeting on nov 25 13:00 (CET)
    - Harshil says happy to step back from lead (James suggests himself/Rike Lead)
    - Maxime happy to help out
- Reproducibility of pipeline results
    - reproducibility of pipeline results across different infrastructure. Some of it is solved via tests including checksums in nf-core/modules, however not all modules have checksums, for various reasons. Do we have guidelines there? Ideally all results should be reproducible. 
        - What about switching to checksum-based tests for all pipelines? (similar as to what is implemented in Sarek with the pytests).
        - alternative [nf-test](https://code.askimed.com/nf-test/) (if / when it works)
    - Suggestion: work on nf-test at next hackathon, James/Nicolas (/maintainers team) work on getting experience before then, and work with nf-test team for fast fixes
    - Seqera planning: 'Seqera approved' badge - to give end-to-end pipeline validation for most common pipelines across ALL infrastructure to ensure reproducbility (e.g. along the lines of clinical validation)
    - cf https://github.com/nf-core/sarek/issues/798
- Refgenie is still alive
    - But not very responsive?
    - discuss next meeting
    - do we want to add more keys to AWS iGenomes?
        - Should we actively take over from Phil?
- Same with PEP
    - But also not super responsive 
    - Idea: move to nextflow/nf-core JSON schema for samplesheet (basic validation), more complicated push to pipeline level (e.g. across rows)
    - Another 

## 2022-09-06

### Notes

- Summit update
    - Registration is closed (Hackathon: on-site 50 people, 108 remote)
    - Fika, Lunch, Bottomless coffee, snacks provided
    - Masks etc. will be sorted out by Seqera
- Training:
    - 219 europe, 105 americas, 67 APEC
    - Gather town (chat disabled) + Slack -> check that the GT chat can be turned off and on
    - :point_right: MG will set up GT by the end of the month
- AWS megatests
    - Not working at the moment. Don't use until fixed
    - :point_right: Revoke nf-core Tower Token :heavy_check_mark: 
    - :point_right: Fix security hole
    - :point_right: When fixed, create new token
    - Still no idea what the underlying issue is
- Refgenie:
    - Talked to Rafal (in Nathan Sheffield's group) currently working on PEP and not Refgenie
    - :point_right: need to get one of us into the project
    - :point_right: JMP emails Nathan directly to get PRs merged
- Edmund/Matthias in contact with Oleh from Seqera
    - Will rewrite website using Gatsby(?)
- Core team retreat
    - Everyone is now booked!
    - Social Event: 
        - Wednesday: Phil's place
        - Thursday: Bar or Aifur
        - Friday: 
- Sentieon: wait for POC
- Goolge/Azure: no news
- Rob Syme joined Seqera
- There seem to be some conda issues in general in the pipelines:
    - If anyone has time to set up a minimal example
- Nextflow patch release in the making & a new website
- Mentoring:
    - Next round starting in October, with 10 people
    - Waiting for survey


#### Other meetings
- Hackathon: 
- Training: 8th Sept, 14:30

## 2022-08-02

### Things that could go to next release

#### Refgenie

- JMP: it is setup on nf-core tools side (dev), just Refgenie build recipes and PRs need to be merged. No response from their side so far.
- Nathan mentioned he would receive more funding hopefully improving response time
- Otherwise: can one of use get access to refgenie and/or aws-igenomes

#### Nextflow parameter validation plugin

- Still pending from Seqera's side
- Probably not in next release

#### Template changes?

- Should be tested with testpipeline.

#### Hackathon planning 
- Next one is August 25th, 14h.

---

## 2022-06-07

### Agenda

- Welcome to new team members
- IRL meetings update
- Updates on grant deliverables
- Updates on requests / big picture
- Updates on pipeline reviews
- Updates on refgenie
- Clean up GT

### IRL Meetings update

- nf-core/core: 21-23 September
    - Covering of travel costs possible? (@jfy133)
- Nextflow Summit 2022
    - Hackathon: 10-12 October
    - Summit: 12-14 October
    - Location: Torre Glories

### Hackathon

- Will there be screens / teleconferencing for hybrid hacking?
- Max capacity for the event space?
    - Spill-over into Seqera offices?


### Updates on grant deliverables

- Mid-grant report due August :scream: 
- Diversity and inclusion:
    - :white_check_mark: Mentorship program - _ongoing_
    - :white_check_mark: Bytesize talks - _ongoing_
    - :question: Written tutorial on how to self-organise workshops
    - :white_check_mark: Carpentries course - _done_
    - :question: Local workshops in different time zones
- nf-core technical roadmap:
    - Definition and tools for a sample sheet schema - _started_
    - Template and tools to create and sync nf-core modules - _done_
        - Working on automatic updates for new versions on Bioconda.
    - Repository for sharing workflows and subworkflows
    - Sharing of test data in workflow-commons repository for nf-core modules test
    - Sharing of workflows on Workflow Hub and Dockstore

### Content updates

- Website restructure, planning doc approved :+1:
- DSL2 docs updates
    - Nextflow stuff underway
    - [ ] Release checklist needs updating
    - [ ] How to run DSL1 pipelines
    - [ ] DSL1 warning for old pipelines, link to docs :point_up_2: 

### Requests

  - Remove branding (Alex)
      - Some devs his end to work on it.
      - Will work with Rob Syme. [PR started](https://github.com/nf-core/tools/pull/1551). _Stalled?_
      - Template sync?
          - Config for sections? Allow regeneration of template for sync.
      - Get modules to work with any Git provider

### Big picture:

- What do about people doing their 'own' stuff?
  - How to make people contribute rather than _'make yet another RNASEQ pipeline'_
  - Increasingly common request is to have "nf-core stamp" on pipelines that use the template / schema / linting.
  - Automated template sync is difficult / impossible when outside of nf-core
- Scientific benchmarking of tools within pipelines and how to scale it.

### How to review/accept pipelines

- Pseudo-PRs aren't working
- How to promote reviewing, but not put people off, but who to track it?
  - Matthias: time, more people around sooner than later
  - How to record who reviewed?
  - GitHub API: there is a 'reviewer' key
- How to track, automate?
  - GitHub tables have some more automation to add stuff autoamtically - e.g. _"Pseudo PR"_ in PR title?
  - Add to PR checklist to add tag if relevant
- Maintainers team?
  - GitHub bot to select from a fixed list to assign each one (randomly)?
  - Review swap is good incentive: encourage that? But need to make it more trackable
  - [sourcecred.io](https://sourcecred.io/)?

### RefGenie

- Phil to email project lead again (Nathan Sheffield)
    - Got a reply, can choose to go with new syntax or old.
      > Got your e-mail, sorry for the delay in response. I've been having some e-mail issues and it's been a crazy month. Anyway, I'm excited to hear this. I'd love to have some support from you with Refgenie. We were right in the middle of a major upgrade when Michal transitioned to his role at the NIH. So, I can see two paths forward...
      >
      > 1. you could continue using the current released refgenie implementation, and we could probably get this to work pretty quickly.
      > 
      > 2. you could go with the new strategy, which is this new PR you submitted (https://github.com/refgenie/recipes/pull/1/files)
      >
      > You'd be helping us test out the new infrastructure this way. Is that what we should do? Let me know if you get this message, since I'm still trying to work out some e-mail issues. Thanks,

    - Asked to have a follow-up call but no response yet (24th May).
- Try to get some nf-core people onto the RefGenie project

### Community metrics

- Website needs a rewrite / update
    - Build new package to handle community metrics?
- Use an off-the-shelf package to measure metrics?
    - https://www.savannahhq.com
    - https://orbit.love
    - https://peritus.ai

---

## 2022-06-07

### Agenda

- Welcome to new team members
- IRL meetings update
- Updates on grant deliverables
- Updates on requests / big picture
- Updates on pipeline reviews
- Updates on refgenie
- Clean up GT

### IRL Meetings update

- nf-core/core: 21-23 September
    - Covering of travel costs possible? (@jfy133)
- Nextflow Summit 2022
    - Hackathon: 10-12 October
    - Summit: 12-14 October
    - Location: Torre Glories

### Hackathon

- Will there be screens / teleconferencing for hybrid hacking?
- Max capacity for the event space?
    - Spill-over into Seqera offices?


### Updates on grant deliverables

- Mid-grant report due August :scream: 
- Diversity and inclusion:
    - :white_check_mark: Mentorship program - _ongoing_
    - :white_check_mark: Bytesize talks - _ongoing_
    - :question: Written tutorial on how to self-organise workshops
    - :white_check_mark: Carpentries course - _done_
    - :question: Local workshops in different time zones
- nf-core technical roadmap:
    - Definition and tools for a sample sheet schema - _started_
    - Template and tools to create and sync nf-core modules - _done_
        - Working on automatic updates for new versions on Bioconda.
    - Repository for sharing workflows and subworkflows
    - Sharing of test data in workflow-commons repository for nf-core modules test
    - Sharing of workflows on Workflow Hub and Dockstore

### Content updates

- Website restructure, planning doc approved :+1:
- DSL2 docs updates
    - Nextflow stuff underway
    - [ ] Release checklist needs updating
    - [ ] How to run DSL1 pipelines
    - [ ] DSL1 warning for old pipelines, link to docs :point_up_2: 

### Requests

  - Remove branding (Alex)
      - Some devs his end to work on it.
      - Will work with Rob Syme. [PR started](https://github.com/nf-core/tools/pull/1551). _Stalled?_
      - Template sync?
          - Config for sections? Allow regeneration of template for sync.
      - Get modules to work with any Git provider

### Big picture:

- What do about people doing their 'own' stuff?
  - How to make people contribute rather than _'make yet another RNASEQ pipeline'_
  - Increasingly common request is to have "nf-core stamp" on pipelines that use the template / schema / linting.
  - Automated template sync is difficult / impossible when outside of nf-core
- Scientific benchmarking of tools within pipelines and how to scale it.

### How to review/accept pipelines

- Pseudo-PRs aren't working
- How to promote reviewing, but not put people off, but who to track it?
  - Matthias: time, more people around sooner than later
  - How to record who reviewed?
  - GitHub API: there is a 'reviewer' key
- How to track, automate?
  - GitHub tables have some more automation to add stuff autoamtically - e.g. _"Pseudo PR"_ in PR title?
  - Add to PR checklist to add tag if relevant
- Maintainers team?
  - GitHub bot to select from a fixed list to assign each one (randomly)?
  - Review swap is good incentive: encourage that? But need to make it more trackable
  - [sourcecred.io](https://sourcecred.io/)?

### RefGenie

- Phil to email project lead again (Nathan Sheffield)
    - Got a reply, can choose to go with new syntax or old.
      > Got your e-mail, sorry for the delay in response. I've been having some e-mail issues and it's been a crazy month. Anyway, I'm excited to hear this. I'd love to have some support from you with Refgenie. We were right in the middle of a major upgrade when Michal transitioned to his role at the NIH. So, I can see two paths forward...
      >
      > 1. you could continue using the current released refgenie implementation, and we could probably get this to work pretty quickly.
      > 
      > 2. you could go with the new strategy, which is this new PR you submitted (https://github.com/refgenie/recipes/pull/1/files)
      >
      > You'd be helping us test out the new infrastructure this way. Is that what we should do? Let me know if you get this message, since I'm still trying to work out some e-mail issues. Thanks,

    - Asked to have a follow-up call but no response yet (24th May).
- Try to get some nf-core people onto the RefGenie project

### Community metrics

- Website needs a rewrite / update
    - Build new package to handle community metrics?
- Use an off-the-shelf package to measure metrics?
    - https://www.savannahhq.com
    - https://orbit.love
    - https://peritus.ai
    
---

## 2022-05-10

### IRL Meetings!?

- Nextflow: 1st week oct?
- Sept 12th-16th: nf-core/core?
- Phil to make new channel and poll

#### New People

Julia: June 8th
Chris Hakkart: Dev. advocate
Erik: 13th June

- CZI:
    - Julia
    - Phil
    - Dev Advocate (Seqera): Asia/Sourth Pacific Chris Hakkart (NZ)
    - Dev Advocate (Seqera): S. America (Brazil)
- ???
    - Matthias
- Outreach (CZI)
    - Franziska (25%)
    - Chus (25%)

Erik: 12 Summer student (Seqera)
Julia: 8 weeks (SciLife)

#### Requests

Requests:
  - Remove branding (Alex)
      - Some devs his end to work on it
      - Will work with Rob Syme. [PR started](https://github.com/nf-core/tools/pull/1551).
  - Custom container?
      - Requires some thinking. Use `task.ext`?
      - Maybe wait a while: new Nextflow configs coming.

Review of 2.4 tools release? Phil goes through
  - Milestone basically just waiting for Phil's reviews: [2.4](https://github.com/nf-core/tools/milestone/13)

#### Big Picture

What do about people doing their 'own' stuff?
- How to make people contribute rather than _'make yet another RNASEQ pipeline'_
- Increasingly common request is to have "nf-core stamp" on pipelines that use the template / schema / linting.
- Automated template sync is difficult / impossible when outside of nf-core

#### How to review/accept pipelines

- Pseudo-PRs aren't working
- How to promote reviewing, but not put people off, but who to track it?
  - Matthias: time, more people around sooner than later
  - How to record who reviewed?
  - GitHub API: there is a 'reviewer' key
- How to track, automate?
  - GitHub tables have some more automation to add stuff autoamtically - e.g. _"Pseudo PR"_ in PR title?
  - Add to PR checklist to add tag if relevant
- Maintainers team?
  - GitHub bot to select from a fixed list to assign each one (randomly)?
  - Review swap is good incentive: encourage that? But need to make it more trackable
  - [sourcecred.io](https://sourcecred.io/)?

#### RefGenie

- Phil to email project lead again (Nathan Sheffield)
- Try to get some nf-core people onto the RefGenie project