# Triage team recruitment

As the Nushell project grows, we are starting to get quite a few issues in the tracker :open_mouth:
Some have probably been addressed without noticing it, some other might be duplicates or could be refactored into [`meta-issues`](https://github.com/nushell/nushell/labels/meta-issue), more could be labeled more precisely, etc, etc...

### This is where you, the community, can have a big impact :point_right:

> We are looking for motivated regular members of the community and contributors to help us in that endeavour.

As a first step in that direction, we would like to see if that idea can be made real.
In order to test that, you will have access to
- the public [issue tracker]
- a private document to simulate a real-life triage process

In the private document, you'll
- have a look at the [issues][issue tracker]
- mark duplicates and addressed ones
- propose new and better labels
- propose to remove out-of-date problems
- discuss additional resolutions

Once that process is complete, if we want to scale the triage team to the whole [nushell repo], you will be added to the `triage` team on *GitHub* and granted *triage* permissions, allowing you to close, refactor and label issues.

### :postal_horn: if you feel motivated and want to help, please reach out to any *green member of the @CORE-TEAM over on discord*, either in the server or privately

we hope to see you soon :elephant: :heart:

[issue tracker]: https://github.com/nushell/nushell/issues
[nushell repo]: https://github.com/nushell/nushell