(apologies if the snipping removes too much context)

I understand T.M.O. to encompass 3 major components (this is from my experience so anyone feel free to correct me on anything I've overlooked):

Talk.
Whist not trivial nor free it sounds as if this could be straightforward to provision (it's has been previously, so is almost a known entity?). Is the DNS / Regsitration for maemo.org under our / the council's control already?

Repositories.
I see this as the most critical part for 'disaster planning' as users depend on these services who are not necessarily party to any of the conversations that happen here and elsewhere - how would an update to sources be communicated if required?
How sustainable is a mirroring approach?
Would it be disruptive to users?
In terms of finding a home for the repos is their anyone else 'upstream' (other than Nokia) who could offer any support - Debian, Gnome etc

This is the part I wouldn't know how to go about solving.

Garage.
The primary services of source code hosting, bug tracking and mail-list management could be replaced with usage of external free services; sourcecode hosting (Github or Sourceforge), mailing lists (Google Groups etc)
Whilst I'm sure this doesn't offer a feature for feature replacement - it should cover the core.


Naturally, the best outcome would be funding to continue as it is now, but we are talking Plan B / C here.

Just my thoughts on how to approach minimising some of the costs, I'm sure I've missed a lot of the subtlety though.