At CodeDay Labs, we aim to ensure that every issue selected for students meets our requirements. To achieve this, we subject each issue to rigorous quality control and thorough examination.

What Peer review exactly is at CodeDay Labs?

Peer review is the process by which a group of people in a field assess an item to decide whether or not it is fit for use. In a similar way, the issues that our managers submit at OS Database will be subjected to a multi-staged peer review process in order to assess their quality.

Here is the workflow designed in some steps that will greatly assist us in carrying out the peer review of the issues:

  1. Visit the OS Database and look through the newly added Issues. The database consists of all the issues provided by our OS Managers and Partner Projects.
  2. Already distributed, a number of issues will be assigned to various reviewers and the notification for each assignment will be sent on mail and Slack.
  3. Every issue that is awaiting a review has "Not Started" as its default review status in the first column of the database. When we begin reviewing a issue or set of issues, set the status to "In Progress”.
  4. The columns labelled "Name of the Project" through "Notes by Manager" contain all the information required regarding the open source issues that the managers have submitted. If applicable, these columns may also include a note from the managers.
  5. The column "Reviewer assigned" lists the reviewers who have been assigned to that particular issue. So, you can begin by going over the issues that have been assigned to you. If there are any notes you have for the team, you can always mention them in the section labelled "Notes by Reviewers.”
  6. The next step is to perform a quality check on the issues to determine whether or not they are suitable for use. If an issue does not meet our standards, you reject it and mark it as "No" in the section titled "Considered for Use." If, however, the issue appears promising, you may mark it as "Shortlisted" and take it further.
  7. It is advisable to begin the reviews as soon as the managers add a few issues and continue the reviews concurrently when they add more, as each reviewer will be individually reviewing the set of issues assigned to them for reviews.
  8. The last step is to conduct a final group review of the issues that are shortlisted in order to verify their quality and determine whether or not they are a good fit. If they are finalized during the final stage, we mark them as “Yes” in “Considered for use” column else we mark them as “No” and set the “Review Status” in first column as “Completed”.

The flow would work like:

Untitled Diagram.drawio (1).png

Some Important dates and numbers for us: