[openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

Sean McGinnis sean.mcginnis at gmx.com
Tue Jun 2 21:29:50 UTC 2015

I like this idea. I agree, as things grow it is probably easier to find 
folks that know certain areas a project rather than the full scope.

This could be a good way to handle the load and delegate some pieces 
(such as driver reviews) to a different set of people.

On 06/02/2015 04:24 PM, Boris Pavlovic wrote:
> Hi stackers,
> *Issue*
> *-------*
> Projects are becoming bigger and bigger overtime.
> More and more people would like to contribute code and usually core 
> reviewers
> team can't scale enough. It's very hard to find people that understand 
> full project and have enough time to do code reviews. As a result team 
> is very small under heavy load and many maintainers just get burned out.
> We have to solve this issue to move forward.
> *Idea*
> *------*
> Let's introduce subsystems cores.
> Really it's hard to find cores that understand whole project, but it's 
> quite simple to find people that can maintain subsystems of project.
> *How To*
> *-----------*
> *
> *
> Gerrit is not so simple as it looks and it has really neat features ;)
> For example we can write own rules about who can put +2 and merge 
> patch based on changes files.
> We can make special "subdirectory core" ACL group.
> People from such ACL group will be able to merge changes that touch 
> only files from some specific subdirs.
> As a result with proper organization of directories in project we can 
> scale up review process without losing quality.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150602/d667316f/attachment.html>

More information about the OpenStack-dev mailing list