Re: Older QC reports

"Doug Chamberlin" <dougchamberlin at earthlink dot net> wrote in message news:474598b2$1@xxxxxxxxxxxxxxxxxxxxxxxxx
After about 3 months it was finally posted to the internal db. After
about 6 months a result of "will not fix" (or something similar) was
posted. I gave up watching it at that point.

So because of one bug that did not get addressed correctly early in the development and acceptance phase of QC, you do not intend to ever allow for the possibility that, for the most part at least, it works well?

There are still lots of older reports that have not been addressed, that is true, but there are far less than there was because there *has* been much increased participation from both customers and CG staff since its inception and an explicit effort to address many of the older reports (it very naturally took some time to really start becoming effective, but that is already quite a while ago now - again that depends on participation).

Here's a good example: I heard about the QC SYSOP opportunity and
thought, "OK, that's one way to contribute in a positive way!" so I
went an looked into it. I was immediately turned off by the elaborate
system of levels and what you had to go through to be accepted into the
ranks of volunteers. Too much like a real job interviewing process. Big
turn off.

Well, so far, about 230 others didn't find that such a big deal. What exactly bothers you about the expectations for being a SYSOP? Is it not reasonable to expect *some* commitment for participation and some standards for doing the work? What good would it do to have 1000 sysops if 900 of them did not improve the level of the reports in the system, or didn't do due diligence (reproducing a bug before promoting it) or just opened everything they looked at?

--
Wayne Niddery - Winwright, Inc. (www.winwright.ca)

.

Relevant Pages

  • Re: Older QC reports
    ... know which of the Delphi guys are lead engineer. ... I was a QC sysop for roughly a year and a half before taking this ... The percentage of reports open and closed were ... QC's reputation gets better, more folks will be using it, so it's going ...
    (borland.public.delphi.non-technical)
  • Re: What to do when QC admins dont have knowledge to open a spesific report..
    ... So you can stop asserting that reports haven't been marked as ... >> needing attention when in fact they have? ... >> that, you know, and it doen't require any new features in QC. ... You don't need to be a sysop, and QC doesn't need any new ...
    (borland.public.delphi.non-technical)