DdIV makes good points. I have worked in many engineering teams, but never in an online software collaboration team. Also it is pretty certain to say that skill levels vary greatly in this group. And I for one am at the lower end of the scale.

I have thought about it a little bit and would like to suggest a simple model. It is a little rigid, but for starting out it could result in working strategies that people can later alter to suit their individual objectives. Let's assume that the bot concept that dusktrader is developing works out very well. I assume that this code provides all the surrounding infrastructure required to a take full advantage of an 'edge.'

So this leaves the development of out individual ideas of an edge. First, we list all the different areas of trading that we want to test. For example, MA cross, candle patterns, Larry Williams patterns, Turtle / Donchian, range breakout, some idea someone read in a book or website. There can't be many more than a couple dozen. Then each of us take an area that we like, code the edge and apply the bot tools. Maybe we have a private thread for each of the area of trading. That way the person looking at that edge can report to the group and get suggestions. Hopefully, at the end of the thread the person is able to make a post that has code, results summary and other comments.

Finally, people can make suggestions for improving the bot infrastructure code.

The wheel I am trying to avoid each of us inventing is the bot code that covers risk management, portfolio trading, and whatever else is common to every system. Then the collaboration aspect means that we each aren't wasting out time trying to code a single trading concept. And if someone reviews someone else's work, particularly an abandoned concept, and has a spark of genius, then they can continue where the other person left off.

Will have to decide on a few overall concepts, like the risk sizing / position sizing strategy. JCL made public the section of code in the Zs that covers this. Do we want to use this model or have options for others. We may want a second positions sizing code that simply makes 1 micro lot trade size for live testing for a few months.

Also keeping a running list of things to check as we are developing code would be handy. Obviously the compiler takes care of syntax. But common logic errors, setting the right flags such as Weekend, doing a final test with the Tick flag before posting to group, etc.

Summary:
1. We use the bot code as the basic common system infrastructure.
2. We list the areas of trading / edges that we want to investigate.
3. One person takes an edge, creates a thread, codes the edge with the bot code and reports back to the thread.
4. An overall thread is maintained with tips and tricks. Every once in a while someone should summarise the tips and tricks, maybe into an ongoing PDF. Includes the edge areas and the person who is currently working on it.

Actions:
1. Allow dusktrader time and opportunity to prove his bot concept. Possibly some discussion and revision will be required. If the group is happy to proceed on this basis, then….
2. Create a private thread and flesh out the details of how this will work and what edge areas are to be investigated. At this point we will need a project leader type person to manage this overall effort. This is simply updating a common PDF with group decided items. The person will need to have a clear vision for the initiative. Hence a champion to keep the idea alive during times when people are distracted with the rest of their life.