Its a rather confusing issue, which can easily be solved using a repository like github. If OpenBVE was put on a repository before, it would be easy to distinguish the original version and a forked version of the project. Not to mention nothing would've been lost in the process, and there would've been no need to scramble around to try to buy up domains just to get the file hosted online again.
It would also be a million times easier to fork the project, and collaborate with other developers, who wish to work on the project, this is all through the source code versioning system allowing teams to easily create code changes and see what was done, but of course, at this stage, I'm still trying to convince people who will be willing to do this, as placing it on a source code versioning system like github, it will allow OpenBVE to retain its Open Source visions by providing a public location where everyone can view its source code, allow anyone and everyone to contribute or freely fork the project, and provide the security of a independent service (that is unlikely to go down) allowing anyone to download it.
As far as my opinions on OpenBVE.org (remember that BVEStation Administration DOES NOT own it), because it is not assumed to be the original version of OpenBVE, while at the same time it has the name of the official name of the site. The original developer should be the one holding the site, and I'm sure its frustrating for them to have to deal with it, even if the project is in public domain. That should be simply in respect of the original developer.
Also since the original developer michelle is now dead/gone putting her roadmap is something that nobody cares about at this point. I'm sure the community has different goals and requests. Rather the roadmap should be a collaborative effort of the community and it should be what the community wants and where everyone wants the project to move forward in. This really brings in the public domain and openness of the project. There's no need for a developer blog either, we have enough forums, and github's version control will force (kinda) you to comment on every change you make, this makes it easy to create change logs and all the other goodies you'd want from a blog, not to mention make it easy to download older versions of the project, track bugs, etc.
Ok, so to summarize, we need to get this project on some type of source code versioning system, github, source forge, etc. We should respect the original authors despite the project being in public domain and thats my 2 cents.