See below for the minutes from today's Workstation WG meeting.
Switch from Pagure to Taiga - https://pagure.io/fedora-workstation/issue/112
- Neal likes the kanban board. The discussions on Taiga aren't great
- Neal: there's a Pagure/Taiga extension, so you can have a board in Taiga
and still have discussions in Pagure.
- Matthias is not in favour of syncing between two tools
- Langdon - issue trackers aren't really intended for discussion. He has
struggled with discussion on Taiga in the past. Considers Pagure being good
at issue handling to be a "trap," prefers discussion in meetings.
- Neal thinks having Pagure to allow reporting issues to the working group
is nice. Doesn't want to host discussions on Taiga.
- Langdon suggests using both tools, Taiga for kanban and Pagure for
external parties to report issues, and not syncing them. Taiga better for
assigning issues as work.
- Allan thinks Pagure is not nice for discussions, either.
- Neal: GitLab's kanban is not good. Pagure is a better external reporting
tool. Taiga is better for internal organization.
- Chris: no strong opinion.
- Kalev: most of Fedora uses Pagure, switching to something else will
cause difficulty for other Fedora members used to Pagure.
- Allan: but aren't other teams migrating to Taiga?
- Langdon: Council wants to surface to the public what activity is
occuring in different projects. Taiga makes this easy. But Pagure works
better for FESCo, which is not a working body, it just approves issues.
Hence it doesn't need the kanban. This is why some Fedora teams are slowly
moving to Taiga but others are not. Workstation WG should pick whichever
tool works better for it; there is no mass migration in progress.
- Allan senses hesitation to move away from Pagure. Proposes vote. Option
one is complete migration to Taiga. Option two is to enable Taiga extension
- Michael suggests enabling Pagure's Taiga extension would be low-cost;
people who don't like Taiga don't need to look at it.
- Matthias: whether this works depends on whether the chair we select
likes to use it.
- Langdon: we can do a pilot/trial
- VOTE 1: try Taiga for a while in addition to Pagure.
- +1 Allan, +1 Michael +1 Neal, +1 Chris, +1 Jens, -1 Matthias, -1 Kalev,
Abstain: Langdon, Result: (+5,1,-2)
- VOTE 2: pilot Taiga for a while, without Pagure.
- +1 Allan, -1 Michael -1 Neal, +1 Matthias, -1 Kalev, -1 Jens, -1 Chris,
Abstain: Langon, Result: (+2,1,-5)
- Approved: try Taiga alongside Pagure
- Action: Langdon to find out how to set up Taiga
- Done: https://teams.fedoraproject.org/project/workstation-wg/timeline
Appoint a permanent chair(s) -
- Discussion: should we have a chair and vice-chair, or two equal
- Chris likes co-chair model. Also suggests having individual chair and
vice-chair assigned to WG subgroups, like the encryption subgroup.
- Michael and Neal also support separate chair and vice-chair.
- Discussion: should we have appointed positions, or a rotation?
- Langdon just doesn't want the same person in charge for a long time,
but doesn't think a rotation system is necessary for that.
- Consensus: appointed (elected) chair and vice-chair, terms coinciding
with Fedora release cycle.
- Suggestion: collect volunteers this week and appoint in the next meeting