Tails

#1 Updated by sajolida 2015-05-12 16:38:24

• Assignee set to tchou

I like this idea very much even if I feel lazy to:

• Find how to integrate this in the wireframe.
• Have the warnings in the release notes ready for inclusion in there (while available elsewhere at the same time).

Tchou: what do you think?

#3 Updated by sajolida 2015-05-12 16:57:22

• blocks Feature #8855: Design data source for ISO verification extension added

#4 Updated by sajolida 2015-05-20 17:53:56

• blocked by deleted (Feature #8855: Design data source for ISO verification extension)

#5 Updated by tchou 2015-08-28 07:12:49

• Assignee changed from tchou to sajolida

I think it’s better to have a way to warm the user before or after, but not while.

before :
- before even trying to intall tails. We suppose that the user knows tails, but we could add a tiny link “shure you want to use tails?” or “What is tails” in the first screen of the router (or have a spash screen).

after:
Maybe in the Installation Assistant (same for upgrade), at the end (or before the persistence) because :

- we are closest to the real us
- we are in a browser (rather thant is this Tails Installer itself, that could be an option) so it’s easier to follow links (like tickets, knows issues…)

#6 Updated by sajolida 2015-09-02 08:41:15

• Assignee changed from sajolida to tchou
• QA Check set to Info Needed

Could you clarify what you mean by “before or after”, before of after what? We’re talking here about the download step of the Download and Verify extension. I’m saying this because I have a hard time understanding your comment especially since you’re saying “after: Maybe in the Installation Assistant” while the Download and Verify extension is part of the Installation Assistant. Maybe you though we were talking about Tails Installer…

Anyway, I’m personally in favor of keeping this as a good idea for later but not as part of our initial work in 2015. We have too much to do already.

#7 Updated by tchou 2015-11-04 14:43:06

• Assignee changed from tchou to sajolida
• QA Check deleted (Info Needed)

When I say “I think it’s better to have a way to warm the user before or after, but not while.”, it mean that I think that the download time is not the best moment to do it.

So lets close this ? or change target for next year with low priority ?

#8 Updated by sajolida 2015-11-07 07:38:36

• Priority changed from Normal to Low

As I said in Feature #9386#note-6, I propose not to discuss this any futher in 2015. But I want to the idea on my radar. So I’m fine with having this assigned to me. Low prio, right.

#9 Updated by sajolida 2016-01-05 22:27:35

• Parent task deleted (Bug #7552)

This won’t be done as part of Bug #7552 as a first implementation.

#10 Updated by sajolida 2016-04-01 10:59:17

• Assignee deleted (sajolida)
• Priority changed from Low to Normal

#11 Updated by sajolida 2016-05-10 06:12:06

• related to Feature #8845: Give some love to our warning page added

#12 Updated by sajolida 2016-05-10 06:12:22

• Affected tool changed from ISO Verification Extension to Download and Verification Extension

#13 Updated by intrigeri 2017-11-18 10:56:21

• Assignee set to sajolida
• QA Check set to Info Needed

Is this still relevant with the new extension? If not, let’s reject.

#14 Updated by sajolida 2017-11-29 13:04:28

• Assignee deleted (sajolida)
• Priority changed from Normal to Low
• QA Check deleted (Info Needed)

Good question…

From a user perspective, even with the new download page the user has to wait until the download is finished and that waiting time could still be a place to display useful information.

But from a technical perspective, with the new download page we apparently can’t monitor when the download really starts and when the download really finishes. So we are missing the mechanisms that would make it possible to start displaying useful information and stop displaying it once the download is over (and display instead the verification step).

These technical limitations might be possible to work around either with code, either with UX. But I don’t think we should keep this high on our radar as we don’t have plans or budget to work on this any time soon.

Then it’s the frequent problem of what to do with good ideas that seem important but for which we don’t have a clear plan for the future. I’m fine rejecting and reopening later, but:

• It’s not the meaning I put behind the phrase “rejecting an idea” in English.
• It’s not the meaning documented for “Rejected” in https://tails.boum.org/contribute/working_together/Redmine/.
• The same logic could probably apply to a good share of other open tickets.

#15 Updated by sajolida 2017-11-29 13:06:09

• Affected tool changed from Download and Verification Extension to Verification Extension