Garrett D'Amore wrote: > Stephen Lau wrote: >> We've got an existing DTS evaluation going on - it's floundering not >> because Sun is holding anything back, but because nobody is making the >> effort to evaluate any of the DTS (or at least they haven't mentioned >> it publicly). >> > > There is another real problem here. I think the only people who are > qualified to "fully" evaluate the bug database are those who are also > Sun employees. Why? Because only they really know what the current > bugster contains, and what features are needed, and what aren't. > > Of course, all the Sun employees I know are up to their neck in other > work. And it isn't entirely clear that the Sun folks who should be > paying for an evaluation of a new DTS have any motivation to do so; > after all, bugster works just fine for *their* purposes. > > Speaking for myself, I don't have the time to do a full evaluation of a > DTS. And, I'm not really qualified as a DTS administrator. *HOWEVER*, > I know that I would be willing to play in a sandbox that someone else > built. And even use it to track real project bugs. I *suspect* that > the same is true of other people. > > So, if someone is energetic enough (a big if, I know) to set up the demo > sandbox, then maybe an announcement in a broader context inviting others > to participate in the test (as developers, not DTS administrators!) > would be helpful.
Good points Garrett, but I do think there are still some pieces where non-Sun people should certainly be able to help out. We've outlined a specific list of requirements: http://opensolaris.org/sc/src/website/spec/dts-requirements/d-dts-requirements.txt It should certainly be at least possible for people to help eliminate potential candidates based on whether or not they meet the requirements or not. cheers, steve -- stephen lau // stevel at sun.com | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development
