On 09/10/2015 10:06 AM, James Slagle wrote:
TripleO has added a few new repositories, one of which is
python-tripleoclient, the former python-rdomanager-oscplugin.
With the additional repositories, there is an additional review burden
on our core reviewers. There is also the fact that folks who have been
working on the client code for a while when it was only part of RDO
are not TripleO core reviewers.
I think we could help with the additional burden of reviews if we made
two of those people core on python-tripleoclient and tripleo-common
Specifically, the folks I'm proposing are:
Brad P. Crochet <b...@redhat.com>
Dougal Matthews <dou...@redhat.com>
+1 to both. I've seen a lot of Dougal's reviews and his Python knowledge
The options I see are:
- keep just 1 tripleo acl, and add additional folks there, with a good
faith agreement not to +/-2,+A code that is not from the 2 client
+1 to this. I feel like it encourages cross pollination into other
tripleo repos (we could use the eyes on THT) without having to jump
through extra hoops as their involvement with them increases.
- create a new gerrit acl in project-config for just these 2 client
repos, and add folks there as needed. the new acl would also contain
the existing acl for tripleo core reviewers
- neither of the above options - don't add these individuals to any
TripleO core team at this time.
The first is what was more or less done when Tuskar was brought under
the TripleO umbrella to avoid splitting the core teams, and it's the
option I'd prefer.
TripleO cores, please reply here with your vote from the above
options. Or, if you have other ideas, you can share those as well :)
OpenStack Development Mailing List (not for usage questions)