Starting with PTXTool (http://code.google.com/p/ptx-tool/) last week I'm planning to release all my tools as open-source. I chose Google.Code for that.
This grants several new possibilities:
- anyone can view the source and suggest his ideas and improvements
- anyone can download the source and compile it into working EXE with any changes/improvements
- new developers can join the coding team and make tools even better together
- issue tracker - anyone can submit a bug-report and see its status
- all changes to source are stored and thus one can download any version he exactly needs
- every change is logged, that helps to track down bugs
Now this requires some polling since other tools include password protection and making them open-source means that it will be weakened or gone at all. I've tried to find a way to keep passwords secure, but that is impossible:
MTKit2 - Models can be viewed without knowing the password. Passwords only blocks export to other formats. That means one can simple override export function password check.
EditCar - It has nothing in it except loader and saver functions.. putting those to secure DLL effectively equals to keeping whole tool unpublished.
AFC11/FVR Managers - those tools read editcar data irregardless of password presence and put it to games database. Opening these tools means that editcar data can be viewed along the way. Again putting read/merge functions to secure DLLs leaves nothing lefts to open.
STKit2 - this one can go open-source easily for it has no password data in it.
Other tools are hardly worth mentioning.
Discussion is welcome! (please keep it English)