Code Review Data Collecting

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by zzolo on April 15, 2011 at 12:11am
Last updated by sreynen on Fri, 2011-05-13 04:21

We need to start data collecting about the code review process so that we can make more informed decisions. See zzolo's post for more context.

One thing we can all do to ease data collection, as well as speed up reviews, is apply appropriate tags and components to issues. Issues have "module" and "theme" components. Beyond that, here's a set of standard tags everyone should use, based on a suggestion by greggles:

  • "PAReview: Security" -- security issue found during review.
  • "PAReview: LICENSE.txt" -- LICENSE.txt file found during review (shouldn't be there).
  • "PAReview: GPL issue" -- non-GPL code found during review (shouldn't be there).
  • "PAReview: Ubercart" -- project relates to Ubercart, often helps to have review from someone more familiar with Ubercart.
  • "PAReview: CiviCRM" -- project relates to CiviCRM, often helps to have review from someone more familiar with CiviCRM.

Comments

Improve Data Collection Solution

Posted by TimelessDomain on April 27, 2011 at 8:07pm
TimelessDomain's picture

Data collection to support the Code Review process would greatly be improved by establishing the system outlined here https://drupal.org/node/1140208 Secure Code Review Wiki - Centralized Database of Drupal Code Exploits

Freedom Isn't Free

Code review for security advisory coverage applications

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: