And about your comment about 10 viable communities adding diversity and
You can cut a worm into to two and it'll live. Most of the time. Try
cutting up a worm into ten pieces and tell me what that gets you.
A dead worm. In case you don't figure that analogy out.
And I'm not saying *thrash everything*, I'm say: STOP SPAMMING CLONES!
IT'S NOT GETTING ANYWHERE!
Take the DB which is most complete/expandable, graft the information it
doesn't have from the others if they do. Get a real/proper/adequate CMS,
not a non-scaling/limited one like Joomla. Set both up on a server.
Once we got that done we can cut up the jobs that need to be done. For
* Recovery of manuals / Additional setup instructions
* Recovery of game files
* Recovery of associated files (mods, etc..)
* Higher res screenies
* More capable search system?
* Forums with subforms for each game (+ link to that forum on game page
* Virus checking system? (Please, gods rot it, pick a good one!)
* System for submitting new games
If people want to try out different UIs, give them a subdomain and they
can use std. access to the DB and work with the same dataset as everyone
else while still getting their own UI design. We'll vote on one later on
for the main page or something.
Sorry for bluntness, but the Joomla specs don't meet what this'll need
in the long term AFAIK. I seriously doubt any community will live with
their entrails cut up into ten bits.
Personally I have a (bad?) habit of doing three re-writes on any project
minium if it's some sort of API, simply because hacks or inefficiencies
in APIs are unacceptable. And that's the same as the framework for the
new HOTU. Your cornerstone won't hold much weight.
This maybe will upset some people who don't get to use their sites,
depending on what happens, but it appears some people are upset already
that could happen, although I see no reason to go forwards if the
mentality is more than one site, and that people can't cooperate on one
effort (the process of rebuilding one site can easily be reinvested in
I think active posters shall be the ones able to vote, otherwise we
could have some problems with the identity of some voters...
Two weeks from now on could be a nice deadline for making the ultimate
Many web sites are moving to open source CMS. For example, InfoWorld
just moved to Wordpress. (See http://drupal.org/cases and
http://wordpress.org/showcase/ for more details.) A huge benefit of an
open source CMS is that they are much less open to exploits, as the
code is continually tested and audited by many parties.
Simply, if we're going to build a CMS from scratch, we're wasting time
reinventing the wheel. We should rather start with an established
open-source CMS and modify is as seems fit. Drupal is well designed
when it comes to that, and I'm sure many others are too, but I can't
speak for them, as I haven't used them.
I think we'd be best off finding a CMS that is scalable and does what
we need, and build on it.
Just my thoughts,