---
# System prepended metadata

title: spring cleaning march 2023 kick off
tags: [' meeting notes', ' maintainers', spring cleaning]

---

---
title: spring cleaning march 2023 kick off
tags: spring cleaning, meeting notes, maintainers
---

## Group Assignments

We have assigned maintainers who weren't in the meeting and didn't indicate they weren't around to two groups (one main, one fallback). Please join the corresponding channel to find out your plan of action.

All Slack channels are public and can be found using the links below :point_down: 

- 1) ✅ nf-core/modules repo cleanup [#springclean-modules](https://nfcore.slack.com/archives/C04SJUGR2CS)
    - @matthdsm
    - @jasmezz
    - @louperelo
    - @nvnieuwk
    - @ramprasadn
    - @sppearce
    - Jon (suggested)
    - Adam (suggested)
    - Anders S. P. (suggested)
    - Anders J. (suggested)
- 2) ✅nf-core/configs repo cleanup [#springclean-configs](https://nfcore.slack.com/archives/C04SMCRL8TE)
    - @matthdsm
    - @jfy133
    - @maxulysse
    - @ramprasadn 
- 3) ✅ nf-core/documentation [#springclean-docs](https://nfcore.slack.com/archives/C04SG0ZUQTF)
    - @jasmezz
    - @ChrisHakk 
    - @nvnieuwk
    - Rob (suggested)
    - @sofstam
- 4) ✅ Core Team Tasks [#springclean-core](https://nfcore.slack.com/archives/C04SG11EE4D)
    - @jfy133 
    - @mashehu
    - @FriederikeHanssen  (suggested)
    - Harshil (suggested)
- 5) ✅ Hackathon preparation [#springclean-hack](https://nfcore.slack.com/archives/C04S4CZMSMD)
    - @jmir 
    - @louperelo
    - Gisela (suggested)
- 6) ✅ nf-core/pipelines [#springclean-pipelines](https://nfcore.slack.com/archives/C04T8KDMXUY)
    - @maxulysse
    - @emiller (suggested)
    - Gisela (suggested)
- 7) ✅  Infrastructure (nf-co.re,tools,test-pipelines,nf-core org) [#springclean-infastructure](https://nfcore.slack.com/archives/C04S4D35T6K)
    - @mashehu 
    - @jmir
    - Moritz (suggested)

If you find open PRs that may still be being worked on: add tags as a reminder to revisit this at the end of the week:
- awaiting-changes 
- awaiting-feedback

Guidance:
    - Add stale label to issue or PR, if older than 1 year, 
        - leave comment to give a warning that they have 2 weeks to reply and they should remove stale tag if still working on/don't want it to be closed

Pipeline group task: create `stale` label for every pipeline; 

Infrastrucure task: set up autodetection of stale label being added, if 2 weeks with no acitivty/response _then_ auto close with friendly message.



## Results

    - RESULTS:
        - Slack channels: ~170-155ish
        - Github teams: cleaned up (1), consolidated, deleted (3)
        - Slack teams: cleaned up (1), consolidated, deleted (2)
        - Maintainers lists: on website 🎉
        - Pipelines: archived 7 (due to no activity, not released, superseded, and/or consolidated):
            - genomeskim, liverctanalysis, kmermaid, crisprvar, ssds, rnadnavar, denovohybrid 
            - DSL1 & released pipelines will get evaluated next time
        - Adding main pipeline devs to #pipeline-maintainers

- Infrastructure group:
    - Check repos in org :heavy_check_mark: [@mashehu]

- Modules
    - Older than March 2022; add stale labels (with 2 weeks)
    - Tagged hackathon2023 if very interesting
    - PRs reviewed and merged
    - Checked PRs had an open issue and added
    - Looked through subworkflows, checking to see if they matched specifications
        - Needed a lot of work - longer than expected
        - Differences in `meta.yml` if full channels or each element separately like modules -> need to discuss (but Nicolas went with full channels)
        - Matthias will tackle this when it comes to JSON
    - Keywords: made some suggestions to make them less redundent; big list picking representive of each
        - Matthias said we should put on guidelines page!
        - See: https://hackmd.io/cyrGiRu0RCGK0u4QdalWwQ?both
    - Branches: all merged deleted etc. 

- Documentation
    - Went through each page (~19): checked broken links, old references to DSL1, atom etc.
    - Focus on making issues for hackathon (easy for newcomers)

- Pipelines team
    - Transfered two pipelines to nf-core organisation (rather than a fork)


## Feedback

- Bot for tagging stale stuff etc?
- There is a PR for that!
    - Modules try already
    - For pipelines - requires template merge
- Freedom to do in your own time - was good!
- Maybe two a year is a good idea (so it doesn't build up)
    - not all tasks (e.g. core team tasks only has to be once year)
    - test data for next time? more pipeline stuff?
- Try and expand to more people - not just maintainers
    - Pipeline maintainers remind them to do a clean up (over a month)