Things have moved on.
The really good part is that London Underground in the best traditions of a public body have agreed to release the framework as open source. It will be sponsored or adopted by the UK Department for Transport as part of a drive to push systems engineering throughout the transport domain.
It is being released in 4 products: 1) metamodel 2) UML profile 3) Viewpoint and stereotype definitions 4) Sparx Enterprise Architect file / plugin.
We have the OK from both the US DoD (DODAF) and the UK MoD (MODAF).
Have let loose the general UML profile ( http://trakumlprofile.sourceforge.net
) and the MDG technology (plugin) for Sparx Systems' Enterprise Architect ( http://mdgfortrak.sourceforge.net
). These 2 parts are implementations (i.e. solution) of TRAK. They are released under GPL v3.
The remaining 2 parts - the metamodel ( http://trakmetamodel.sourceforge.net
) and the viewpoints ( http://trakviewpoints.sourceforge.net
) will escape very soon. Releasing properly as open source is a very rigorous affair - I am trying to structure the documents and properly preserve the attributions and history with respect to MODAF to be carried forwards. These are the logical (solution free) definitions.
All 4 sourceforge sites have individual mechanisms ("trackers") for capturing bugs, support requests and feature requests in a systematic and open way. I've set up the categories for each based on the content of each product. I've added some headline features for each.
In time there is some joining up to do.
There is quite a lot more that will happen soon.
The best way to keep in touch with the Sourceforge products is to subscribe to each site's RSS feed - this will provide alerts in terms of file activity, news, support etc
As open source products anyone will be able to get involved in the definition and problem-solving to improve the framework and it will all be in the open.
Not saying it's perfect - we know it isn't. It's good enough for practical purposes and we have a list of things that need looking at. What I hope is, being open source, that anyone needing to apply it in a particular situation and finding it lacking can then get involved to solve the problem. Application and usability are all important - more so than any theoretical underpinning. The framework is not a system - this only arises when you add tools, people, organisations and therefore you always have to address visibility, navigation, affordance etc - in short the user interface for the whole thing. We hope in this way that TRAK will be user-centric and problem-led rather than specification-centric.
Anyway, that's the utopian vision which can only be achieved if others get stuck in!
Epitaph: 'Under this sod lies another'
TRAK support: http://www.trak-community.org
TRAK training: http://www.eclectica-systems.co.uk/trak-training