Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-requirements-council] Agenda for Next Tuesday's Meeting
All,
 
Here is a strawman proposal for our Requirements Council meeting next week. This is based on the minutes of the phone call held in late April provided to me by Bjorn and which are attached.
 
0800-0830: Continental Breakfast
 
0830-0845: Intros, getting started
 
0845-0930: The Roadmap Process (Mike Milinkovich)
We have quite a few new members. Taking the time to go back over the requirements process would be useful to the new folks. Some time will also be spent going over the existing Roadmap Themes and Priorities.
0930-1015: Enforcement: Who gets to wear the sherriff's badge in an open source world?
There is lot's of talk about "...how can we enforce policy X, Y or Z in an open source world?". The answer in genera=[' is we can't. And the Requirements Council's role is not to dictate to the open source projects. That said, Eclipse is an experiment in gently nudging open source projects to behave in an altruistic manner for the greater good of the overall community. What can we reasonably accomplish at Eclipse, and what can the Requirements Council tangibly do to help this process?
1015-1030: Break
 
1030-1100: Synchronizing Releases and Release Numbers
The major releases should be synchronized or at least have synchronized numbers. One view is: "The projects should give lots of information in advance about when the various releases will occur so that members can base their technology on full synchronized stacks." The projects have actually been doing pretty well, with many releases shipping close together. What the RC ask them to improve?
1100-1200: Process Discussion
Define the process for tracking requirements through from the RC through to the final deliverables. It must include Bugzilla and the Road map.
1200-1300: Working Lunch

1300-1400: Quality
What should it mean to have the Eclipse brand attached to a project? What are the quality requirements? How proactive should we be? How can we enforce this in an open-source project? What role does the RC have in establishing quality objectives for Eclipse projects?
1400-1500: New Projects
What sort of requirements should we have for new Eclipse projects? We want to keep our process light and quick and not become just another JCP.  We also want to keep our process heavy and not become just another SourceForge. What's the right balance?
1500-1515: Break
 
1515-1615: Roadmap Redux
Gather requirements and themes and priorities. Define the process by which they will be gathered. Are there any changes from the existing road map. Both shorter term (3.2) requirements and longer term "where is Eclipse going" requirements.
1615-1645: Wrap-Up
Action items
Discuss whether we should have monthly phone calls, and how we can make them useful
Discuss goals for the plenary session on Wednesday morning
 
 
Comment:
 
The astute observer will have noticed that there were certain topics not included in the agenda. In most cases this is because the Foundation is discussing the topic with its Board. And in most cases, they get first crack at solving the problem.
 
 
 
Mike Milinkovich
Executive Director,
Eclipse Foundation, Inc.
Office: 613-224-9461 x228
Cell: 613-220-3223
mike.milinkovich@xxxxxxxxxxx
 
blog: http://milinkovich.blogspot.com/
 

Attachment: RC Minutes 05.04.26.doc
Description: MS-Word document

Back to the top