QA (public)

Motivation¶

The SUSE QE Tools team has recently grown to 10 members which is great but also becoming a challenge to be an efficient team. We already have a soft split into the scopes of "dev" and "infra" which helps. I would like to go the next step and either have us focus more following the existing definitions or redefine. I was thinking of two possible teams:

• openQA - upstream os-autoinst+openQA and o3
• QE infrastructure - OSD, qem-dashboard, hardware, compliance, etc.

Acceptance Criteria¶

• AC1: The team agrees on how to best split or organize different topics within the team

Suggestions¶

• Consider the implications of two teams with different projects
• Propose more explicit focus areas
  • It's good for any team member to pick a topic, for example
    • web UI
    • production infrastructure
    • test coverage
• Come up with one or more proposals and present it to the team