Time to revisit this topic again. I'm here to persuade you, Zini, to get on-board with the Github OpenMW organization.
The reason I'm bringing this up again is because I just found out that we can host binaries on Github again.
The Release Workflow:
https://github.com/blog/1547-release-your-software
Obviously you can do this on your project, since you are the defacto repo, but I doubt you want handle releases.
What I suggest is the following:
1) Create an OpenMW organization
2) Have Nicolay move his OpenMW project to the new OpenMW organization
3) Make you (Zini) the admin of the project
4) Do a MASSIVE pull from Zini's repo to the OpenMW repo to catch it up to date
5) Setup collaborators as necessary to the new OpenMW repo, maybe scrawl and/or others to handle releases and other details.
Optional (debatable?):
* We can port our wiki over to github, one less moving part
* Use github's issue/milestone tracking system instead of current one (we can port the issues)
The main benefit here is that we finally unite the original repo with Zini's repo, making it finally search-able in google and github. We also get the benefit of hosting our binaries, so when someone tags a release, we automatically get the sources and we can add a summary (our changelog?) plus binaries. This solves our hosting problems.
Our only roadblock is that there is currently someone with the name OpenMW, who joined in 2012 and hasn't done much of anything lately. We're trying to contact this person and ask github for help on this.
What do you think Zini?
