Open Stack

On 08/03/18 12:57, Doug Hellmann wrote:
> Why would the repos be owned by anyone other than the original project
> team?

A few reasons I think it makes sense in this instance:

* Not every set of trademark tests will necessarily belong to a single 
project. Tempest itself is an example of this - in fact that's basically 
how the QA program came to exist. Vertical-specific trademark programs 
are another example that we anticipate in the future.
* Allowing projects to create their own repos means that there's no 
co-ordination point to ensure e.g. a consistent naming scheme. Amongst 
other things, this could potentially cause confusion about which plugins 
are trademark-candidates-only and which are just regular tempest plugins.
* By registering trademark plugins all in one place it makes it easy to 
determine how many there are, which plugins exist (e.g. are there any 
extant plugins that are not referenced by refstack? This is a question 
you can answer in 20s if they're all registered in the same place.)
* The goal is for maintenance of these plugins to be a collaborative 
effort by the project team, the QA team, and RefStack. If the first step 
for a project establishing a trademark test plugin involves the project 
team reaching out to the QA team then that's a good foot to start on. If 
teams create the repos in their own projects and fly under QA's radar 
then QA folks might not even be aware that they've become core reviewers 
on the repo.


I guess we have examples of both models in the community... e.g. 
puppet-openstack vs. Horizon plugins. I wonder if there are any lessons 
we can draw on to see which works better, and when.

cheers,
Zane.