Project

General

Profile

Feature #16536

Feature #9814: Clarify what Tails is and what makes it so awesome

Rewrite our About page (aka. "How Tails work")

Added by sajolida 7 months ago. Updated 20 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/06/2019
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Starter:
Affected tool:

Description

As per the plans we made with Simply Secure, it should be the continuation of the shorter explanation on the homepage and tell people how Tails work and go more in depth on its properties.


Related issues

Blocks Tails - Feature #16538: Have illustrations to support our explanation of Tails In Progress 03/06/2019

History

#1 Updated by sajolida 7 months ago

I'll try to have something ready to test with people at the IFF.

#2 Updated by sajolida 7 months ago

  • Blocks Feature #16538: Have illustrations to support our explanation of Tails added

#3 Updated by sajolida 7 months ago

  • Blocks Feature #16080: Core work 2018Q4 → 2019Q2: User experience added

#4 Updated by sajolida 6 months ago

  • Status changed from Confirmed to In Progress
  • Blueprint set to https://tails.boum.org/blueprint/explain_tails/about/

I have a draft now. Uuuh yeah!

Next step is to format it very roughly using Bootstrap.

#5 Updated by sajolida 6 months ago

  • Target version changed from Tails_3.13 to Tails_3.14

#6 Updated by CyrilBrulebois 4 months ago

  • Target version changed from Tails_3.14 to Tails_3.15

#7 Updated by sajolida 4 months ago

  • Blocks deleted (Feature #16080: Core work 2018Q4 → 2019Q2: User experience)

#8 Updated by CyrilBrulebois 2 months ago

  • Target version changed from Tails_3.15 to Tails_3.16

#9 Updated by intrigeri 20 days ago

  • Target version deleted (Tails_3.16)

Hi!

We've set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

  • better reflect your plans;
  • bring down your amount of work-in-progress to a sustainable level;
  • encourage team work and increase the chances that someone finishes the work;
  • avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

  • Stalled work-in-progress
  • Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I'm doing on this ticket.

You now have a few options, such as:

  • Deassign yourself. That's fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
  • If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable "Target version". This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today's choice.

Cheers!

Also available in: Atom PDF