GlassFish Documentation: Written by the GlassFish Doc Team

A big thanks to the FishCAT members (aka "FishCATs") who tested GlassFish v3 Prelude documentation. Of the 117 bugs, RFEs, and comments filed during the FishCAT program, 25 of those were for docs – pretty impressive! Those doc reports came from the following people (and my apologies if I missed anyone – please let me know if I did) :

• Kristian Rink
• Dick Davies
• Preetam Deshpande
• Sebastien Dionne
• Kanae Kotake
• Madhavi
• Manfred Riem
• Wolfram Rittmeyer
• Shinsuke Takeuchi
• Wim Verreycken
  

Thanks very much for your time and dedication, which were evident in the many exchanges on the quality mailing list (just look at August and September!) and in the final results. You directly improved the quality of the docs and the overall quality of the GlassFish v3 Prelude release by:

• Reviewing the guides, flagging errors and providing suggestions for improvement.
• Performing procedures and examples, verifying their accuracy and completeness.
• Testing the online help, cross-checking it against the GUI and identifying places where explanations were unclear or information was missing.
• Reviewing the man pages, testing commands and verifying the correctness and completeness of the content.

What's even more impressive is that you did all this work as unpaid volunteers (well, not counting the T-shirt), fitting it in with real jobs and school and everything else that keeps life busy. And even though the FishCAT program is officially "over" for GlassFish v3 Prelude, you're still working away – testing builds, reviewing docs, filing issues. Community at its finest.

This was the first round of FishCAT, and as with any new thing there's always room for improvement. We're thinking about that on the docs team, and would love to hear your thoughts as well. What worked and what didn't for FishCAT doc testing and review? What would you like to see done differently next time around? Any and all feedback would be greatly appreciated. Just leave a comment on this blog or send an e-mail to the docs team. And thanks again for a job very well done.