Our Mission
To discuss, document, and rally around the Full Project code review process for new contributors to Drupal. To help people become (better) code reviewers so that the barrier to code contributions on the Drupal infrastructure is minimal but still valuable and to enhance the code on Drupal.org overall.
Started from webchick's talk at DrupalCon Copenhagen and then further enhancements. This is NOT a place to ask someone to review your application. Please read the instructions and use the full project instructions to apply for access.
Our Community
The Code Review team is dedicating to being a strong, cohesive force in bringing in new code contributors to Drupal.org.
- List of Reviewers
- List of Review Administrators
- Team Leads: zzolo
- On IRC: #drupal-codereview
Hold a Sprint!
Code Review Sprints are a great way to build community and get reviews done.
Process Building
It is important to define and document the process of reviewing code as it is so important to the community.
Go Ahead and Review
Anyone with some basic module writing skills can do reviews.
Storytelling and Feedback
It is important to get feedback about this process.
TODO: Create a way for anonymous feedback.
Recent Content
- Project application checklist
- Session at Drupalcon Munich
- Drupal Camp LA
- Issue priority for review bonus only
- Making review bonus strongly recommended
- Maintain project quality on d.o
- Group of people doing application...
- Project application overview, with rocketship
- klausi reviews/approves project applications with a review bonus only
- Reviewing Project Application - Instructions
- META: Let's build ventral.org on official Drupal infrastructure
- Many modules are waiting approval.
- Not a a serious applicant?
- Denver Project Application Sprint Brainstorming session - Time to start planning
- Third party API's or Native Jquery API?
- How much should we demand of the applicants?
- Bug squad feature
- Project Apps State of the Union
- Refactoring of other Drupal 6 module which is not on d.o
- Shared accounts?
- Too short?
- question about a code review for the admins here
- Getting code sniffer to work in eclipse with .module, .inc, and .info files
- Another question on a review
- Question about doing a code review
- Encouraging applicants to review other projects
- Applicants with Multiple Applications
- "Lost" Contributors
- How shall we handle non-typical/highly advanced applications?
- New 'Project Applications' d.o development environment
- How to seach text from .txt file
- How much code do we need to approve a user?
- Applicants' motivation analysis and possible conclusions
- Code standards review is a incredibly difficult - http://ventral.org/pareview should be set as the standard
- Developer / Project Manager of Web Solutions | University of Arizona
- PAReview.sh - online service
- Trouble with newlines
- Klausi in Community Spotlight on front page
- Do we approve people with "Features" only projects?
- Project Application Security Review Mentoring
- things to automate in the code review
- Increasing efficiency in manual code reviews
- Feedback for reviewers?
- Just 100 more
- Meta Discussion: Project Application Process Revamp
- Reply before even looking at the code?
- What are the most common problems you spot in applications?
- Kicking it old Skool!
- Most active commenters in post git process in the last 30 days, 90 days, all time
- Project Applications which require Core edits - Is this a blocker?
- Evolution of the Project Application Process - 'Coles Notes' summary
- Evolution of the Project Application Process (Part 4) - Sanity Check - Wait a Minute Here ...
- Evolution of the Project Application Process (Part 3) - The Proposal
- Evolution of the Project Application Process (Part 2) - Where the Existing Process Breaks
- Evolution of the Project Application Process (Part 1) - Today's Project Application Process
- Best practice: code review in application issue or projects sandbox?
- Automated Coder Reviews for New Project Applications - Planning/Development
- Current Applications by Age (as of June 25th)
- 'Request a Second Opinion' Here!
- Get a second opinion
- Solutions (got tired of looking at that title... thanks sreynen)
- Automation of various Code Review steps
- Module duplication: did I handle it right?
- What happens to project applications that are seemingly abandoned?
- Related Initiatives Package
- Do you support the use of incentives, such as expedited applications, to encourage more people to participate in the process?
- Do you support the use of 'active' status to differentiate applications in the screening and technical review stages?
- Do you support the use of a two stage process (screening and technical review) to facilitate using multiple people for reviews?
- Do you support the idea of using multiple people to do code reviews?
- Code Review Group: Major Thrusts/Initiatives
- Expedited Applications
- New recruits and splitting up reviews
- Proposal for Addition of Component Status to Project Application Issue pages
- Draft 01 by DrupalCon London
- Proposed Code Review Checklist (With Gates)
- First theme review
- Clearing the queue: Official Drupal 'Review a Module' Week
- Discussion regarding Module Duplication in the Code Review Process (and the 'Devil's Advocate' viewpoint).
- Duplication is bad, but what is it?
- Theme Autoswitch
- Reviewing themes
- Pieces of the queue (ubercart, views, theme)
- Review Process - Basic Steps
- How to hold a Code Review Sprint
- Code Review Review and Meetings
- Code Process Solutions
- Code Review Issues and Problems
- Code Review Data Collecting
- Code Review Leadership
- Code Review Complaints
- Reviewee's Stories
- Code Review Process Goals
- Code Review Administrators
- Code Reviewers
- Module Approval Process will KILL Drupal.
- Code Review Sprint at DrupalCon Chicago 2011?
- Issues requesting Peer Review
- Web Developer (PHP, Ajax , Expert in Drupal , Adobe photoshop) | ASM Consulting
- Drupal Developer | iVedha
- Combine Peer Review and Code Review groups
- 1 of 2
- ››
Subscribe with RSS 