I noticed that the Peer Review group is being revitalized and the mission expandedand there is a movement for a more structured peer review of modules program, which is awesome.
So, I would like to propose that we combine the Code Review group I recently started and the Peer Review group, as the Code Review is more focused on CVS Applications and that is really just a subset of the focus of code peer reviewing given a slight expansion in the mission of the Peer Review group. I think this will be more apparent once the migration to Git happens and we will not be reviewing for CVS access but simply release access.
Logistically, I don't care what the name is or if it needs to change, but an open to suggestions. Also, it makes more sense to move the discussions from Code Review to this group.
Please let me know your thoughts in the next few weeks.
Comments
This sounds like a good idea.
This sounds like a good idea. The idea of Peer Review is to encourage open sharing and collaboration. My only concern, and it's a slight one but I bring it up to see if anyone else feels this way, is that the gatekeeper aspect of CVS/Git applications might get in the way of open sharing of ideas. But an overly balkanized discussion is not great, either.
Perhaps more will sound off here on the proposal to merge these groups.
PINGV | Strategy • Design • Drupal Development
Peer Review
That's great! My concern originally was the tie to CVS apps, but now I simply like the name Peer Review more because i think finding requests for UX review, accessibility review, etc. should use the same approach.
Here's how issues can be found: http://groups.drupal.org/node/125424
Perhaps crosslinking between the groups is enough? I don't think posting to the groups asking for review is a good approach, as above i think it should be done in the issue queues, so i think we should be redesigning the peer review group to clearly direct people how to request reviews, and how to do reviews. The wiki started by Bill Fitgerald is the roadmap. Perhaps the code review group might still be a good place for code reviewers to discuss procedures etc?
benjamin, agaric
combine while new
Hi Benjamin. The main reason I would like to address this now is because the Code Review group is pretty new, so instead of investing the separate resource, it would be easy to push them together now.
I do agree that we need to be very clear about where code reviews actually happen.
--
zzolo