Re: [openstack-dev] [trove] Request for transparent Gerrit approval process

2014-05-06 Thread Morgan Jones
I've been thinking about this a bit, and had some ideas. Take the following as points for thought, rather than my saying this is what we should do. How about each Trove participant be assigned a core mentor. This way, each non-core person knows who they can ask for information about how

[openstack-dev] [trove] Request for transparent Gerrit approval process

2014-05-05 Thread Lowery, Mathew
As a non-core, I would like to understand the process by which core prioritizes Gerrit changes. I'd also like to know any specific criteria used for approval. If such a process was transparent and followed consistently, wouldn't that eliminate the need for Hey core, can you review change? in

Re: [openstack-dev] [trove] Request for transparent Gerrit approval process

2014-05-05 Thread Nikhil Manchanda
Hi Mat: Some answers, and my perspective, are inline: Lowery, Mathew writes: As a non-core, I would like to understand the process by which core prioritizes Gerrit changes. I'm not aware of any standard process used by all core reviewers to prioritize reviewing changes in Gerrit. My