To help with cooperation between developers there is a subproject called Tasks set up in Mantis. It contains a list of issues that developers think need to be done, sort of like a shared TODO list. It allows writing ideas for changes or additions so that other developers can see them. Plus, if the developer that added the task doesn't have sufficient time to accomplish it other developers can complete it. The list is viewable by everyone, however only developers are able to add and update the issues.

Tasks differs from the main Double Commander category in that it contains reports directed towards internal changes in the code (implementation) rather than what the user can experience.

General pointers on how to create issues:

1. Don't create entries for issues already reported in the bugtracker, either as bugs or feature requests. You can assign yourself to that issue there.
2. The list should contain issues about specific implementations of features, such as internal structures, algorithms used, etc.
3. If you're not sure about adding an issue discuss first on the mailing list or on the forum with other developers so that consensus can be reached on how to proceed. Having said that, issues can be always later resolved as Won't Fix or No Change Required.
4. Try to add as much detail as possible on how you see the issue implemented so that you don't forget and others can read. The creation of issue should be treated as a first draft which can be later changed in its entirety.
5. There are some custom fields added that you should specify whenever possible:
• Workload - to estimate how much work an issue would require; if you cannot estimate leave Unspecified
• Operating system
• Widgetset
• Architecture
If an issue is not specific to certain choice(s) (for example is for all widgetsets or all operating system) then don't check any items.