Proposed Solutions:George wrote:1. I have a limited amount of development time devoted to engine changes and we need to allocate that fairly. What is a fair system? Does every developer get a slice of time? Do you coordinate to get the most important fixes first?
2. Is there are way for people to work together on mods to spread the work (and knowledge)?
3. What's the best way to coordinate?
1. I think if we have trac, or a similar bug tracker back, we can fix and enhance the game engine instead of focusing on a single modder's requests. This way, we can focus on features instead of individual mods.1. I have a limited amount of development time devoted to engine changes and we need to allocate that fairly. What is a fair system? Does every developer get a slice of time? Do you coordinate to get the most important fixes first?
Code: Select all
2. Is there are way for people to work together on mods to spread the work (and knowledge)?We probably need to make common core mods and assets that other people can use easily (I'm thinking about Dvlenk6, SiaFu, and giantcabbage's mission framework).
We also need to document the game first and good mods so we have more examples of what we can do. I spent ~3-4 hours figuring out that A-I are bound to 1-9. It would have been better to look this up instead of spending so much time derping around.
That being said, I still want to make modding accessible to most people. In response to Shrike's post I'm thinking about starting a 'learning lisp' series which is basically an introduction to the language/computing. This will be a resource for those interested in learning. We can probably make this a community endeavor as well, but as I said earlier, coordinating is hard when all of the modders in the community are basically lone wolves.George wrote:3. What's the best way to coordinate?
tl;dr:
Solutions:
1. Get Trac back
2. document the game and good mods, show what can/can't be done
3. Get a tutorial to programming so more people can self teach.
