In article , jn11+@andrew.cmu.edu (Joseph M. Newcomer) writes: > The flaming style of the complaint coupled to the dry-official responses > made this one of the more popular underground memos within DEC. You might be interested in the following form. The title has been changed to protect the product group involved (you know who you are 8-). Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, US terry@spcvxa.spc.edu (201) 915-9381 SPR/QAR/BUG Response Form _______________________________________________________________________________ Maintainer: _______________________ SPR/QAR/BUG No: ____________________ Date: _______________________ Copy to: ___________________________ Description: ______________________________________________________________ Hours Spent: ________ Output Priority: ________ Duplicate? Yes__ No__ _______________________________________________________________________________ Related Article in Software Dispatch? Yes___ No___ Didn't Look___ Attach Seq. No. ________ Patch Checked? ____ No, wait for patch ____ No, take it anyway ____ Yes, but it might not work Patch source cleared? Yes___ No___ Almost___ What's "Source cleared"? ___ If yes, in what versions(?) _______________________________________________________________________________ (Check only ONE) ____ Correction Given ____ Not Reproducible ____ New Patch ____ Reproducible, but tell ____ Existing Patch it wasn't anyway ____ Special Patch ____ Fixed in Next Release ____ Fake patch, won't work ____ Will never be fixed, but but looks good let's be optimistic ____ Unsupported ____ Insufficient Information ____ Used to be supported ____ Suggestion ____ Needs a lot of support ____ User Error ____ Supported until we got ____ R.T.F.M. (Read the F* Manual) this SPR ____ S.F.O. (See Figure One) ____ Hardware ____ Y.F.U.R. (Your Fault for ____ Really software, but using RMS) blame hardware anyway ____ S.L.A.P.P. (Sounds Like A ____ TS11, must be hardware Personal Problem) ____ Inquiry ____ Restriction ____ FYI ____ Documentation Error _______________________________________________________________________________ Problem Statement: ____ Copy entire problem statement ____ Copy indicated part in box below: ----> [] _______________________________________________________________________________ Response: ____ Standard "Fixed by Patch" answer ____ Standard "Thanks for your suggestion, we'll probably do this when hell freezes over" answer ____ Standard "Ha, Ha, you've got to be kidding!" answer