Developers and project tasks

This project will eventually consists of a substantial set of math-loaded routines. Therefore, I plan to assign developers to small and easy tasks so that they will not be overwhelmed by the amount of complex code written by others.

Also, for each task I plan to assign multiple developers. By doing so the project is less dependant on one key developer (which is a risk if this developer leaves the project). The trick is that 2 (or more) developers should communicate their ideas via the e-mail list. In this manner the e-mail archive will serve as a source of knowledge after some time.

So, if you want to contribute to this project:

• Share your ideas via the email-list (ac3-general@lists.sourceforge.net).
  This will enable all other developers to take notice of your work.
• Be prepared to work with a co-developer.
  This will enable knowledge-sharing.
• Discuss your plan or approach or algorithm before you program.
  This enables other developers to see the impact of your actions on other parts of the program. Also you may get valuable feedback on your ideas, leading to less errors and bugs.
• Publish your work as often as you can
  By using the CVS mechanism of SourceForge you can upload your code often, even if it still is not finished. This enables others to collaborate on programming and testing. I propose that after you have changed a function or class you upload it immediately, or at least on the same day.