Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "RequirementsCouncil06TP"

Line 1: Line 1:
 
== Timeline ==
 
== Timeline ==
 
This is the discussed at the March 2006 Requirements Council meeting at EclipseCon.
 
This is the discussed at the March 2006 Requirements Council meeting at EclipseCon.
* 2006 – Late April – Team email on “key themes/trends” that matter (Collaborate
+
* 2006 – Late April – Team email on “key themes/trends” that matter (Collaborate on the WIKI if technically possible to keep within the council)
on the WIKI if technically possible to keep within the council)
+
 
* 2006 – Early May – Conference call re: email brainstorm, first draft for council
 
* 2006 – Early May – Conference call re: email brainstorm, first draft for council
 
* 2006 – June – Council meeting
 
* 2006 – June – Council meeting
* 2006 – July – Requirements council delivers “DRAFT: themes and priorities”,
+
* 2006 – July – Requirements council delivers “DRAFT: themes and priorities”, with preamble (or some cool name for this) i.e.,”mid course planning advice”, “areas of focus” or “trends and recommendations”. Plus – each theme streamlined and “why this theme is important”
with preamble (or some cool name for this) i.e.,”mid course planning advice”,
+
“areas of focus” or “trends and recommendations”. Plus – each theme
+
streamlined and “why this theme is important”
+
 
* 2006 – September – Members at meeting get interactively involved in themes v3
 
* 2006 – September – Members at meeting get interactively involved in themes v3
 
*  2006 – October – Council meeting
 
*  2006 – October – Council meeting

Revision as of 11:48, 23 May 2006

Timeline

This is the discussed at the March 2006 Requirements Council meeting at EclipseCon.

  • 2006 – Late April – Team email on “key themes/trends” that matter (Collaborate on the WIKI if technically possible to keep within the council)
  • 2006 – Early May – Conference call re: email brainstorm, first draft for council
  • 2006 – June – Council meeting
  • 2006 – July – Requirements council delivers “DRAFT: themes and priorities”, with preamble (or some cool name for this) i.e.,”mid course planning advice”, “areas of focus” or “trends and recommendations”. Plus – each theme streamlined and “why this theme is important”
  • 2006 – September – Members at meeting get interactively involved in themes v3
  • 2006 – October – Council meeting
  • 2006 – December – Council meeting, and Board approved Roadmap

v3

Brainstorming

Back to the top