Hi, On short term and development wise I think we need to formalize and ease different development the processes. The first thing to do would be to organize the work so define a few project and make sure every commit is related on one of those projects (cleanup, DAP support, openocd as lib...).
Make the work visible this can be as simple as a mailing list with the connits in there or a review system like google code uses. I am not per-see for a git based system as this makes it harder to get a common base but I use git to track openocd to do my own little stuff and it works very well for me. Change the tone on the list and be more careful. Since a few week's just around Zach's arrival I have not been able to enjoy working on openocd. Populate IRC and join the irc on #openjtag on freenode. This will also help understand the problems users are facing. They usually still are in full confusion about the configuration changes. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
