It is in the long-term interests of this project and the EUTC for reasons of tinkering to select a suitable free software license for this codebase and make the source publicly available - perhaps with a word on how we're unlikely to be of much help in the future.
By opening up the codebase in a way that protects it (and ourselves) we extend the longevity of the project and provide a starting point/how-not-to guide (depending on your viewpoint).
The purpose of opening this issue is to begin the discussion on how to do this, and a couple of things immediately spring to mind:
Review. There may be parts of the git tree that we wish to "rewrite" in the interests of removing confidential information. I'm not sure if there's anything in particular, but I seem to remember there being some discussion of this before.
Documentation. Only a little bit, I promise. A short abstract explaining the scope and goals of the project, and enough information to get up and running with a working environment. Lower the barrier to entry...
Have I forgotten anything?
Edit: Please feel free to share this with anybody who may be interested in this project/has expressed an interest in the past.