We have plenty of time to finish with lengthy explanations of what failed.
My idea is to make one final effort anyway. Then afterwards we can see whether we have enough people to continue, and even if not, to have a final release (and a final theme too).
Second question is what parts of the big thing should be trimmed down to produce a playable game ASAP?
I don't know either but if I have to name one feature, it would be fighting
. We should have a very simple fighting system in place. We could use what everyone else uses too, XP (Experience points) and levels. While it is not the most realistic way, it can be fun to scavenge for XP, and it would be better than the current state of the game. And I think we could easily reach that too, before "final day".
I'd also like to rally and focus EVERYONE on ONE quest. I think the two starting quests worked nicely in the past, lots of different people contributed.
We might as well use the release to regroup and start to build lacking infrastructure without the bloats and caveats that were holding us down.
Yes, but I think we need to focus a lot more, rebrand the game, put a focus. I think the code of the game should be the main focus for everyone, even if they are not coders. Just so that they get the general "feel" of how things progress.
Docs will easily follow, they are easier than code.
I'll be missing the blog, the wiki and the forums mostly.
Yup, forum was fun. Wiki too, using mediawiki. What I disliked was that these two were somewhat disconnected.
It makes it hard to know what is current, and what is outdated. I think t here should have been regular checks, and throw away what is too old
. Legacy is a bad thing IMHO.
Not sure about where to host all those things, images from the wiki are probably the heaviest. (Not sure about what Arx people are going to do.)
I guess the code logic can be easily hosted on a github repository too.
I'm not really sure how to replace the blog, but we could introduce a mailinglists instead of the forums
Hmm, mailing list is bad ... I can't cope with them.
Trac would probably contribute to "why we've fail" part, dunno if we should keep the tickets, but it's not me to decide.
I'd say to get rid of it. Trac is nice, but we have too many tickets and not enough coders. We need to more rapidly decide on tickets. If tickets are too old, I think they should be closed. Sounds harsh but I think this is better than 3 years old ticket noone will bother to close.
In the end - well, let's get loud this one time!
FINAL DAY ARTWORK TOO!