Okay, lets just think about what is needed to put togther an open source collaborative project and what we would want and not want to include in 'Community Patch #1: YR v1.002'.
Whats needed:
Some kind of version control, someone who is going to maintain the master build of the working patch in progress.
A file repository, probably an FTP with various levels of access. Need at least 2 levels, one that provides read only access to all individual files needed to build the patch as approved by content moderators and one that provides a place to upload modified files for approval. This lets people wanting to contribute or improve one aspect of the patch download only the files that pertain to that aspect and not have to pick the patch apart.
Moderators to look over and approve submissions of assets (UMP is likely to have majority of needed code changes initially), make sure they are of comparable quality to WW assets.
What should be included:
Patches to the exe that fix bugs or re-activate/add logic not normally in the game.
Art assets and code that demonstrate new features working, even if they are not active in the actual patch itself (kind of like leftover code and assets that WW left in there).
Support for assault game mode
A few new maps to show of any re-enabled terrain logic (conversions of TS maps maybe?)
TX terrain pack maybe??
What should be left out:
The assault map packs themselves (leave them as an optional addon).
Any tinkering with the AI beyond fixing a few known bugs. Certainly not implementing any of the AI's that use fake units/buildings to improve the AI's savvy.
New content beyond demo stuff that isn't normally available...leave that to other mods to provide.
Edit:
Also, I think discussion of a patch using any future modified exe should be moved to another discussion and leave this for discussing the actual exe mods themselves. Also, its probably not worth worrying about starting to get this together until there has been a lot more added to the exe to actually make stuff to use.
Whats needed:
Some kind of version control, someone who is going to maintain the master build of the working patch in progress.
A file repository, probably an FTP with various levels of access. Need at least 2 levels, one that provides read only access to all individual files needed to build the patch as approved by content moderators and one that provides a place to upload modified files for approval. This lets people wanting to contribute or improve one aspect of the patch download only the files that pertain to that aspect and not have to pick the patch apart.
Moderators to look over and approve submissions of assets (UMP is likely to have majority of needed code changes initially), make sure they are of comparable quality to WW assets.
What should be included:
Patches to the exe that fix bugs or re-activate/add logic not normally in the game.
Art assets and code that demonstrate new features working, even if they are not active in the actual patch itself (kind of like leftover code and assets that WW left in there).
Support for assault game mode
A few new maps to show of any re-enabled terrain logic (conversions of TS maps maybe?)
TX terrain pack maybe??
What should be left out:
The assault map packs themselves (leave them as an optional addon).
Any tinkering with the AI beyond fixing a few known bugs. Certainly not implementing any of the AI's that use fake units/buildings to improve the AI's savvy.
New content beyond demo stuff that isn't normally available...leave that to other mods to provide.
Edit:
Also, I think discussion of a patch using any future modified exe should be moved to another discussion and leave this for discussing the actual exe mods themselves. Also, its probably not worth worrying about starting to get this together until there has been a lot more added to the exe to actually make stuff to use.