Feature #6860

Conduct a usability testing session on Tails at NUMA

Added by sajolida 2014-03-06 17:51:44 . Updated 2014-10-17 09:17:20 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2014-03-06
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

https://tails.boum.org/blueprint/usability_testing/

Starter:
0
Affected tool:
Deliverable for:

Description

People from Silicon Sentier proposed to conduct a usability testing session on Tails.

The starting point is the fact that FOSS projects too often have poor usability
and are not attractive to potential users. They want to play a role in fixing
this, by building a bridge between the designers, graphics artists, and UI
experts community on the one hand, and the FOSS people on the other hand.

That would be in late May so, it would make more sense to do it on Tails Wheezy even if it will be before its official release.

Subtasks

Feature #6862: List the blockers to have a Tails Wheezy ISO for usability testing Resolved

0
Feature #6864: Finalize a lists of test to be conducted during the usability testing session Resolved

0
Feature #7415: Report on the first usability testing session at NUMA Resolved

100

History

#1 Updated by sajolida 2014-03-06 17:54:00

  • Tracker changed from Bug to Feature

#2 Updated by sajolida 2014-03-06 17:55:51

  • Description updated

#3 Updated by sajolida 2014-03-06 17:56:51

  • Blueprint set to https://tails.boum.org/blueprint/usability_study/

#4 Updated by sajolida 2014-03-06 17:58:17

  • Type of work changed from User interface design to Test

#5 Updated by intrigeri 2014-03-08 11:00:10

  • Blueprint changed from https://tails.boum.org/blueprint/usability_study/ to https://tails.boum.org/blueprint/usability_testing/

#6 Updated by intrigeri 2014-03-08 11:01:26

  • Description updated

#7 Updated by sajolida 2014-06-16 12:06:37

  • Subject changed from Conduct a usability testing session on Tails at Silicon Sentier to Conduct a usability testing session on Tails at NUMA

#8 Updated by BitingBird 2014-07-03 12:40:32

  • Status changed from Confirmed to Fix committed
  • QA Check set to Pass

#9 Updated by BitingBird 2014-07-03 12:41:26

I can’t mark this as resolved, any idea why ?

#10 Updated by intrigeri 2014-07-03 15:22:04

  • blocks deleted (Feature #5685: Document how to install new software)

#11 Updated by intrigeri 2014-07-03 15:22:07

  • blocks deleted (Feature #5636: Document how to access internal hard disks)

#12 Updated by intrigeri 2014-07-03 15:23:07

> I can’t mark this as resolved, any idea why ?

Because it’s marked as being blocked by issues that haven’t been resolved yet. I’ve just removed these obsolete relationships.

Still, I’d like to make sure the outcome of the session that happened is now tracked properly as tickets, before seeing this ticket closed.

#13 Updated by sycamoreone 2014-07-26 20:02:04

intrigeri wrote:
> Still, I’d like to make sure the outcome of the session
> that happened is now tracked properly as tickets,
> before seeing this ticket closed.

https://mailman.boum.org/pipermail/tails-dev/2014-June/006200.html
contains a list of the tickets resulting from the NUMA session.

I will assign this ticket to u, who will know if this list is complete.

#14 Updated by BitingBird 2014-10-17 08:48:01

  • Status changed from Fix committed to Resolved

The children tasks have been completed, closing.

#15 Updated by intrigeri 2014-10-17 09:17:20

> The children tasks have been completed, closing.

It might be that the next steps haven’t been pushed to Redmine yet.
But oh well, if the UX folks need this ticket and want to use Redmine more, they can still reopen it.