This repo collects all information about people conducting CODECHECKs as part of the CODECHECK community.

You can take a look at the codecheckers table, codecheckers.csv to find a suitable codechecker. GitHub even provides a nice search function for the file. Consider skills earlier in the list to be more advanced, later ones to be less strong. If you have a good candidate, please check the codechecker is currently not busy with too many CODECHECKs already (see assigned issues in the CODECHECK register).

Alternatively, you can @-mention the codecheckers team with @codecheckers/codecheckers in the issue for managing the codecheck and ask around for interested codecheckers by adding @codecheckers/codecheckers to an issue comment.

Finally, you can ask the author for recommendations, start an open call for codecheckers on Twitter, et cetera.

If you want to get involved as a codechecker, we need to run through the following steps:

1. Codechecker (you!) opens an issue using this link (with an issue template)
2. Community manager makes sure all required information is there
3. Community manager invites the new codechecker to the Codecheckers Team (Note: the team page is not public)
4. Communtiy manager welcomes the new codechecker
5. Communtiy manager saves information in the "database" and closes the issue with the commit

About CODECHECK