TYPO3 Phoenix and FLOW3 budget use until August 2012

Categories: Association Created by Karsten Dambekalns
This article describes the use of funds granted to the TYPO3 Phoenix and FLOW3 project in 2012 until now.
This post will quickly look back at the budget application for 2012 and then show how the budget was spent in 2012 so far.

The 2012 budget application

For 2012 the project was granted 197.600 € for development. An independent budget of 24.000 € is reserved for work on the UX/UI. In addition to that there is the joint budget of 36.000 € to be used by the v4/6 and Phoenix teams together.

Budget Use until July 2012

Let me explain some of the things you are about to see.
  • The spreadsheet contains hours per month. Those are hours worked, so any holiday hours are not contained in those numbers. Furthermore, those numbers are minimum hours worked, as everyone on the team most of the time works more than is invoiced…
  • Expenses mostly cover JiffyBox costs for hosting various integration setups, our CI server and some production websites. We are moving to the TYPO3 projects infrastructure slowly, this process still continues.
  • The graph titled Remaining Budget (Estimate) in the spreadsheet is a projection of the money spent, with the estimated costs being colored red. As invoices come in, those numbers are replaced by the real ones. (This time there are two green numbers as well, those have not been invoiced yet, but are known to me already.)
So far our estimates have worked out quite nicely, but some deviations are obvious. One example for that is budget not being used. Christian Müller did not invoice anything of the work he did until July and for Rens we have a similar situation, only half of his actual work time is invoiced. Give those guys a hand! Less reason for happiness can be found in the UI/UX and joint development budgets not being touched so far, although hope dies last, as usual. July (and August, too) are popular holidays, as can be seen from the hours worked. :)  Travel expenses are lower than last year so far, although the exact costs of next weeks code sprint in Copenhagen are not yet known, of course. As with the sprints already held in Lübeck and Venlo this year, we are trying to keep costs low, of course.