---
# System prepended metadata

title: outreach training discussion 2024-06-11
tags: [meetings, outreach]

---

---
title: outreach training discussion
tags: meetings,outreach, training
date: 2024-06-11
---

present:   Raquel M, @OKZOiVa0QWiYvK12QXWPgQ (Geraldine), @mribeirodantas, @ChrisHakk, @FranBonath, @FriederikeHanssen 

# current resources:
1. in development nf-core training
    - https://github.com/nf-core/website/tree/nf_core_basic_training
    - <https://deploy-preview-2397--nf-core.netlify.app/docs/contributing/nf_core_basic_training>

2. Seqera training for nf-core
    - https://training.nextflow.io/#applied-training

# to discuss:
- where to host which training?
    - IF we can have versioning and better oversight of the changes in the training, we can host nf-core training at the nf-core website
- who is responsible for upkeep?
    - plus for Seqera: has ppl working full time, so they might drive this
    - common work is preferred
- contents of training?
    - have some sort of release schedule / versioning
        - needed for Seqera but also for community training by e.g. ambassadors
    - separate gitpod for nf-core training
    - need to go more basic for intro training
        - nf-core create, add a very simple module, schema, linting
- training vs. documentation
    - have better documentation for e.g. the template
        - Fran to write documentation for the template


upcoming:
- Seqera training will continue for now as is, for the deadline in July that is coming up
- need an addition meeting to map out what goes into the course

# How to organise training releases on the nf-core website
- identify ppl that are responsible and have permission to do changes / reject changes
- treat this like a pipeline: major and minor releases --> TODO: Rike will discuss with Matthias
    - ask Matthias if we can host them in a different repo, otherwise, releases are more difficult (Rike)
    - working on different branches is possible, but tricky
- passing tests - maybe, but loads of work --> low priority, Marcel will try a POC
    - pre-commit hook to make sure it works
    - might add inertia to development of material
    - proof of concept page (Marcel), low prio
- style guide