Hey Gael On Fri, Mar 19, 2021 at 12:00 PM Gaƫl Chamoulaud <gchamoul@redhat.com> wrote:
Ladies and Gentlemen,
First, thanks for your votes!
With the agreement of Marios, I've added David as part of the tripleo-core group and his voting rights will be exercised only on the following repositories:
thanks for adding David I can see he is in the tripleo-core group members list at [1].
- tripleo-validations - validations-common - validations-libs - python-tripleoclient (only on VF related patches touching the tripleo_validator.py CLI Code)
However, it would be great to create a dedicated core group for the Validation Framework team including those repositories. And thus being more compliant with what we do with others TripleO Teams. Marios, any thoughts?
As briefly discussed this morning on #tripleo yeah I think it makes sense. I just did some digging about that so a couple of thoughts; these repos are under tripleo governance [2] so first thing so we can create a new group and add the tripleo-core group as members. I'm not sure how we create a new tripleo-validation (or whatever name) gerrit group yet though so there's that ;)... I couldn't quickly find info about that in hound [3] but I'm sure we can work that out _eventually_ Then I think we need to add a file like that [4] for the validation repos to set the access for the new group. Let's see if there are any other thoughts or comments about that proposal before we proceed anyway, regards, marios [1] https://review.opendev.org/admin/groups/0319cee8020840a3016f46359b076fa6b6ea... [2] https://opendev.org/openstack/governance/src/commit/98614886e2a93c5981be4fc9... [3] https://codesearch.opendev.org/?q=tripleo-core&i=nope&files=&excludeFiles=&repos= [4] https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/o...