Ahoy mates,
this all sounds great to me, but what's missing in my opinion is a bit of organization (which is extremely difficult for a forum community - so no offence meant!). Having been a coder about 5 years ago, I rarely code anything nowadays (apart from quick 'n dirty hacks), but I've got some experience in project management of software development, so I'd like to share it and make a few proposals:
1. Define the goals
The goals should be well defined and be supported by the majority of the community. I'll just outline a few goals, which seem to have a broad majority:
- Complete Build 14 - at least provide a stable Build 14 for POTC
- Port Build 14 features to CoAS (see point 3 for more)
- Improve the Engine to support better quality graphics, animations and gameplay
- Create and maintain the best pirate game ever (this should be worked out in detail... )
2. Build teams (this process is already ongoing as far as I can see)
There should be these teams:
Core team
Description
The core team is the only team with access to the sources. They should be few in numbers and have a lot of coding experience (and if possible: a lot of time
)
Tasks
- Ensure the compatibility of all source code changes (code integrity)
- Implement source code changes by priority
- Provide a documentation to the modders on how to use the changes for modding (e.g. new public function calls)
Steering team
Description
The steering team consists of experienced modders and core team members. It has a coordinative role.
Tasks
- They analyze the requests and reported issues of the modders regarding the Storm engine.
- They decide which proposals require a modification of the source code.
- They form packages (small units of related requests) and write a short specification
- They assign a priority to each package and forward it to the core team for implementation
Modders team
Description
All PA! members, who contribute to the mods or did so in the past
Tasks
- Add features to the game, which have been requested by the PA! community
- Implement and update translations of mods (maybe in a subteam)
- Forward requests to the steering team, if features might require updates to the engine.
- Fix bugs
PA! community
Description
All PA! members.
Tasks
- Bring up ideas
- Test releases and report bugs
- Provide constructive criticism
- Occasionally motivate the above teams with praise and gratitude
3. Create a "migration plan" for Build 14
In order to achieve goal 4 I see the necessity to define what should be migrated to CoAS and what not. This will be more work than just "copy/paste all", but it will yield better results. Besides, I don't think anything else will work out, as we'd carry too much dead freight otherwise.
- There are features implemented in the build, which were implemented in the CoAS stock game. Those can be left out.
- There are features implemented in the build, which can be achieved much easier with the 2.8 engine.
- There are features started in the build, which will never be finished (as far as we can see now). Those should be left out.
- The key features to be ported could be defined by the community (e.g. by using a poll with all the features listed) - this would result in a prioritization
- There are already (good!) mods for CoAS, so those should be taken into account as well in the planning
Well, that was quite a lot, and I could even write more, but I think it's enough for now. I hope someone can make use of these proposals. I am afraid this is all I can contribute at the moment, and if you think, it's all theoretical rubbish, I am fine with that as well
So long,
Sulan