Project

General

Profile

Feature #12710

Feature #12708: Prepare our 2018Q2 → 2019Q1 budget

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

Added by intrigeri 6 months ago. Updated 4 days ago.

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

30%

QA Check:
Feature Branch:
doc/roles-2018, fundraising.git:budget/2018.mdwn
Type of work:
Communicate
Blueprint:
Starter:
Affected tool:

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.


Related issues

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

Associated revisions

Revision 5f737760 (diff)
Added by intrigeri 4 days ago

Update RM & FT roles for 2018Q2 and onwards (refs: #12710)

Revision 134e00a0 (diff)
Added by intrigeri 4 days ago

Drop a task from the RM role (refs: #12710)

This has never been done consistently, which has never caused problems recently.

Revision a1d81b1c (diff)
Added by intrigeri 4 days ago

Drop another task from the RM role (refs: #12710)

This has never been done consistently, which has never caused problems recently,
so we've moved this to a recurring task done once a year by the Foundations
Team: next iteration is refs: #15029.

History

#1 Updated by intrigeri 6 months ago

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

#2 Updated by intrigeri 6 months ago

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

#3 Updated by intrigeri 4 months ago

  • Assignee set to u

#4 Updated by anonym 28 days ago

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

#5 Updated by intrigeri 27 days ago

  • 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 u 27 days ago

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 26 days ago

I will be able to do that tomorrow or monday.

Great :)

#8 Updated by u 23 days ago

  • 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 22 days ago

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 17 days ago

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

#11 Updated by intrigeri 17 days ago

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 4 days ago

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

Also available in: Atom PDF