On Fri, Jun 26, 2015 at 1:21 PM, Clint Byrum <cl...@fewbar.com> wrote: > Excerpts from Gregory Haynes's message of 2015-06-26 08:17:36 -0700: >> Hello TripleOers, >> >> At the last mid-cycle we briefly discussed whether we should have >> separate groups for tripleo and DIB core and decided it wasn't >> necessary. I would like to revisit that topic. >> >> It seems clear to me that we have some existing tripleo cores who are >> becoming less familiar with the tripleo project as a whole but are >> highly active in the DIB project. We also have new contributors who are >> fairly active in the DIB project but are not active in the other tripleo >> projects. I would really like a path where new contributors like this >> can become core on DIB but that isn't really an option right now with >> one core group for both tripleo and DIB. >> >> I'd like to propose we make a new gerrit group for dib-core and add the >> existing tripleo-core members to it (note: this is different than adding >> tripleo-core as a member group of dib-core, which is an alternative). >> This would mean that new tripleo cores would not automatically be DIB >> cores, and new DIB cores would not automatically be tripleo cores. > > Why wouldn't we just make dib-core a sub-team for people not familiar > with the broader TripleO effort, and just add tripleo-core to dib-core?
I would need to double check, but I think this is what we already have. diskimage-builder-core includes the group tripleo-core in gerrit. In project-config, diskimage-builder-core is what has +2 on diskimage-builder. It also has +2 on tripleo-heat-templates and tripleo-image-elements as well though (since this was it's original purpose), so we could remove those. We should also probably add +2 on dib-utils for it as well. Ok, so I basically just double checked trying to write this :). Either way, I agree it makes sense to have the ability to give a set of folks +2 on dib, and not all the tripleo repos in the process, so that dib is able to grow it's team of core reviewers. -- -- James Slagle -- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
