Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-requirements-council] Requirements Council conference call Tuesday April 26th 10am PDT, 1pm EDT, 7pm CEST
Reminder: there is a Requirements Council conference call Tuesday, April 26th 10am PDT, 1pm EDT, 7pm CEST. The call-in numbers have changed to: 
   613.287.8000
or   866.362.7064
pass code 874551#
The main purpose of this call is to set the agenda for the May 17-18 Requirements Council meeting in Portland, Oregon. To quote from the Eclipse Development Process document, the purpose of the Requirements Council is to "review and categorize all the incoming requirements from all residents of the Ecosystem" and that "there will always be more requirements than resources to satisfy them: 

   * Requirements that advance the Eclipse Foundation towards the
     achievement of its Purposes
   * Requirements that advance specific Projects
   * Requirements that satisfy the needs of the Membership at Large
   * Requirements that grow the Ecosystem"

Agenda for this call:

*Logistics*

   * Reminder to make your hotel reservations for the Council meetings
     in Portland
   * Review of the Council meetings schedule: Tuesday all-day is the
     Requirements Council meeting; Wednesday morning is the plenary
     meeting with all three Councils for the Requirements Council
     members (especially the Strategic Consumers) to present and
     explain the requirements.

*Agenda for the May Council Meeting*
Note that this call is mostly about the agenda for the Council meetings, not so much the actual discussion. We should add these items to the agenda for the meeting if anyone on the call thinks it is important. We probably should not spend too much time on the call discussing the pros and cons - just whether we need to bring the item up in Portland. 

   * Add to the Council agenda: how to track requirements from the
     Council through to the deliveries from the projects.**
   * Add to the Council agenda: a request that major releases be
     synchronized, i.e., all the 3.1 releases occur on the same day.
   * Add to the Council agenda: start gathering the Themes and
     Priorities for the next Roadmap.
   * Add to the Council agenda: gather and distill requirements to pass
     to the projects.
   * Add to the Council agenda: a request that projects keep their
     consumers aware of commitments and changes to commitments.
   * Add to the Council agenda: an explicit statement of one major
     release per year and one patch set per quarter.
   * Add to the Council agenda: enlisting the community in
     globalization of Eclipse projects
   * Add to the Council agenda: what should it mean to have the Eclipse
     brand attached to a project; what are the quality requirements?
   * Add to the Council agenda: strategy for dot-NET tooling and for
     dot-NET <-> RCP interoperability.
   * Add to the Council agenda: when Eclipse was smaller, it was
     focused on the "nothing but Java" developer. Now Eclipse is more
     so we need to decide how much effort to continue focusing on the
     "nothing but Java" franchise versus how much effort we should
     invest in branching out to other areas.
   * Add to the Council agenda: what kind of requirements should we
     have for new Eclipse projects? Should we categorize the projects
     (top-quality, tool-quality, technology-exploration, research, ...)
     and have different quality/entrance/exit/etc requirements for
     each? How are these requirements going to be communicated?
   * These are just my list of Council meeting agenda items; I'm sure
     you'll have many more so we will gather them and add them to the
     Council agenda.

*A Few Action Items*

   * The penultimate agenda item for this call is to sort the Council
     meeting agenda in priority order.
   * The final agenda item for this call is to assign homework for the
     various agenda items. The goal is for selected Council members to
     come to the Council meetings with background information on each
     agenda item so that the discussions at the meeting can be focused
     and productive.

--
*Bjorn Freeman-Benson*
Technical Director, Open Source Process and Infrastructure
Eclipse Foundation <http://www.eclipse.org/>
voice:  	971-327-7323 (PDT, GMT-8)
email: bjorn.freeman-benson@xxxxxxxxxxx <mailto:bjorn.freeman-benson@xxxxxxxxxxx>

Back to the top