Tails

#2 Updated by sajolida 2017-04-07 08:32:42

• blocks Feature #12431: UX core work 2017Q2 added

#3 Updated by sajolida 2017-04-14 11:00:11

• Target version deleted (Tails_2.12)

#4 Updated by sajolida 2017-07-05 19:06:36

• blocked by deleted (Feature #12431: UX core work 2017Q2)

#5 Updated by sajolida 2017-07-05 19:06:42

• blocks Feature #13424: Core work 2017Q3: User experience added

#6 Updated by sajolida 2017-10-03 07:10:29

• blocks Feature #14761: Core work 2017Q4 → 2018Q1: User experience added

#7 Updated by sajolida 2017-10-03 07:10:34

• blocked by deleted (Feature #13424: Core work 2017Q3: User experience)

#8 Updated by sajolida 2017-10-24 18:58:46

• Assignee changed from sajolida to intrigeri
• QA Check set to Ready for QA

Sorry it took me so long but I’m really not inspired by this one.

I prepared something in contrib/12416-describing-core-ux…

#9 Updated by intrigeri 2017-10-29 09:19:26

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10
• Feature Branch set to contrib/12416-describing-core-ux

#10 Updated by intrigeri 2017-10-29 09:32:52

• Assignee changed from intrigeri to sajolida
• QA Check changed from Ready for QA to Dev Needed

Looks mostly good (modulo it shall be added to the list of core work pages in contribute.mdwn).

I have one concern though. It’s about the fact you’re limiting the scope to what’s “related to the work of the [[Foundations Team]]”, which does not match what you’ve been classifying under UX core work on Redmine so far (which I guess is what you clock in your UX core work category) e.g.:

• Feature #8860, Bug #12436, Feature #11493 and Feature #8859 are about UX improvements that are follow-ups to a past project
• Bug #14736 and Feature #14734 are about researching UX bugs identified after a past project was delivered
• Bug #5466 and Bug #7904 are misc. UX improvements

I think none of these are related to the work of the Foundations Team. So I think either you need to make the scope of the UX work formally broader, or you need to adjust what you put into this category (be it on Redmine or in your clocking) so that it fits into the scope you choose. As you wish :)

#11 Updated by sajolida 2017-12-19 23:25:04

• Assignee changed from sajolida to intrigeri
• QA Check changed from Dev Needed to Ready for QA

I made the scope broader with 9e3e203ae8. Please have a look again!

#12 Updated by intrigeri 2017-12-22 08:01:56

• Status changed from In Progress to Resolved
• Assignee deleted (intrigeri)
• Target version set to Tails_3.5
• % Done changed from 10 to 100
• QA Check changed from Ready for QA to Pass

Thanks, merged and then handled “it shall be added to the list of core work pages in contribute.mdwn” from my previous review myself, to save a roundtrip and paperwork.