action #179963
closed[tools][organisational] Team split - split backlog queries
0%
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¶
- Review and update https://progress.opensuse.org/projects/qa/wiki/Tools#How-we-work as applicable
- Change on https://github.com/os-autoinst/qa-tools-backlog-assistant
Updated by okurz about 2 months ago
- Copied from action #167884: [tools][organisational] Reconsider team composition size:S added
Updated by okurz about 2 months ago
- Copied to action #179966: [tools][organisational] Team split - additional scrum master size:S added
Updated by okurz about 2 months ago
https://github.com/os-autoinst/qa-tools-backlog-assistant/pull/51 as a first step to mention dev+infra backlogs.
Updated by okurz about 2 months ago
- Status changed from New to In Progress
- Assignee set to okurz
Updated by okurz about 2 months ago
- Status changed from In Progress to Feedback
I added an explanation of individual teams and their backlogs on https://progress.opensuse.org/projects/qa/wiki/Tools/diff?utf8=%E2%9C%93&commit=View+differences&version=550&version_from=549
Now waiting for https://github.com/os-autoinst/qa-tools-backlog-assistant/pull/51
Updated by livdywan about 2 months ago
Now waiting for https://github.com/os-autoinst/qa-tools-backlog-assistant/pull/51
Merged.
Updated by livdywan about 2 months ago
- Copied to action #180764: [tools][organisational] Team split - clear definition of infra and dev scopes size:S added
Updated by okurz about 2 months ago ยท Edited
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 :)
Updated by okurz about 2 months ago
- Status changed from Feedback to Resolved
I hope I managed to incorporate the necessary changes into https://progress.opensuse.org/projects/qa/wiki/Tools#How-we-work for now