First off, an apology. I re-read my message, and it came off sounding much harsher than I intended. My primary concern was that I was making the mistake of trying to contribute to a project that was "closed" in some official way. Now I see that it's not, thank you for your measured response.
> It may seem that this particular project is somewhat > less open in some respects, but I believe this is due to > the lack of interest in this project by the community. > Or maybe there's a lack of interest from the community because the project is somewhat less open. I suspect it's a combination, with most of the problem being, as you said, that test harnesses are kinda boring to most people :-) I understand that it's a dilemma. It seems (at first glance) silly to publish ideas to the list, and then be the only voter. But without transparency, new developers will have no way to get up to speed. The other project that went off and developed its own copy of the test suite is a good example. > Since the activity has been so low, I've made the > occasional change to the test driver to make > enhancements and have given thought to changing over to > a new testing harness. > Right. But silly as it seems, the thing to do is share those thoughts with the list, even if you suspect you're the only one listening :-) I've spent time working on GTest (ref my occasional patches and comments over the past couple of months), and I probably wouldn't have done that if I had know there was going to be a move to another harness framework. It's not like I wasted my entire life on it, I bring it up mostly as a minor example, but it is a little frustrating. To keep things at least a little less meta, here's a more concrete request: could you post your thoughts on what's going on with the test harness situation? Should I keep looking at the current setup with an eye to improving GTest? Or should I hold off? -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
