Community workflow

The CODECHECK community workflow described here is the steps that codecheckers follow when conducting independent CODECHECKs, i.e., without an active collaboration with a journal or conference. The community workflow uses free to use infrastructure, in particular the GitHub organisation codecheckers and Zenodo for depositing codecheck certificates. The community workflow is a concrete implementation of the abstract CODECHECK process and follows the CODECHECK principles, although it may fall short of Rule 3, because the CODECHECKs are not yet properly registered as peer reviews in open research information databases.

The community workflow documentation is split into three parts:

Support

Every CODECHECK is unique, just as the associated research article. The codechecker can partly rely on the examples below and the full breadth of CODECHECKs for good practices and approaches for codechecking.

If you have any questions or concerns, or get stuck, please reach out to fellow codecheckers in the public CODECHECK discussion forum or contact the CODECHECK team (see footer) if you need to consult on sensitive information.

Examples

See the CODECHECK register for a full list of codechecks, including direct links to the reports and register issues. You can check there for more examples from different communities. The good practices and common pitfalls from the examples below are summarised in the author guide.