nf-core/maintainers meeting notes 2025

--- title: nf-core/maintainers meeting notes 2025 tags: meetings,maintainers ---  ## 2025-11-28 1. [ ] Adam 2. [x] Adrien 3. [ ] Anabella 4. [ ] Edmund 5. [x] Evangelos 6. [x] Famke 7. [x] Felix 8. [x] Florian 9. [ ] Igor 10. [ ] James 11. [ ] Jasmin 12. [x] Jim 13. [x] Jon 14. [ ] Jonas 15. [ ] Joon 16. [ ] Jose 17. [x] Júlia 18. [ ] Lorena 19. [x] Louis 20. [ ] Luisa 21. [x] Mahesh 22. [ ] Matthias D. S. 23. [x] Matthias H. 24. [ ] Maxime 25. [ ] Nico 26. [ ] Nicolas 27. [ ] Pontus 28. [ ] Ram 29. [x] Rike 30. [x] Simon 31. [ ] Sateesh 32. [ ] Usman (probably sleeping) ### Agenda - Discuss how to improve the release process - Guidelines for introducing existing pipelines to nf-core (Igor) - Note in the "workflow specificity" guideline - Anywhere else? - nf-test improvements from our side - Topic channels - new CI for nf-core/test-datasets repo (@mashehu) - Delete sarek and eager! +1 ### Minutes - nf-test improvements from our side - 4 people from the nf-core team have write access to the nf-test repo: Edmund, Sateesh, Nicolas, Maxime - What are the priority changes? - Being able to exclude tags - Topic channels - Compatibility with strict syntax - Local storing of downloaded files/containers/conda environments - Discuss how to improve the release process - Trunk based development (https://github.com/nf-core/proposals/issues/49) - Means potential lack of traceability as most beginners run without -r TAG, so will just run the most recent - No way to deal with this? - Hard to get reviews still, even if you have little PRs - A lot of personal pestering/guilting often required - Especially for pipelines that are less well connected to the maintainers/core team - People don't feel confident to judge scientific accuracy - Maintainers/core team should only be worrying about the Nextflow, not the science. - Dev -> Master release should only be checking the overall guidelines, not the individual PRs - Can we get AI to automate this checking the overall guidelines? Help decrease the burden - Better linting? - Can we have some kind of automated linting report pushed to repo issue/PR? - Try and get the linting issues dealt with sooner rather than when we get to the Dev -> Master release - Should we have any expectations on new pipelines as to how long they are committing to maintaining them? - new CI for nf-core/test-datasets repo (@mashehu) - Now warns on deleting files - Topic channels - Now all merged and able to be used ### Action points Famke volunteered to try and make a permanent monthly Zoom link that doesn't require her present to start it. ## 2025-10-31 1. [ ] Adam 2. [x] Adrien 3. [ ] Anabella 4. [ ] Edmund 5. [x] Evangelos 6. [ ] Famke 7. [ ] Felix 8. [ ] Florian 9. [x] Igor 10. [ ] James 11. [ ] Jasmin 12. [x] Jim 13. [x] Jon 14. [x] Joon 15. [ ] Jonas 16. [x] Jose 17. [ ] Júlia 18. [x] Lorena 19. [ ] Louis 20. [ ] Luisa 21. [ ] Mahesh 22. [ ] Matthias D. S. 23. [ ] Matthias H. 24. [ ] Maxime 25. [ ] Nico 26. [ ] Nicolas 27. [ ] Pontus 28. [ ] Ram 29. [x] Rike 30. [x] Simon 31. [ ] Sateesh 32. [ ] Usman (probably sleeping) ### Agenda / Minutes - How did the hackathon go? - From the regulatory group: Collect stats on pipelines to get an overview of pipeline maintenance - - Topics channels in modules: - Starting conversion to use topics channels. First modules are adopted now - At the moment topics are pushed to a separate branch. Why? Follow up with Nicolas. - This is waiting for a tools release (planned for next week!) - After tools is released, both branches should be merged asap to avoid divergence - + documentation on how to adjust pipeline code to collect topics channels - example on how to include topics: https://github.com/nf-core/rnavar/blob/dev/main.nf (experimental with nf-core-utils: https://github.com/nf-core/rnavar/pull/252/files) - --> Maxime to chase Nicolas - We know from rnavar that we can mix&match topics and versions channel - nf-test is not supporting topics channel now, so modules are exposing emit and topic - How long are we waiting to implement the now-stable workflow outputs? (Jon): - NOW if you want. enforcing around March 2026: https://nf-co.re/blog/2025/retreat-2025#adopting-new-nextflow-syntax - Helpdesk: - APAC: Chris & Arthur - We need to be better at advertising it and organizing it in general: - Needs to be automated -> talk to the outreach team about this (Rike to ping Fran) - Can Seqera promote this as well? Repost? -> Rike/jon to ask Lizzie - US seems pretty abandoned - Can we merge Europe & US? - 3pm CET / 2pm British / 9am ET (?) -> Simon - How to improve release process - https://github.com/nf-core/proposals/issues/49 - - https://github.com/nf-core/proposals/issues/85 - Template updates make it challenging - Lots of pestering to get someone to review - - RFC board in general - Should maintainers votes count for changes beyond pipelines - Mostly about chasing the core team - Some people are not engaging because their votes don't count - people who create RFCs need to actually put in content and not just "landgrab" - Can people that approve, put in actual reasoning? ### Action points THINK ABOUT WHAT YOU WANT THE RELEASE PROCESS TO LOOK LIKE! ## 2025-09-26 1. [ ] Adam 2. [x] Anabella 3. [x] Edmund 4. [x] Famke 5. [x] Felix 6. [x] Florian 7. [x] Igor 8. [x] James 9. [ ] Jasmin 10. [x] Jon 11. [x] Joon 12. [ ] Jonas 13. [x] Jose 14. [x] Júlia 15. [ ] Lorena 16. [x] Louis 17. [ ] Luisa 18. [x] Mahesh 19. [ ] Matthias D. S. 20. [x] Matthias H. 21. [x] Maxime 22. [ ] Nico 23. [x] Nicolas 24. [x] Pontus 25. [ ] Ram 26. [x] Rike 27. [x] Simon 28. [x] Sateesh 29. [ ] Usman (probably sleeping) ### Agenda - Regular: bytesize ideas! ### Minutes ### Action points ## 2025-08-29 1. [ ] Adam 2. [x] Anabella 3. [x] Edmund 4. [ ] Famke 5. [ ] Felix 6. [ ] Florian 7. [ ] Igor 8. [ ] James 9. [ ] Jasmin 10. [ ] Jon 11. [ ] Joon 12. [ ] Jonas 13. [ ] Jose 14. [x] Júlia 15. [x] Lorena 16. [ ] Louis 17. [ ] Luisa 18. [ ] Mahesh 19. [ ] Matthias D. S. 20. [ ] Matthias H. 21. [x] Maxime 22. [ ] Nico 23. [ ] Nicolas 24. [ ] Pontus 25. [ ] Ram 26. [ ] Rike 27. [x] Simon 28. [ ] Sateesh 29. [ ] Usman (probably sleeping) ### Agenda - Last month's action points follow up - [ ] Edmund: Activate git lfs on test-datasets already (to make it faster for cloning) - [x] James: Add decisions as proposals - RFC: https://github.com/nf-core/proposals/issues/70 - [ ] Edmund: enquire costs of hosting modules on cloudflare - [x] James: contact special interest groups to find out what minimum information they want for documented - Test data follow up - See [thread](https://nfcore.slack.com/archives/C07B5FK9GKA/p1753970916859429) from Matthias/Phil: summary, AWS S3 probably most secure (very long history of support) and we shouldn't have egress costs because our modules tests now run on AWS (run-on). Local runs are fewer and small data files so not much - General approval for AWS: biggest Q is submission/review process - ideas? - Further thoughts? - Survey: https://nfcore.slack.com/archives/C070369GP7T/p1755679519083569 and [results](https://docs.google.com/spreadsheets/d/17iagyRS3myBIS_m4-fDhmu-_016yQmqRT3gkFHbg9M4/edit?usp=sharing) - nodefaults: - {%preview https://github.com/nf-core/modules/issues/8847 %} - {%preview https://github.com/nf-core/modules/pull/8250 %} - Helpdesk start up again in Septmeber! Prepare [new schedule](https://docs.google.com/spreadsheets/d/1c1Pz97W5azlPph9iiORAxRCLc6q4KBQRfK4M0h127KM/edit?usp=sharing) - please sign up! ### Minutes - test data - stored on cloudflare should be cheap - plans for migration - language server and automatic nextflow lint and format - on hold until harshil alignment is fixed - but we could at least run it - how about just running it and comment warnings and errors (and maybe fail?) - topics - should be in template first before we can start putting it in - with nf-core-utils we can mix topic and legacy versions channels - seqera containers - arm build - automation - how to handle the container definition - pain points - process.success and process.failed should be before assert - nft-utils https://github.com/nf-core/tools/issues/3691 https://github.com/nf-core/tools/issues/3737 https://github.com/askimed/nf-test/pull/310 https://nf-co.re/blog/2024/seqera-containers-part-2 https://github.com/nf-core/tools/issues/3738 Maxime showcased his nf-test setup in sarek ## 2025-07-25 1. [ ] Adam 2. [x] Anabella 3. [x] Edmund 4. [x] Famke 5. [x] Felix 6. [ ] Florian 7. [x] Igor 8. [x] James 9. [ ] Jasmin 10. [x] Jon 11. [x] Joon 12. [ ] Jonas 13. [ ] Jose 14. [ ] Júlia 15. [ ] Lorena 16. [x] Louis 17. [ ] Luisa 18. [ ] Mahesh 19. [ ] Matthias D. S. 20. [ ] Matthias H. 21. [ ] Maxime 22. [ ] Nico 23. [x] Nicolas 24. [ ] Pontus 25. [ ] Ram 26. [x] Rike 27. [x] Simon 28. [ ] Sateesh 29. [ ] Usman (probably sleeping) ### Agenda - Let's 'burn nf-core/testdatasets to the ground' - _@edmundmiller June 2025_ - [Slides](https://docs.google.com/presentation/d/1M4VDIsTI_Vy0WPjTfIFuny2DektvIxmLQsbMJ7cnNn0/edit?usp=sharing) ### Minutes - Structure - Maxime: chaos, no structure (s3 style) - Jon: Write once (immutable) - point to the hash URL instead, because some people have modified the contents of a file and now it doesn't work - Simon: GitHub is the wrong place? - Edmund: GitHub is OK, we can lint for usage of hash - Famke: we need more metadata, how to link to the original data (if derivative); which chrs in there? Not documented and some tools need specific - Anabella: same issue, have a way to visually inspect contents of files without downloading? - Louis: idea -> stricter way of naming files; mega metadata table to describe each test-dataset; filename should be descriptive enough to know what is inside (no test.vcf). - James: one mega file won't work, some generation is too complicated -> one README next to each file - Famke: meta.yaml for each - Edmund: we should use git lfs not git because every line change makes it huge (so checking out hte repor is massive) - Example from xeniumranger because all test-datafiles were bigger than 10mb - Hugging face we have up to 5GB per file; and unlimited free - Simon: Any drawbacks of hugging face - Edmund: separate team managemnet (not a free for all); on different system - Edmund: another benefit is can put on s3 - but also nf-core s3 usage will cost something (or use cloudflare r2(?) which should be free - but would need to ask someone for credits etc.) - Jon: what is huggingface? - Edmund: Basically just git repo but using git lfs - Jon: Why not git lfs on normal git? - Simon: can we activate git lfs on existing repo? Yes! - Famke: current structure of `master` being empty makes it too easy to forget to docs - Simon: we should move to split modules and test-data - Louis: the GitHub file size limit isn't necessarily a bad thing, enforces people to think about things -> GENERAL AGREEMENT - Louis: maybe just have a spillover when something absolutely can't fit in ? Either same location or seaprate location (Reduce costs) - Famke: is there a way of tracking what datafiles have been used (and delete stuff not used)... no-one knows? - Simon: are we discussing modules or pipelines? Lets just focus on modules (biggest issues) - DECISION: start from scratch with an new repo for modules (aand archive old one, slowly move stuff) - Jon: all the test files are already on s3, just use that instead? But what would the process be for uploading. - Costs? S3 cahrgers you moving outside of region (i.e. ingress/ingress)? - Oh wait GHA... - Cloudflare R2 for free (only charge for hosting, not ingress/egress) - Benefit: don't have to archive -> **we want a directory compatible filesystem** - 42basepairs? You can attach public buckets, and use it to navigate and can look inside: https://42basepairs.com/browse/r2/genomics-data?file=variants_CHM13.vcf.gz (open s3 viewr) - Questions: how stable/longevity? How compatible with non-bioinfromatics data? Can just ask for 'free support' QUESTION: Who actually likes to clone the test-dataset repo 4/12 Location: - Much faster to download - Supports directories - Free (or cheap) -> doesn't charge for ingress/egress Metadata - Famke: yaml file? Too restrictive? - What we want: - Keywords? - Organism? - Whole genome? - Chromosomes embedded? - Individuals ? - Is it real or simulated data? - Is it a tool specific file vs a generic file? - What command(s) was used to generate - What version of the tool was used for generation? - Source location of any upstream files? - Genome version - Panel - Support 'grouped' files (e.g. pairs-end reads, ped/bim/fam, bam/bai)? - Who created (author) - We need subgroups for each discipline to find out which groups need what (Genomics, imaging) - Could we use special interest groups? - Specifications - Should we copy over test-data from a tool that already has gt their own - Igor: Julia, ### Action Items - [ ] Edmund: Activate git lfs on test-datasets already (to make it faster for cloning) - [x] James: Add decisions as proposals - [ ] Edmund: enquire costs of hosting modules on cloudflare - [x] James: contact special interest groups to find out what minimum information they want for documented ## 2025-06-27 1. [ ] Adam 2. [x] Anabella 3. [ ] Edmund 4. [x] Famke 5. [ ] Florian 6. [ ] Igor 7. [ ] James 8. [ ] Jasmin 9. [x] Jon 10. [ ] Joon 11. [ ] Jonas 12. [x] Jose 13. [x] Júlia 14. [x] Lorena 15. [x] Louis 16. [ ] Luisa 17. [ ] Mahesh 18. [ ] Matthias D. S. 19. [ ] Matthias H. 20. [x] Maxime 21. [ ] Nico 22. [ ] Nicolas 23. [ ] Pontus 24. [ ] Ram 25. [x] Rike 26. [ ] Simon 27. [ ] Sateesh 28. [ ] Usman (probably sleeping) ### Agenda - @FloWuenne Help-desk format: https://nfcore.slack.com/archives/C077RNGJTC7/p1750190531124699 ### Minutes ## 2025-05-30 1. [ ] Adam 2. [x] Anabella 3. [ ] Edmund 4. [x] Famke 5. [ ] Florian 6. [ ] Igor 7. [ ] James 8. [ ] Jasmin 9. [x] Jon 10. [ ] Joon 11. [ ] Jonas 12. [x] Jose 13. [x] Júlia 14. [x] Lorena 15. [x] Louis 16. [ ] Luisa 17. [ ] Mahesh 18. [ ] Matthias D. S. 19. [ ] Matthias H. 20. [x] Maxime 21. [ ] Nico 22. [ ] Nicolas 23. [ ] Pontus 24. [ ] Ram 25. [x] Rike 26. [ ] Simon 27. [ ] Sateesh 28. [ ] Usman (probably sleeping) ### Agenda - NO wg-taskforce-test-data takeover, but a Maxime takeover - nf-test migration progress report - @maxulysse will present the RFC proposal - We will look into this from time to time, but Maxime is assuming that most of the RFCs will come from our side anyway - Anyone that cares enough to do an RFC should be a maintainer - [CODEOWNER proposal](https://github.com/nf-core/proposals/issues/40) - [`pipeline/main.nf` file for workflows instead of `pipeline.nf`](https://github.com/nf-core/proposals/issues/39) - References proposal - nf-core/tools release happening next week (monday?) - includes pipeline level nf-test ### Minutes - nf-test migration almost over - 1 module left -> need to specify CPU number for repro - 1 subworkflow left -> https://nfcore.slack.com/archives/C043UU89KKQ/p1748441535247279 - RFCs presentation - nf-core tools release - megatests should be fixed for good - discussion about nf-test pipelines tests conversion - bamtofastq squash-merge from dev to master - DON'T DO THAT :D ### Action Items - [ ] Maxime to create a recurring zoom link for the meetings - [ ] Famke to write an RFC for branch merge ## 2025-04-25 1. [ ] Adam 2. [ ] Anabella 3. [x] Edmund 4. [x] Famke 5. [ ] Florian 6. [ ] Igor 7. [x] James 8. [ ] Jasmin 9. [x] Jon 10. [ ] Joon 11. [x] Jonas 12. [x] Jose 13. [x] Júlia 14. [x] Lorena 15. [ ] Louis 16. [ ] Luisa 17. [ ] Mahesh 18. [ ] Matthias D. S. 19. [ ] Matthias H. 20. [x] Maxime 21. [ ] Nico 22. [x] Nicolas 23. [ ] Pontus 24. [x] Ram 25. [x] Rike 26. [ ] Simon 27. [x] Sateesh 28. [ ] Usman (probably sleeping) ### Agenda - [x] Welcome to new maintainers: Anabella, Louis, Pontus - Goodbye now alumni: Anders, Anders, Carson, Christopher, Lili, Sofia, Rob, Gisela, Harshil - [x] @maxulysse: Can we set up for some pipelines a CODEOWNER, so that the actual pipelines maintainers can check up the PRs being merged, and help them actually maintain pipelines cc @emiller - @FriederikeHanssen Use prefix in output directive: https://github.com/nf-core/modules/issues/7792 - [x] @famosab: I am all for module wishlists (on Issues) I just think we need to do them differently than now - some people also responded that they completely forgot about the issue and do not need the module or it was implemented somewhere else and so on - [ ] @FloWuenne: I propose to include resource optimized configs for `test_full` profiles for all nf-core pipelines. Many orgs run these pipelines with full test profiles regularly for infrastructure tests etc. Default resource configurations are unnecessarily wasteful in most cases! I did some work to generate optimised configs for all pipelines that had succesfull runs since beginning 2024 here : https://github.com/FloWuenne/megatest-resource-optimization/tree/main/optimized_configs - [ ] @jfy133 comments on improvment of use of test-data?: https://github.com/nf-core/website/pull/3327 - @jfy133: take over next meeting for wg-test-data? ### Minutes - Welcome to new maintainers (everyone on holiday unfortunately 😅) - CODEOWNER - Some people want better information when PRs are being reviewed/merged in -> now allowing other groups coming in and reviewing amongst themselves - Two places: modules and pipelines - Opt-in? So not in templates - Have a fallback for core or maintainers (but we already have those rights) - But shouldn't protected branches help with that (you can set restrictions on pipeline repo level stuff) - Add to guidelines that you CAN use them if you want? - What if we autopropgate CODEOWNERS with `maintainer` tag of contribtuion in nextflow.config manifest? - Prefixes: this seems to be a Nextflow bug - https://nextflow.slack.com/archives/C02T98A23U7/p1745528754489099 - Modules wishlishes -> there a TOO MANY ISSUES, to they make sense? - Famke's Idea: have a meta-issue to collect 'wishlist' modules for thoes who want to a module but don't want to implement themselves? - James: label with 'wishlist' and auto-close after 1 year if no-one takes it up (but only if no-one assigns themselves) - Label gets removed if someone assigns themselves (as it shows interest) - Can we re-add label if someone unassigns themselves - Can we ping assignees if they've not done the module after X amount of time - Florian's suggestions: James summarised (but Florian is not there) - Interest in automating? - Firstly test these optimised configs manually in their `test_full` - Maybe initially requiring in first release to add this (After the pre-release run) - James forced everyone to review his PR regarding test-data messiness - Júlia tools updates: - Probably a small patch release prior the bigger one to include the fixes to AWS and the `latest-everything` issue (likely next week ™️) ### Action Items - [ ] Maxime: write a RFC adding codeowners to certain pipelines to test if it upsets people - [ ] James, Jon, Lorena, Jonas, Rike, Nicolas -> add a CODEOWNERs file with their current maintiners -> see if any pushback from any of their co-maintainers - [ ] Revisit in 2 months? - [x] Rike to report Nextflow bug of captured input files in output patterns: - Ben already replied on the issue. It's a limitation of the scratch directive. - [ ] Famke (+ Edmund) to investigate wishlist labelling system - [ ] James/Lorena/Sateesh: try manually Florian's manual configs - [ ] Reivist in 2 months - [ ] James to speak to Simon about a agenda for wg-taskforce-test-data takeover of next meeting ## 2025-02-28 ### Attendance - [ ] Adam - [ ] Anders J. - [ ] Anders S. P. - [ ] Carson - [ ] Christopher - [x] Edmund - [ ] Famke - [x] Florian - [ ] Gisela - [ ] Igor - [ ] Harshil - [x] James - [ ] Jasmin - [x] Jon - [x] Joon - [x] Jonas - [x] Jose - [x] Júlia - [ ] Lili - [x] Lorena - [ ] Luisa - [x] Mahesh - [ ] Matthias D. S. - [ ] Matthias H. - [x] Maxime - [ ] Moritz - [x] Nico - [x] Nicolas - [ ] Ram - [ ] Rike - [ ] Rob - [ ] Simon - [ ] Sofia - [ ] Sateesh ### Agenda (Don't edit, only append!) - @jfy133: Tshirts: final vote - big or little ducky - Ref: https://nfcore.slack.com/archives/C043UU89KKQ/p1740642277922649 - @jfy133: Spring cleaning (10-15th March): what are we doing, and who does what - Planning doc: https://hackmd.io/@nf-core/ryU88h3YJl - @mashehu : hackathon projects ### Minutes 1. Tshirts - Will go live for a few days next week (James to announce) 2. Spring cleaning - More than 500 people joining the hackathon, so we need to clean - The war plan was copied over from last year - And updated: https://hackmd.io/@nf-core/ryU88h3YJl - Everyone should have a look at it - We will be cleaning up the teams as well 3. Hackathon projects - GPU testing - nf-test testing - references - Ontologies? ### Action Points - Spring cleaning (@jfy133 to add to calendar): - [ ] Kick off meeting Monday March 3rd 15:00 CET - [ ] Closing meeting Friday March 7th 15:00 CET - Hackathon - [ ] @maxulysse to create a project for references - [ ] @FloWuenne to create a project for GPU testing ## 2025-01-31 ### Attendance - [ ] Adam - [ ] Anders J. - [ ] Anders S. P. - [ ] Carson - [ ] Christopher - [x] Edmund - [x] Famke - [x] Florian - [ ] Gisela - [ ] Igor - [ ] Harshil - [ ] James - [ ] Jasmin - [x] Jon - [ ] Joon - [ ] Jonas - [ ] Jose - [x] Júlia - [ ] Lili - [x] Lorena - [ ] Luisa - [x] Mahesh - [x] Matthias D. S. - [ ] Matthias H. - [x] Maxime - [ ] Moritz - [ ] Nico - [x] Nicolas - [ ] Ram - [x] Rike - [ ] Rob - [x] Simon - [ ] Sofia - [ ] Sateesh ### Agenda (Don't edit, only append!) - Spring cleaning date decision - (final point:) Did we scare Famke off? - Question from Maxime: Who actively use the igenomes.config in their pipeline? - Proposal: Arthur Gymer for maintainers (again(?)) - Proposal: echo commands rather than removing args (IN STUB) - Proposal: remove latest-everything from _required tests_ on release PRs (still run, but not block releases) - Question from Florian: How can we get people to join the North American side of helpdesk? - Default prefixes in modules (https://github.com/nf-core/website/pull/2608) ### Minutes - Spring cleaning date decision - Week 11 (03-10 -> 03 -14) - We haven't scared Famke yet - Maxime is given free rein with igenomes.config - He will hopefully present references soon - Maxime will ask Arthur about maintainer - STUB? args? Let's think more and raise the question later - We're removing args in stub due to language server - We don't mind echoing the args, but we don't print them, so it's kinda useless - Let's comment on the static types PR and see if we can do something there - Let's remove latest-everything from REQUIRED TESTS - Florian + Lorena have been almost alone in AMERICAS helpdesk - He worked on stickers, so it's still a win - Simon wants us to talk again about the default prefixes - Simon wants us to do pre-spring cleaning - Edmund informs us that seqera containers are in progress ### Action Points - [x] @jfy133 give @maxulysse and @FriederikeHanssen co-hosting rights - (not possible as on different paid 'accounts' - maybe switch to a Seqera ) - [x] @jfy133 Figure out how to get the Zoom meeting on the calendar invite - See above... - [x] @maxulysse asks Arthur about being a maintainer (even in Autralia) - [ ] DECISION FOR STUBS - [ ] echo args for now instead of removing - [ ] Capture stdout in stub test? - [ ] Talk with Ben and maybe Lukas and see how we can improve - [ ] Testing stubs with a plugin instead of writing stub tests - [ ] Let's do it and remove latest-everything from REQUIRED TESTS - [x] Helpdesk AMERICAS - [ ] Change time? - [ ] Rebrand as Happy Hour? - [x] Communicate more about the questions that can be asked - [ ] See with outreach team and see if we can pump on ads - [ ] @jfy133 @oRVLyAzyS6SABKri_BFj5w @maxulysse @emiller https://github.com/nf-core/website/pull/2608 - [x] jfy133 - [ ] ALL OF US - [ ] Check your open PRs (@emiller :eyes:)

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.