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

Requirements Council

Revision as of 09:49, 4 October 2011 by Wayne.eclipse.org (Talk | contribs)

Important.png
The Requirements Council, due to changes in the Eclipse Foundation's Bylaws in 2011, is now defunct.


The Requirements Council has three main responsibilities:

  • Drive the evolution of the 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:

[http://www.eclipse.org/org/councils/20070122RC_Serena.pdf Serena Member Presentation, January 22, 2007 (.pdf)</a> [http://www.eclipse.org/org/councils/20061010RCMinutes.pdf Requirements Council Meeting, October 10, 2006 (.pdf)</a></li> [http://www.eclipse.org/org/councils/20060628RCMinutes.pdf Requirements Council Meeting, June 28, 2006 (.pdf)</a></li> [http://www.eclipse.org/org/councils/20060319RCMinutes.pdf Requirements Council Meeting, March 19, 2006 (.pdf)</a></li> Requirements Council Meeting, August 24, 2005 Requirements Council Meeting, November 30, 2004 (.pdf) Requirements Council Meeting, August 31, 2004 (.pdf)

This page is moderated by the EMO.

Back to the top