Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Fx2 Planning Centre (was PRD review)
2 views
Skip to first unread message
Mike Beltzner
Mar 23, 2006, 6:15:55 PM3/23/06
to bonecho, dev.planning
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.
Chris: would you be able to start updating the wiki?
cheers,
mike
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.
Chris: would you be able to start updating the wiki?
cheers,
mike
Ben Goodger
Mar 23, 2006, 7:39:21 PM3/23/06
to Mike Beltzner, dev.planning, bonecho
How do folk with questions like Rob Strong's etc submit feedback? Do
they just edit the document?
they just edit the document?
> _______________________________________________
> BonEcho mailing list
> Bon...@mozilla.org
> http://mail.mozilla.org/listinfo/bonecho
>
Mike Connor
Mar 23, 2006, 7:48:30 PM3/23/06
to
I think whatever group/list we're using for discussing planning issues
would be the right place to submit feedback/propose changes. If we're
going to consolidate planning discussion, let's do it right.
would be the right place to submit feedback/propose changes. If we're
going to consolidate planning discussion, let's do it right.
-- Mike
Ben Goodger
Mar 23, 2006, 8:31:15 PM3/23/06
to Mike Beltzner, dev.planning, bonecho
The talk pages are pretty horrible for any kind of serious trackable
discussion. Why reinvent the email wheel?
discussion. Why reinvent the email wheel?
-Ben
On 3/23/06, Mike Beltzner <belt...@mozilla.com> wrote:
> (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.
>
> Or in these groups.
>
> Sensible?
0 new messages