Hi Folks,

I also agree that better bug tracking is needed, although I am not sure that
SourceForge should be the repository for bug reports.

I have never worked with SourceForge, indeed I don't even have the slightest
idea how to go about using it, but I have used three successful electronic
bug tracking systems over the past 6 1/2 years at my current company.  All
of these systems have been home grown; the most recent incarnation is
implemented on Lotus Notes.  This system is used daily by several hundred
employees of my company and has proven to be an invaluable tool for keeping
everyone on the same page.

I don't really care what is used on the back end, to hold onto the problem
reports, but I do think that users should be able to get at them from
Squeak, if Squeak is on-line.  If Squeak is off-line, it should know how to
generate files that represent bug reports that can be uploaded to the bug
repository.

Since I have used several bug tracking systems, successfully, on a daily
basis for a long time, I suppose I could come up with a list of requirements
for such a system -- if somebody has interest in developing it.  I don't
have that kind of free time.

Let me know if y'all would like me to type up a suggested feature list.  Of
course, any requirements that I put forth are merely "suggestions"...  I
don't want anybody to think that I'm an authority on this subject.

Cheers,

---==> Chris