Hi, Julian and I have been discussing for a while the idea of creating a category of "experimental" tools in the Valgrind source tree. These would be tools that are not necessarily mature, but may be of interest to people. This would make it much easier for users to try out experimental tools -- they would be included in the Valgrind distribution -- which in turn might accelerate their development.
The core Valgrind developers would maintain experimental tools at the minimum level of keeping them compiling, eg. if the core/tool interface changes, as it does occasionally. But each tool would have to have a nominated maintainer who would be reponsible for responding to bug reports, feature requests, and who would continue development. These tools would be given an "exp-" prefix to their name to indicate their experimental nature, and they would be marked clearly as experimental on the website and in the manual. Experimental tools could lose the "exp-" prefix once they reached a certain level of maturity and popularity. The tools would have to be licensed as GPLv2-or-later, like the rest of Valgrind. We are interested in hearing people's opinions on this idea. We are also interested to hear if anyone has a tool they would like to be considered for inclusion as an experimental tool. Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
