[TheLieka]

Ok, I think that we're all agreeing on the what(s), now we're just haggling on the how(s).

we can sit here and negotiate this all day (for weeks), but someone needs to grab the reigns and run with it.

Suggested Execution:
Collaboration Space:
Matt, would it be possible for you to split the dev section to add a "Community" dev section?

Since I don't think we want to do a full project fork, but the devs don't want to take the time to test / add the community code, I suggest that we take their code changes and test / add them to our code, as if it was submitted by the community. At that point, we would be able to keep a comprehensive source version, rather than a rogue code source.

Over time, I feel that this approach would make the community code, the official source for the project.

Code Repository
We will need someone (please step up and volunteer) to set up a repository for code builds. I guess this would be done through source forge. Whoever sets this up, should delegate to a few trusted people to keep this clean.

We should have all the official working database tools up there as well, along with a comprehensive guide on building the source. There are 45 different guides on the forums and wiki, and none of them work 100%, they all expect that you've used Visual Studio or whatever tool before. We need to make this project accessible to the masses. If anyone is willing to come in and join this team, they should be welcomed and treated with respect. We gain NOTHING from flaming new people. Let me repeat that:

We gain NOTHING from flaming new people.


Let's get this thing started. What other items need to be handled?

Dax