Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Requirements Council"

Line 1: Line 1:
 
The Requirements Council has three main responsibilities:
 
The Requirements Council has three main responsibilities:
* Drive the evolution of the [[Eclipse Themes and Priorities which serve three main purposes:
+
* Drive the evolution of the [[RequirementsCouncilThemesAndPriorities
 +
| Eclipse Themes and Priorities]] which serve three main purposes:
 
** Drive the creation of the Eclipse Road Map, used by the Ecosystem to understand in a snap-shot format the direction and challenges we face
 
** Drive the creation of the Eclipse Road Map, used by the Ecosystem to understand in a snap-shot format the direction and challenges we face
 
** Help projects focus on important issues
 
** Help projects focus on important issues

Revision as of 13:45, 21 August 2007

The Requirements Council has three main responsibilities:

  • Drive the evolution of the [[RequirementsCouncilThemesAndPriorities

| Eclipse Themes and Priorities]] which serve three main purposes:

    • Drive the creation of the Eclipse Road Map, used by the Ecosystem to understand in a snap-shot format the direction and challenges we face
    • Help projects focus on important issues
    • Consolidate terminology used frequently in the Eclipse Ecosystem
  • Maintain a list of, and drive to resolution of, important issues and challenges facing the Eclipse Ecosystem
  • Network with each other and the Ecosystem to consolidate public knowledge involving Strategic Members planned directions with Eclipse technology


Useful Stuff:

Copyright © Eclipse Foundation, Inc. All Rights Reserved.