JBG said:
I guess I'm sort of redundant, then. >sniff<
Okay. I'll talk to TF about transferring control of the thread.
Do you guys actually still need/have a use for me? I'm sorry about not being around much lately (ISP problems

).
If you still have a use for an XML-er, civilopedia writer, basic (static) graphics man, &c (I think I enumerated my limitations earlier on) then I'm happy to stay on - although if it's felt I'm no longer required, I can vanish. It's been fun.
I think we're actually quite sparse on people, JBG. I wrote a little list for myself of all the areas in which we (might) need (want) folks--
(Some of these we've already done though as we move forward we may wish to alter, add to, or replace them.)
Intro, Event and Wonder Movies
Slideshow/Progress Screen work (and those hints that come out underneath them)
Splashscreen work
Documentation
Civilopedia Entries
Foley Work (walk sounds, combat sounds)
Background Music
Event/Notfication Sounds
Graphics/Modeling:
Units
Buttons
Buildings
Terrain
Improvements
Features
Resources
XML Specifications
Python Work
[SDK Work]
Edit:
Merge Manager
Release Manager
Design Manager/Team Lead
Edit:
XML Specifications:
Units (incl. Promotions)
Buildings
Technologies
Terrain (incl. Bonuses, Features, Routes)
Improvements (incl. Builds)
Civilizations
GameInfos (That entire folder)
Art Thief (Art XML work to import Art from the community)
General (GlobalDefines & BasicInfos)
Misc (The Misc folder and some of the other cracks which we/I don't know that much about)
(Note: Art XML files fall in with the appropriate graphics work, Sound files fall in with their associated Audio work listed above.)
Some of these XML areas are pretty narrow, but it's unclear how people might want to group them. We can have overlap, of course (and I'm sure from time to time people will want to or be required to work on areas they haven't "claimed", but the baseline work for each section should be done by the main person in charge of that area--i.e. The first conversion from the design doc once we've reviewed it).
Of everything on that list, I've got really plenty of work to do just doing the Python Work, and whatever SDK stuff we might need. Whatever I don't do, I'm sure Matt can accomplish. But these other areas... We can rely to a certain extent on the community at large for some of our graphical needs, but we're going to want someone who can make those niche models that are insufficiently interesting to catch anyone outside our projects interest. The sound issues are even less likely to get solved for us. The Documentation, Civilopedia and XML work is clearly going to be all us. I'd say we need several people. Not to mention, given the nature of our last bug (randomly shows up after you've played at least 50 turns), I'd say we have need of play testers as well. Not to mention a Build master and a Release master (I'm currently thinking I'll be handling the actual releases; I had hoped to have Matt do the build merging so he could merge/test and then I could sanity check his build and do the release, but I'm not sure how much time Matt's going to have for that sort of thing...).
Anyway, I'd say we have plenty of work to go around.