GlassFish v3 Documentation Planning Minutes - 5/22/08 Main meetings page
\ Attendees Dixie, Gail, Ian, Paul, Debbie, June, Jennifer
\ Agenda
- Review of AIs - Paul
- Status of Glass Fish v3 User Task Analyses - Paul
- Status of deliverables
- Quality improvement measures for the v3 doc set
- Open mic - All
- Next meeting - All
\
Meeting Notes 1. Review of AIs - Paul
-
- Paul:* Find out if TP2 is going to be turned into an FCS-quality developer release. IN PROGRESS - still being discussed (but likely)
- Paul:* Start a SolBook rules page. DONE - feedback incorporated, sent for final review (due 5/23), will then send pointer
- Paul:* Create a wiki page and add ideas to it for quality improvement measures for the v3 doc set. IN PROGRESS - created GF wiki page, refining it before announcing to the community
- Paul:* Look at list of new features and propagate into the Glass Fish v3 User Task Analyses table. NOT STARTED - lower priority
- Book owners:* Look through your books, identify task brainstorming sessions that would affect your books, send list to Paul. AMEND AI: Rather than sending to Paul, add them to the table of potential brainstorming sessions. Details: If you're listed in the doc plan as an owner, look through your book, identify existing topics that might also warrant task brainstorming sessions. New features get highest priority, followed by existing features that are most commonly used.
- Book owners:* Add a link from each task in the task analysis page to the explanation of the task in the doc set.
If the task isn't going to be doc'd because it's out of scope, mark it as such; if the task is something we're going to doc but just haven't gotten to yet, leave as-is; we'll assess later whether items should be moved to the Community Docs wish list. NOT STARTED
\
2. Status of Glass Fish v3 User Task Analyses - Paul
Features might be added to TP2; these would be the highest priority for task brainstorming sessions; otherwise the focus would be on the Beta release milestone.
\ 3. Status of deliverables:
- June working on some updates to Dev Guide (EJB 3.1 and classloaders info); drafts out for review; hopes to wrap up 2 new chapters by the end of next week; will republish on docs.sun.com
- Paul updating installation instructions for TP2
- Dixie updating task list for Admin Guide
- Jennifer updating JRuby doc to accommodate post-JavaOne reviews; will republish on docs.sun.com
- Paul will republish the collection to push revised Dev Guide and JRuby doc; work with him on the specific timing of that
\
4. Quality improvement measures for the v3 doc set
Revisit after wiki page is created
\ 5. Open mic - All
Any special procedures for sharing books? In general:
- When there are multiple writers, apportion the work so writers don't need to work on the same files at the same time.
- If someone needs to make book-level changes, give that person exclusive control of the book for a specified period of time, during which everything is back in the team workspace and nothing's touched until the book-level owner gives the OK (also, it's helpful if the primary book owner runs 'cleanup entities' periodically).
- File merging operations on sgml files are fraught with danger - consider them carefully and ask Paul for assistance if unsure!
- Bottom line: If possible, no chapter should ever be worked on by more than one writer at the same time. If multiple writers must work on the same chapter simultaneously, consider chunking up the chapters into smaller file entities.
\
6. Next meeting - All
Thursday 5/29 2-3 PM PDT
\ Main meetings page
|
