Allen Fisher unofficially wrote (among other pearls): > These guys and gals are overworked. Give 'em a brake. They're just > trying to do their job, and remember, they *are* on your side. Making > sure that any and all problems that customers report are reported and > fixed as high priorities is in their best interest, because it makes > their job a hellova lot easier. I really hope you all take this to > heart, I know that they appreciate polite, clear, consise emails about > issues--I know I certainly did.
Dear co-users of Finale Notation Program After carefully reading these unofficial advices: I hereby propose to use the most appropriate and exquisite style when preparing bug reports for submission to FinaleMusicCoda Guidelines: 1) Use of language: As clearly stated by Mr. Fisher the reports have to be: Polite Clear Concise i.e. PCC The amount of politeness, clearness and conciseness should be proportional to the infecting power of the bug (more important = more PCC) Remember: PCC 2) Only a bug report shall be allowed per customer per year, to avoid overworking pressure on the guys and gals. If one user do so by mistake or by malicious behaviour, he or she will be downgraded to Finale 2.0 until he or she repents publicly. 3) Write with optimism about the bug and don�t ever mention Finnish composers in the text of the bug report. I hope you find these guidelines useful for your future. Javier Ruiz. _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
