Bug #16116

Write blog posts about plans

Added by sajolida 2018-11-11 06:56:59 . Updated 2019-01-04 17:48:46 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Start date:
2018-11-11
Due date:
2018-12-07
% Done:

0%

Feature Branch:
web/16116-plans
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description


Files


Subtasks


History

#1 Updated by sajolida 2018-11-11 06:57:16

#2 Updated by sajolida 2018-11-11 07:34:41

Copying intriger’s comments from Feature #15931:

  • 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.

#3 Updated by sajolida 2018-11-11 08:08:29

Thanks for the review!

> * I think “are still a major difficulty” is not the best English phrasing. Maybe “cause major difficulties” or similar?

Done in 9282079332.

> * Secure Boot:
> Let’s either say “UEFI secure boot”, “Secure boot” or “Secure Boot”: merely “secure boot” suggests something more magical than it is.

Done in 6b9c0e917b.

> 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.

Done in eaa0acbbd6.

> s/Busted/Buster/ (hopefully!)

Oops!

> * “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.

Done in 6fd3b94b10.

> * 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.

That’s moire’s part of the job. Sorry for not making this clear at first.

#4 Updated by sajolida 2018-11-11 08:09:42

  • Assignee changed from sajolida to moire
  • QA Check set to Dev Needed
  • Feature Branch set to web/16116-plans

Reassigning to moire to put some motivating sentences around all this.

#5 Updated by sajolida 2018-11-11 08:11:58

  • Due date set to 2018-12-07

We originally planned to publish this around December 7.

#6 Updated by moire 2018-11-22 17:58:16

Attached is a patch file for “our plans in 2019”.

#7 Updated by sajolida 2018-11-28 21:24:27

  • QA Check changed from Ready for QA to Pass

Good, the blog post is ready now!

#8 Updated by sajolida 2018-12-10 15:47:48

  • Target version changed from Tails_3.11 to Tails_3.12

We agreed on posting it between December 17-20.

#9 Updated by sajolida 2019-01-04 17:48:46

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Pass)

Done some days ago already.