Code Review Processes Used In Open Source Projects

Project 1: vue

vue is licensed under the MIT License.
https://github.com/vuejs/vue/pull/10531

In this case, there are 3 participants involved in the review. One is the contributor, one is the reviewer, who is a member of vuejs. The last one is a robot. It took 2 days to finish the review. Actually, almost every request has been reviewed and finished in 2 days. I guess a standard survey before the request is help to improve the efficiency.
It fixed link to point to ModuleOptions lines. Contributor changes
js#L38-L45 to js#L47-L59. One member of  vuejs reviewed the change and approved it. After merged the change, the robot gave the contributor a thankful reply, also the reviewer.



Project 2: octant

octant is licensed under the Apache License 2.0.
https://github.com/vmware/octant/pull/298

In this case, there are 4 participants involved in the review. It including 2 reviewers, 1 contributor and 1 VMware CLA Bot. It took 2 days to finish the review. There are some discussion between the contributor and the reviewers. Also the bot added the cla-not-required label. 
It move namespaces which are overview specific to top level. Contributor basically remove modules/overview/ from the code. After it has been approved, another reviewer make a suggestion and the contributor made another change.

  • How many people were involved in the review
  • The role of those people in the community and project
  • How long the whole review took
  • How responsive the participants were to updates in the process
  • What kinds of issues were discussed
  • How issues were resolved

Comments

Popular posts from this blog

Project - Stage 0.2 - Background Learning

Project - Stage 0.1 - Project Selection

Hacktoberfest - My 1st