Feature #8777

Update screenshots on the website if relevant

Added by sajolida 2015-01-22 18:56:53 . Updated 2015-03-23 02:03:12 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.3.1
Start date:
2015-01-22
Due date:
% Done:

100%

Feature Branch:
feature/8777-update-screenshots
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

If we change the background color, it would be nice to go quickly through the screenshots we have on our website and update their background color using GIMP.

Files

a.fw.png (193331 B) pablonatalino, 2015-01-23 18:15:55

Subtasks

Related issues

Blocked by Tails - Feature #8796: Consider using the purple of the logo as background color Rejected 2015-01-25

History

#1 Updated by pablonatalino 2015-01-22 22:05:03

you speak of blue tails screen? I think the best would be a purple screen with tails logo, I could help by making a model? tell me the size of the resolution necessary.

#2 Updated by pablonatalino 2015-01-23 18:16:04

#3 Updated by sajolida 2015-01-23 21:47:28

Thanks for offering yourself. Changing the background color is ticket Feature #7963. We’ve decided to keep the same blue color but reduce its brightness and saturation to make it less hurting to the eyes.

I don’t want to propose a more profound change as this might raise tons of debates and very subjectives point of views that I’m not willing to moderate :)

#4 Updated by sajolida 2015-01-25 11:45:44

Pablo: I thought again about your proposal (since I personnally like), and create a ticket to discuss this: Feature #8796. I’ll add this to the agenda of the next monthly meeting (February 3rd) and we will still have time to implement that in time for 1.3 if we finally go this way.

#5 Updated by sajolida 2015-01-25 18:08:19

  • blocked by Feature #8796: Consider using the purple of the logo as background color added

#6 Updated by sajolida 2015-02-05 21:12:18

  • Target version set to Tails_1.3

#7 Updated by intrigeri 2015-02-10 13:55:33

  • Priority changed from Normal to Elevated

Ping? It’s a bit weird that the parent ticket is marked fix committed, while it has a subtask without progress yet. No big deal anyway, can be done after the freeze IMO. Worst case, unparent it, postpone the milestone, and retitle accordingly.

#8 Updated by Tails 2015-02-19 15:34:22

  • Status changed from Confirmed to In Progress

Applied in changeset commit:b6e198322075913ee836323a69dce645ef6d387f.

#9 Updated by sajolida 2015-02-19 15:34:48

  • Assignee deleted (sajolida)
  • Priority changed from Elevated to Normal
  • QA Check set to Ready for QA

#10 Updated by intrigeri 2015-02-24 23:10:07

  • Assignee set to anonym
  • Priority changed from Normal to Elevated
  • Target version changed from Tails_1.3 to Tails_1.3.2
  • % Done changed from 0 to 50
  • Feature Branch set to feature/8777-update-screenshots

Apparently this was missed during the 1.3 cycle => raising priority and explicitly assigning to the RM.

#11 Updated by Tails 2015-02-25 13:34:25

Applied in changeset commit:dcde87817c7a94af7fddfb5477a8a060c79caadb.

#12 Updated by Tails 2015-03-19 13:29:36

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:0a1f679b4a873b9fd21d677dc357b83325b54dbb.

#13 Updated by anonym 2015-03-19 13:30:02

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#14 Updated by BitingBird 2015-03-22 11:52:14

  • Target version changed from Tails_1.3.2 to Tails_1.3.1

#15 Updated by BitingBird 2015-03-23 02:03:12

  • Status changed from Fix committed to Resolved