action #167884
closed
[tools][organisational] Reconsider team composition size:S
Added by okurz 7 months ago.
Updated 15 days ago.
Description
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:
- dev: openQA - upstream os-autoinst+openQA and o3
- infra: 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
- Target version changed from Ready to Tools - Next
- Subject changed from [tools][organisational] Reconsider team composition to [tools][organisational] Reconsider team composition size:S
- Description updated (diff)
- Status changed from New to Workable
- Description updated (diff)
- Description updated (diff)
- Parent task set to #174442
- Target version changed from Tools - Next to Ready
- Copied to action #179963: [tools][organisational] Team split - split backlog queries added
https://suse.slack.com/archives/C02AJ1E568M/p1743764378690729
I would like to drive https://progress.opensuse.org/issues/167884 forward. For this I have some questions to you:
- Name of teams: How about ""QE Tools dev" and "QE tools infra" which can be abbreviated to "QE dev" and "QE infra" or just "dev" and "infra" as long as it has a unique meaning like in the same way we use it in daily communication already
- The scope for each time as proposed in https://progress.opensuse.org/issues/167884#Motivation is
- dev: upstream os-autoinst+openQA and o3
- infra: OSD, qem-dashboard, hardware, compliance, etc.
ok with that?
- Next steps would be separate SMs, separate backlogs as referenced on https://progress.opensuse.org/projects/qa/wiki/Tools, potentially also separate chat rooms, separate meeting rooms, separate team wiki, separate Slack handles replacing
(at)qa-tools
, separate mailing lists, separate roster on https://confluence.suse.com/display/qasle/QE+squads+-+structure, maybe even separate roster on https://progress.opensuse.org/projects/qa/wiki/Tools#Team, WDYT?
- Status changed from Workable to Feedback
- Description updated (diff)
- Status changed from Feedback to Blocked
Let's block on specific tasks as the confusion between the 3 tickets is getting unnecessarily confusing and annoying.
Specifically #179966
- Status changed from Blocked to Resolved
Let me make it more easy by setting this to "resolved". I see AC1 as covered as over the past months nobody challenged the existing scope definition for the individual teams. Already implementing extension to the wiki and individual backlogs in #179963
Also available in: Atom
PDF