Hello! On Mon, May 18, 2020 at 01:20:07PM +0200, Marco Martin wrote: > Bhushan: We have few questions at this point > - Do we want to keep issues enabled and use them for "tasks"? > - Do we want to have separate "tasks" boards under invent.kde.org/teams ? > Nico: vote for 2 > Marco: vote for 2 > Bhushan: Also we sysadmins will be "linking" bugzilla to projects in > future: https://invent.kde.org/pim/korganizer see for example > Arjen: I'd keep tasks linked to the actual projects, imo that makes > them more likely to actually be seen otherwise there's yet another > thing to keep track of > Bhushan: Agree
Before we make this decision I think we need to weigh our options and how phabricator boards have served us as a Plasma team. Currently for "Plasma" we have one main workboard: https://phabricator.kde.org/project/board/35/ And several, sub-boards(is it even word?), - KWin[*] - Plasma on wayland - Plasma mediacenter[*][@] - Plasma Accessibility - Plasma: Convergence - Plasma: KCM Redesign[*] - Plasma: Workspaces[*] - Start-up improvements - Plasma Mobile In general, all marked with * are associated with some specific repository or repositories. Now translating this to Gitlab this two options can be translated as, ---- # Option 1: https://invent.kde.org/teams/plasma/ (group) And then several projects under it, - KWin - plasma-wayland - plasma-accessibility - plasma-convergence - plasma-kcm-redesign - plasma-workspaces - plasma-startup - plasma-mobile ---- # Option 2: https://invent.kde.org/plasma (group) We already have a repositories for most projects, idea is each task goes into some repository, and IF for worst case we can not find a repository for change, we put the issue in one dummy repository called "tasks" ---- I will send my opinion of which option is better IMO in separate email, to keep this email as overview of options. -- Bhushan Shah http://blog.bshah.in IRC Nick : bshah on Freenode GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D
signature.asc
Description: PGP signature
