Daug Way wrote:
> Here's my longish random list of improvements I'd eventually like to 
> see with BFAV2 (I could help with some of these if necessary)...
> 
snip
> 
> - Include the author name in the first post in a group, something like: 
>   [FIX] DicAddAll-OK -- ok at cs.otago.ac.nz (17 December 2003)
> 
> - (nice to have) Include (*) or some indication in the archivepost 
> subject that an attachment exists for this post.  Probably would 
> require a change in the bfav server?
> 
> - Improve UI wording where possible to make things easier for 
> first-time users... for example, instead of "open comments note pad" 
> (why would I need a "note pad"?) change it to something like "review 
> this bug fix" or "comment on this bug fix".
> 
> - Change "reviewed", "tested", etc. checkbox labels in CommentsNotePad 
> to "reviewed [er]", "tested [et]", etc.  This ties things together 
> better.  Alternatively, we could just get rid of the obscure 
> abbreviated tags ([et] [er] [su]) altogether and instead generate fully 
> spelled out tags ([externally tested] [externally reviewed] [sunit]) or 
> maybe ([ext tested] [ext reviewed] [sunit]).  Since the tags mostly 
> just go through BFAV and not squeak-dev anymore, there's not as much 
> need to abbreviate them.
> 
> - Add more specific balloon help for CommentsNotePad.  Help text for 
> the summary contents pane could say "Enter brief summary contents (like 
> 'Needs tests').  This will appear in the subject line for the comment 
> post."  And the detailed contents pane help could add something like: 
> "... This will appear in the text for the comment post."

I agree with Doug on these changes, they improved the understanding of BFAV for a
beginner.

Ray