And I'm glad I wasn't in this discussion or I would have arbitrarily ripped you a new one...
Outpost 2 is a great game as it is. All patches that have been made to the game have been to fix bugs, enable us to keep playing, and add in a new map here and there.
Fifteen years ago, I would have jumped at a chance to add new things in. Hell, I was 10 and had little to no responsibilities taking up my time. Now I'm 25, looking for work, finishing up a masters degree, and s***ting myself over the prospect of paying back my student loans. What little free time I have I spend trying to escape from the stress of all that and the knowledge that it will just get worse over time.
Most of the other people who have been following this game for as long as I have (and longer) have even more responsibilities than I do. That's especially true of our main coders, who are the ones who put together all the patches that we have enjoyed.
Now, if you think that these ideas would be a good addition, here's what you *should* do to set it up:
Write up a short proposal of what you want to do to use to recruit people to help you. Split up the project into multiple parts so that it doesn't stagnate if one person suddenly gets busy. Since most of the coding done (from what I understand) is fairly standardized, there isn't as much risk of cross-styling causing conflicts. Once you have a group of people willing to work on it, go over some basic timeline stuff (not a strict timeline, justa loose guideline to help keep it going). Most importantly, pitch in where ever you can on the project. Noone wants to volunteer their time for a project where the person who came up with it isn't doing any of the work.