Tails

#1 Updated by sajolida 2015-04-08 21:28:41

• Subject changed from Integrate subscribing to the newsletter in flowchart to Assistant: Integrate subscribing to the newsletter
• Parent task deleted (Feature #8583)

#2 Updated by sajolida 2015-04-08 21:29:03

• Parent task set to Feature #9194

#4 Updated by sajolida 2015-04-25 12:03:07

• Parent task changed from Feature #9194 to Feature #9199

#5 Updated by sajolida 2015-05-19 19:22:27

• Affected tool set to Installation Assistant

#6 Updated by sajolida 2015-08-15 08:15:14

• Assignee set to sajolida

#7 Updated by sajolida 2015-08-15 10:36:32

• Status changed from Confirmed to In Progress
• Assignee changed from sajolida to tchou
• QA Check set to Info Needed
• Type of work changed from Research to Discuss

I had a second thought on that one and I’m really not sure where to put it.

On the current download page it is before the installation and we’re saying “It’s very important to keep your version of Tails up-to-date, otherwise your system will be vulnerable to numerous security holes.”.

The thing is that people are notified anyway on the desktop about new versions and even more, now that we have IUK, subscribing to the mailing list is actually not the best way to keep your Tails up-to-date. The best way is to actually do the updates when IUK asks you to whether you are subscribed to the mailing list or not.

I’m also not convinced by having this before the installation step. People might be more willing to subscribe after installation if it suceeded. Or they might get even more pissed if they gave their email but cannot install!

I might also look intrusive to be asked for an email address by an anonymity distro. All-in-all, I think it should be less strongly advertized. Also, people are already suggested this every time they start Tor Browser inside of Tails as it appears on top of the News page.

So I have two proposals:

• We keep this as a step between “Restart on the final Tails” and “Create an encrypted persistent storage (optional)”.
• We don’t add it to the installation process at all.

tchou, what do you think?

#8 Updated by tchou 2015-08-28 06:15:10

• Assignee changed from tchou to sajolida

> * We keep this as a step between “Restart on the final Tails” and “Create an encrypted persistent storage (optional)”.
+ 1 . I agrea with your concerns, but Tails history showed that sometime upgrade notification was broken, so we could have a “belt and braces” approach.

#9 Updated by sajolida 2015-09-02 08:31:26

• Category set to Installation
• QA Check changed from Info Needed to Dev Needed
• Type of work changed from Discuss to End-user documentation

I’ll do that.

#10 Updated by sajolida 2015-09-03 08:29:02

• Parent task changed from Feature #9199 to Feature #10103

#11 Updated by sajolida 2015-09-03 08:57:35

• Assignee changed from sajolida to tchou
• Target version set to Tails_1.6
• QA Check changed from Dev Needed to Ready for QA
• Feature Branch set to web/8841-newsletter

Done in a dedicated branch as proposed in the new methodology. Please review web/8841-newsletter and then I’ll merge it into master.

To view to changes you can do:

git diff origin/master...origin/web/8841-newsletter

or

git log -p origin/master...origin/web/8841-newsletter

#12 Updated by sajolida 2015-09-06 14:06:36

• Priority changed from Normal to Elevated

#13 Updated by tchou 2015-09-18 00:58:22

• Status changed from In Progress to Resolved
• Assignee deleted (tchou)

ok.

#14 Updated by sajolida 2015-09-18 09:47:02

• QA Check deleted (Ready for QA)

Cool, I merged it then!

Note for other times: as you can’t merge branches in the main repo yourself, I have to do the merge of my work myself. It would be helpful in such cases if you marked these tickets maybe as “Status = In Progress” and “QA Check = Pass”, so that I can still see that I need to do the merge and push. If they are marked as resolved I might miss them.