Review bonus
As Drupal is such a cool project, many people want to contribute to it. We need your help to manage the flood of applications, so we created the Review Bonus system. This system rewards people who are willing to help out with a bonus by prioritizing their application.
This will speed up your own project through the review process and you will learn a lot. The hope is that you will continue your involvement thereafter.
How it works
In order to join the Review Bonus system, you should complete the following steps:
- Review three different project applications whose status is Needs review. While not mandatory, there is a template that you can use to make sure you cover all of the necessary points in your review.
- Add a link to the comment you created in the issue summary of your own application issue, for example creating a new section (Manual reviews of other projects) where the links are listed.
- Then add PAreview: review bonus in the Issue Tags field for your application.
Once the above steps are completed, you have joined the prioritized 'Review Bonus” issue queue and your application will be reviewed in turn.
What happens next
Your project will be reviewed by anyone who has time and may be set the issue to Needs Work if a project file requires changes. We will regularly check the PAreview: review bonus list and provide feedback on your module in order to get it approved.
When your own project application issue is set back to Needs Work by reviewers, the review bonus tag will be removed and your project will lose priority over the normal issues. This will only happen once, and is designed to encourage you to complete another 3 manual reviews of separate project applications.
Once you have completed another 3 reviews, you should follow the steps above, adding in the links to the second round of reviews, and add back the tag.
Once this is done, you will remain on the prioritized queue until your project application issue is finished.
Summary
To join the Review Bonus track, you are asked to complete a minimum of 3 manual reviews of other applications and a maximum of 6 to remain on that bonus track. You can of course complete all 6 reviews at the beginning if you want.
If you use the tools available to ensure that your project meets coding standards, you may only require the first phase (3 reviews) but for applications that require more attention by reviewers it was decided that a second phase of reviews is required if you want your issue revisited under the bonus system.
Examples of applications that successfully got a review bonus
How to review other project applications
As mentioned above, we are always running short on project application reviewers, so we need your help in manually reviewing other project applications. Whether joining the Review Bonus program or just getting involved, you can refer to the following guidance for reviewing other project applications.
- Read How to review security advisory coverage applications and sub-pages.
- Read Writing secure code and sub-pages.
- Learn from others how they did a review, checkout closed issues that lead to a project promotion.
- You can use automated tools for review, but you must always do an additional manual review (reading through the source code) and comment on the code. If you don't do a manual review of the code by yourself, you may lose the bonus.
- Pick the oldest application from the review bonus list and get started! (If it is empty pick the oldest from the "needs review" list.)
- You can use the review template to ensure that you cover all of the necessary points.
- When you post your review comment, set the issue status to needs work, if you found some problems with the project.
Further useful resources
- Security advisory coverage application checklist
- Text-Templates for typical issues
- Instructions about the current review process
- The Code review for security advisory coverage applications group!
Thank you and welcome!
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion