Tails

#4 Updated by intrigeri 2018-10-31 10:32:44

sajolida wrote:
> Here is a draft. I’ll also ask intrigeri to review and correct me when I was too optimistic :)

=> moire, please reassign to me once you’re done.

#5 Updated by sajolida 2018-11-02 10:33:50

To speed things up (the original idea was to publish a second post next
week), I thought that you both could work in parallel:

- moire on the intro, outro, and sexiness of the post.
- intrigeri on the correctness of the items I included.

But I don’t really care as long as we have something ready to be posted
next week :)

#7 Updated by intrigeri 2018-11-02 15:25:12

> To speed things up (the original idea was to publish a second post next week), I thought that you both could work in parallel:

Deal!

> - intrigeri on the correctness of the items I included.

Here we go!

Achievements:

• Hmm, what about Tails 3.0 (Stretch)?
• s/helped that many people being/help many people be/
• s/smaller upgrades:/smaller upgrades/
• This article would feel much more engaging if there was an introduction sentence, e.g. to say “thanks to your donations last year, blah blah”.

Plans:

• I think “are still a major difficulty” is not the best English phrasing. Maybe “cause major difficulties” or similar?
• Secure Boot:
  • Let’s either say “UEFI secure boot”, “Secure boot” or “Secure Boot”: merely “secure boot” suggests something more magical than it is.
  • I don’t think we’ll ship Secure Boot support in our first release based on Buster. I am still hopeful that Buster will have Secure Boot support but we won’t get it for free, e.g. we’ll have to switch to GRUB2 at least for USB sticks, so I think we’ll start working on it only after we release 4.0. But the phrasing suggests we’ll get it for free and might ship it mid 2019.
  • s/Busted/Buster/ (hopefully!)
• “get rid of manual upgrades” suggests manual upgrades won’t be possible anymore. I know I’ve let this through in the roadmap, sorry about that. What about “remove the need for manual upgrades”? And perhaps add a “most of the time” indication as manual upgrades will still be required when upgrading to 4.0, 5.0, etc.
• s/upgrades mechanisms/upgrade mechanisms/
• s/many technical migration/many technical migrations/
• s/Java 9/Java 11/ (the test suite problem starts with Java 9 but we’ll have to address it for 10 or 11, whichever is the default in Buster)
• This article feels a bit dry. An introduction sentence would fix this for me and would be a great place to make it clear that this is the work we want to do in great part with these donations, assuming the donation campaign is successful, not something that will magically happen for free.