Using gitlab issues to track and document UX work


#1

Hi all,

It’s taken me a little longer than I’d like to admit to realise that we need some way to track UX work - why did we do what we did, how did we get where we are.

After a discussion with a few people, I’d like to propose using the Gitlab issues tool attached to the UX wiki.

Initially I was suggesting using the Github issues for it, as after all the UX work will (hopefully) end up in lovingly crafted code.

But smarter people than me suggested we use the UX wiki.

I’ve started by adding the SecureDrop user workflow research I plan doing this month. This work is to inform the design of the Qubes SecureDrop client.

I’d like to hear thoughts on using the Gitlab tracker, what needs to be included, or what not to include.