Open Stack

On 05/13/2013 08:25 PM, Jay Pipes wrote:
> On 05/13/2013 06:44 PM, Sam Danes wrote:
>> I agree that Tempest core (or any OpenStack core) is meant to and should
>> be a fluid thing where members drop in and out based on activity.
>>
>> That having been said, I also agree with what Attila said in that people
>> that are totally inactive, certainly should be dropped. Beyond that
>> there should be an agreed metric for how someone is added or dropped and
>> when it is changed.
>>
>> A question for the group too. There seem to be several Quality related
>> groups out there for OpenStack. There is OpenStack QA, OpenStack QA
>> Core, Tempest Drivers and tempest-core. I assume OpenStack QA is the
>> general QA related group. tempest-core is the Gerrit group that is
>> configured as core review from openstack-infra (and I presume membership
>> in this group is what is being discussed).
>>
>> What then are OpenStack QA Core and Tempest Drivers? I apologize if I'm
>> missing something obvious there.
>
> The Tempest Drivers team has management abilities on blueprints
> (approval and targeting). The OpenStack QA core team I *think* is
> actually the team that we're talking about here... it's the team that
> gets +2 rights on reviews. The tempest-core team I believe should be
> removed?

OpenStack QA Core maps to tempest-core when in gerrit. Naming legacy. 
That is the group we are talking about.

As Jay said, Tempest drivers are the folks that have control over 
blueprint management (prioritization and acceptance).

	-Sean

-- 
Sean Dague
http://dague.net