# spring cleaning template messages

## modules

As a part of spring cleaning 🌻 I am closing this issue as it was inactive for a while. New modules and subworkflows are usually not implemented by someone else. If you need this for your pipeline / project just let us know, reopen the issue, try to work on it yourself and ask for help in our slack channel.

## configs

## pipeline proposals (slack)

🧹 spring cleaning message 🌸

Hello, as a part of the yearly nf-core spring cleaning, we are reviewing the status of new pipeline proposals on our tracking board.
As we've seen no more activity in more than a year, we will archive this proposal as 'timed out'.

If you still wish to work on this pipeline, please make a new proposal.

_Note: nf-core is run 99% on volunteering. The core team may sometimes be slow to reply, so for future proposals please semi-regularly ping the core team for a decision_

## maintainers offboarding (slack)

Hello there :wave:

As a part of the spring cleaning, the maintainers team does an annual review of team members to allow us to make sure we can ensure smooth activity of the team and thus the community.

Via the very scientific method of checking the very haphazardly updated attendance list of each meeting in the meeting notes we note that you have not attended a maintainers meeting in at least the last 6 months, additionally we have not seen you particularly active in the common community repositories (tools, modules, configs, test-data, etc.).

We would like to take this moment during the community spring cleaning to ask if you feel you still wish to and can actively contribute to the maintainers team? Based on this we have three options:

1. If you have in fact been attending the meetings and James has just been bad at tracking, and you've been active in the channels/repos above - please respond with 'Oi yes I have been attending and contributing! Get some glasses and pay better attention James' (Just copy paste that exact text, I won't be offended ;) )
2. If you feel like you no longer have time to commit, then we would like to thank you for your past contributions and activity, and suggest we move you to the 'alumni' of the maintainers team. This also allows us to free up spaces to allow newer very active members of the community to join the team.
3. If you still wish to contribute actively, but recently have had recent time constraints that you envision in the next few months to clear up to allow you to contribute again, please let us know and you can of course keep your place.

Please note that attending the meetings are not required for being in the maintainers team as you may have overlapping meetings with your real job or timezone issues, activity in doing reviews in common repos etc. is our most important criteria

We thank you for your past, current, and future contributions making nf-core the amazing community that it is!
James, Rike, and Maxime (maintainers team leads)

## maintainer invitation (slack)

Hello {NAME}!

Your long-term activity within the community has continued to impress many of maintainers (new and old), and you've been nominated to be added the maintainers team!

We would like to ask if you would like to join us continuing to make nf-core awesome!

The role essentially consists of you continuing to do what you do now: helping reviewing e.g. modules and other PRs outside of your own work/specific pipelines, helping answer questions and guiding the wider community etc, and regularly attending a monthly meeting.

The benefits are: general bragging rights (recognition on the nf-core website, having permission to display :nf-core-duck: on your slack profile etc.), getting more involved in wider decisions and planning for the community, getting early-access to various things both nf-core but also occasionally Seqera related things (at their discretion).

Note that it's not a strict role with quotas etc, it is still a volunteer role so if you have a crunch time at work for example it's ok to drop your activity bit etc- but mostly as long as you keep doing what you're already doing then that's embodying an nf-core maintainer :)

Let us know what you think!
James, Rike, and Maxime (maintainer team leads)