One feature I like with the new version of IE with the tab browsing, it will allow you to view every tab in like a summary, if the feature could be built into firefox I believe it would go over with great fanfare. I am including an image attachment to show you what I mean.
Scott Davis, MCP
(Office) 717.432.7766 x.45
This message, including any attachments, contains confidential information intended for a specific individual and purpose and is protected by law. If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this email. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
From: [hidden email] [[hidden email]] On Behalf Of Mike Beltzner
Sent: Thursday, March 23, 2006 8:05 PM
Cc: dev.planning; bonecho
Subject: Re: Fx2 Planning Centre (was PRD review)
(top-posting 'cause Blackberries suck that way, sorry)
I think the talk documents might be a better way, since it lets us discuss rationale for changes, and then we can track the debate and arrive at decisions together at next week's meeting.
How do folk with questions like Rob Strong's etc submit feedback? Do
they just edit the document?
On 3/23/06, Mike Beltzner <[hidden email]> wrote:
> Based on the feedback received about the structure of the existing PRD, it might be better to split the document into various sections that more clearly call out the different purposes of the planning documentation.
> Why don't we ..:
> - use wiki.mozilla.org/Firefox2 as the bon echo planning centre (really, we've been doing this all along)
> - unlink the PRD, and beak it up into bits as described below
> - take the first sections of the PRD on goals, vision, and mission of the project and put it in a section called "Project Goals and Objectives"
> - replace the "Features" section with a "Requirements" section based on the PRD, but without owners; just a list of prioritized requirements. Provide links to tracking bugs for each requirement, and as Chris H suggested, tie those into a master tracking bug for Bon Echo.
> - replace the "Schedule" page with the updated content from the PRD
> - replace the "Release Criteria" page with the updated content from the PRD
> - get to reviewing the requirements and scheduling sections asap, with the goal of finalising at next week's Bon Echo meeting.
> - continue to cross post between bonecho@ and dev.planning until we can work out list migration issues later this week or early next week.