action #179963
closed
[tools][organisational] Team split - split backlog queries
Added by okurz 20 days ago.
Updated 12 days ago.
Description
Motivation¶
With two teams "dev" and "infra" we should also split backlogs as referenced on team pages and backlog status view.
Acceptance Criteria¶
- AC1: primary entry points on team wiki and status page are team specific
Suggestions¶
- Copied from action #167884: [tools][organisational] Reconsider team composition size:S added
- Copied to action #179966: [tools][organisational] Team split - additional scrum master size:S added
- Target version changed from Tools - Next to Ready
- Status changed from New to In Progress
- Assignee set to okurz
- Status changed from In Progress to Feedback
- Copied to action #180764: [tools][organisational] Team split - clear definition of infra and dev scopes size:S added
some ideas from a collab session
- dev should be about community
- infra is "SUSE internal"
maybe "openQA" is not such a bad name for "dev" :) For some o3 would better belong to infra. Why I mentioned o3 mostly refers to "everything above the base OS layer" so something like continous deployment of os-autoinst+openQA and monitoring the openQA instance itself. Not "kernel upgrades of the OS". "qem-dashboard" is a free software project and "development" and might fit better in dev however okurz argues that most of the work in that domain is understanding the very SUSE specific requirements and interconnections with qem-bot, smelt, IBS, OSD, and alike. We can add a "disclaimer" and also mention that in doubt we all collaborate :)
- Status changed from Feedback to Resolved
Also available in: Atom
PDF