Tails

#1 Updated by sajolida 2015-10-14 09:24:32

• Parent task set to Feature #9854

#2 Updated by sajolida 2015-10-14 09:25:09

• Parent task deleted (Feature #9854)

#3 Updated by sajolida 2015-10-14 09:25:23

• Parent task set to Feature #9855

#4 Updated by sajolida 2015-10-14 09:25:59

• follows Feature #9854: Write a post about achievements in 2015 added

#5 Updated by sajolida 2015-11-27 02:50:29

• Target version changed from Tails_1.8 to 246

#6 Updated by sajolida 2015-11-27 04:40:58

• Target version changed from 246 to Tails_2.0

#7 Updated by sajolida 2016-01-26 18:30:49

• Target version changed from Tails_2.0 to Tails_2.2

#8 Updated by sajolida 2016-03-07 15:12:08

• Target version deleted (Tails_2.2)

#9 Updated by sajolida 2016-10-03 17:31:21

• Target version set to Tails_2.7
• QA Check set to Ready for QA

Done in https://tails.boum.org/blueprint/donation_campaign_2016/#index3h1.

#10 Updated by sajolida 2016-10-03 19:18:59

• Assignee deleted (sajolida)

#11 Updated by intrigeri 2016-10-04 07:03:52

• Assignee set to intrigeri

(Same as Feature #9854 and friends.)

#12 Updated by intrigeri 2016-10-04 07:49:39

• Blueprint set to https://tails.boum.org/blueprint/donation_campaign_2016/#index3h1

#13 Updated by intrigeri 2016-10-04 08:47:08

• Subject changed from Write a post about plans for 2016 to Write a post about plans for 2017+
• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to sajolida
• % Done changed from 0 to 70
• QA Check changed from Ready for QA to Dev Needed

Not much to say since that’s basically a copy’n’paste of our roadmap.

• The ticket title says “for 2016”, which I guess is a mistake, fixing that.
• The post ends a little bit abruptly IMO. Maybe add a conclusion paragraph encouraging people to donate, and linking to the donations page?
• I wonder if/how we should perhaps clarify what we realistically hope to do in 2016/2017 (stuff that has a team which is known to deliver what they commit to do) vs. what’s less realistic (e.g. lack of a team, or less experienced team) or simply scheduled for 2018+. The underlying concern I have is avoiding to look like in a year like we’ve not done what was promised (I know the post says “in the next years”, but still one might expect that 30-50% is done in a year after reading this post). Or maybe just keep everything as-is but clarify what we mean with “plans”, i.e. they’re things we want to do, that we think are important work items, but require a few things to make them happen, such as sufficient funding (if the fundraising drive does not raise enough money to cover our survival budget, then survival work will need to be done as volunteers, and then it’s unlikely that all these fancy features and improvements are done for free on top of the mere survival work; we should probably not explain this in the blog post, of course).

#15 Updated by sajolida 2016-10-06 21:37:25

• Assignee changed from sajolida to intrigeri
• QA Check changed from Dev Needed to Ready for QA

#16 Updated by intrigeri 2016-10-07 16:42:52

• Status changed from In Progress to Fix committed
• Assignee changed from intrigeri to sajolida
• % Done changed from 70 to 90
• QA Check changed from Ready for QA to Pass

Perfect, reassigning to you to track publication.

#17 Updated by sajolida 2016-10-13 18:22:18

• Target version changed from Tails_2.7 to Tails_2.9.1
• Feature Branch set to web/10369-plans
• Blueprint deleted (https://tails.boum.org/blueprint/donation_campaign_2016/#index3h1)

#18 Updated by sajolida 2016-10-13 20:00:49

• Status changed from Fix committed to In Progress

Applied in changeset commit:889bd142d41a9d1ea02c2bb31b2dbc6e9b4b946c.

#19 Updated by sajolida 2016-12-04 13:58:41

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

Published already.