|
From: Bryan M. <om...@br...> - 2006-09-07 22:05:39
|
Well, as a developer of an external tool, I am both really excited and intimidated at the same time. >From a development point of view, keeping Omega out of subversion hasn't hurt at all. I simply got a clean checkout of valgrind, svn added my code and directories as I went along and occasionally push out a diff to the tree with 'svn diff . VEX > file.patch'. People are downloading the patch, applying it, giving Omega a try and some are reporting bugs back to me (no success stories outside of my office yet but there must be at least one out there :D). The intimidating bit is that with Omega in Valgrinds' subversion repo, even when marked experimental and all the rest of it, there will be an increased expectation. It's either going to be a very positive experience or people are going find bugs, grow to hate it and then it wont get used due to a lousy reputation. This is on top of the extra visibility which on the one hand I want Omega to have (it's a really good tool when it works as it should) but on the other hand, being just me at the moment, I don't know if I can support it properly in the face of a sudden influx of users. There should definitely be some additional hurdles to inclusion though - I keep asking people to post reports to the list as well so you can all see some traffic as this shows that there is some user base forming that has an interest in the tool, rather than it just being a weekend hobby project. The other thing would be being able to show some progress against stated functionality. That gets difficult though - I have run Omega on some massive codebases at work without any problems whereas a couple of my bug reporters got it to die with embarrassing ease (fixed now - honest). I suppose this is another case where being able to show a community forming around a tool would give some confidence that it is actually doing something that others find useful. I am certainly willing to be a guinea pig on this if you want to add Omega in the first batch. (Omega has two small VEX tweaks that you might want to consider before inclusion). If I get swamped with bug reports and feature requests and end up having a nervous breakdown trying to work through them all then maybe you will have to rethink things before the next tool comes along :P Bryan Nicholas Nethercote wrote: > On Thu, 7 Sep 2006, Josef Weidendorfer wrote: > >> Currently, a VG tool author can distribute his/her tool by >> (1) convince VG core authors to include it into VG package >> (2) hack a VG source distribution to include his/her tool, thus >> distributing a customized Valgrind package >> (3) distribute an external VG tool package >> [...] >> IMHO, it is worth it because (3) lowers the barrier for new tool authors >> by giving them choice. And exposure also is possible by naming external >> tools on the web site. > > Sure, keeping open (3) as a possibility is a good idea. What the new > policy does is allow (1) in addition to (2) and (3). > > Nick > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |