Feature #12710

Gather data and feelings for our 2018Q2 → 2019Q1 budget forecasting

Added by intrigeri 2017-06-15 06:49:00 . Updated 2018-01-24 08:58:07 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Start date:
2017-06-15
Due date:
% Done:

100%

Feature Branch:
doc/roles-2018, fundraising.git:budget/2018.mdwn
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See the “November” section of the forecasting process doc. This must be started in November, and completed by the end of the calendar year.


Subtasks


Related issues

Blocked by Tails - Feature #12709: Bootstrap the 2018Q2 → 2019Q1 budget forecasting process Resolved 2017-06-15
Blocks Tails - Feature #12711: Zoom into potential issues wrt. our 2018Q2 → 2019Q1 budget forecasting Resolved 2017-06-15

History

#1 Updated by intrigeri 2017-06-15 06:49:12

  • blocked by Feature #12709: Bootstrap the 2018Q2 → 2019Q1 budget forecasting process added

#2 Updated by intrigeri 2017-06-15 06:52:04

  • blocks Feature #12711: Zoom into potential issues wrt. our 2018Q2 → 2019Q1 budget forecasting added

#3 Updated by intrigeri 2017-08-26 15:25:18

  • Assignee deleted (None)

#4 Updated by anonym 2017-11-15 11:30:53

  • Target version changed from Tails_3.3 to Tails_3.5

#5 Updated by intrigeri 2017-11-15 16:53:52

  • Priority changed from Normal to Elevated

u: I’m finally done with everything I wanted to see happen before we go ahead here. We’re running late so I was going to proceed but I could not find this ticket on my plate… and eventually realized it’s because it’s on your plate! … which is good because I’ll have lots of work to do on various teams to answer your questions :)

Do you think you can initiate this process this week? Otherwise, no problem, let me know and I’ll handle it.

I’m raising priority so this time-bound thing is more visible on our various Redmine radars.

#6 Updated by Anonymous 2017-11-16 09:25:59

I will be able to do that tomorrow or monday. Sorry, also very busy currently, but I did not forget this.

#7 Updated by intrigeri 2017-11-16 15:32:35

> I will be able to do that tomorrow or monday.

Great :)

#8 Updated by Anonymous 2017-11-20 14:28:49

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 30

Sent out the emails. Waiting for feedback until the deadline, end of calendar year.

#9 Updated by intrigeri 2017-11-20 17:48:31

> Sent out the emails.

Yeah! :)

> Waiting for feedback until the deadline, end of calender year.

Ideally the deadline would be end of November, because our plans include follow-ups in December (+ nagging those who didn’t reply yet, until they do). So I suggest we ping them soon (e.g. end of November) and clarify that there’s follow-up work we want to do in December ⇒ it would be great if they replied by December 15. Rationale: I’m worried about receiving answers on December 31, then having to ask for clarification & to wait, which would force us to postpone what we need to do in January. I can do this if you prefer :)

#10 Updated by intrigeri 2017-11-26 09:56:53

I just noticed we need to go through the same process for the fundraising & accounting teams, by the way :)

#11 Updated by intrigeri 2017-11-26 09:58:20

intrigeri wrote:
> Ideally the deadline would be end of November, because our plans include follow-ups in December (+ nagging those who didn’t reply yet, until they do). So I suggest we ping them soon (e.g. end of November) and clarify that there’s follow-up work we want to do in December ⇒ it would be great if they replied by December 15. Rationale: I’m worried about receiving answers on December 31, then having to ask for clarification & to wait, which would force us to postpone what we need to do in January. I can do this if you prefer :)

After reading the actual email you’ve sent: scratch that, sorry!

#12 Updated by intrigeri 2017-12-09 08:36:20

  • Feature Branch set to doc/roles-2018, fundraising.git:budget/2018.mdwn

#13 Updated by intrigeri 2017-12-20 06:25:41

  • related to #14543 added

#14 Updated by intrigeri 2018-01-01 13:34:22

  • % Done changed from 30 to 50

#16 Updated by anonym 2018-01-23 19:52:45

  • Target version changed from Tails_3.5 to Tails_3.6

#17 Updated by intrigeri 2018-01-24 08:58:07

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

The only remaining open question will be tracked by Feature #12711.