Since we began this phase, we have spent more than the estimate on maintenance, and doubled the server’s memory under the pressure of use; so it has been more expensive than we thought. It is also a great indicator of a shift to a different, more formal way of seeing the web maintenance as Transition Network shifts into a more formal phase.
NOTE: 7/8: the board approved the rise in budget and the request to double the RAM on our LIVE server Puffin.
- Read about the web maintenance budget on the wiki page
- Read about the the servers on their own wiki pages – Puffin – Parrot – Penguin
The web project budget is split into three streams:
The web maintenance budget is funded directly from core funding and is what this report is about.
This is our first experience of working this way.
The web maintenance budget for 2013/14 was an estimate to see how things go, with quarterly reviews to keep everyone up to date. So this is a learning experience. There are two key reasons why this feels new:
- All of this core cost was previously held in the Tudor web budget, and then the Nominet web budget. In effect, it was invisible to core, and we are now adopting it into core.
- As well as having a more formal budgetary arrangement, we are on new web servers and using new web server software which is relatively unknown.
You are welcome to enjoy the report by downloading it from this blog post – it includes:
- Budget estimates and actual
- Emergency memory addition
- Total increase in budget requested
- Quarter 1: a valuable opportunity to see the shift we are going into
- General point: organisational strategic changes will lead to web changes
… Continued in the report attached to this blog post…and here’s a silly cat picture because this is my blog and I get to put cat pictures on it – it’s that or pictures of binary figures in tunnels, or suited people looking at computers…