| <html> |
| <head> |
| <link rel="stylesheet" href="../../default_style.css"> |
| <title>Eclipse Foundation</title> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <style type="text/css"> |
| <!-- |
| .style1 { |
| color: #FFFFFF; |
| font-weight: bold; |
| } |
| --> |
| </style> |
| </head> |
| |
| <body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000"> |
| <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" height="129" > |
| <tr> |
| <td ALIGN=LEFT width="71%"><font class=indextop>Minutes: Eclipse Members Meeting </font><br> |
| <font class=indexsub>Eclipse Members </font></td> |
| <td WIDTH="29%"> </td> |
| </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr> |
| </tr> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><span class="style1">eclipse members meeting </span></td> |
| </TR> |
| <tr> |
| <td> |
| <p align="center"><br> |
| Eclipse Members Meeting<br> |
| October 27, 2004, Dallas, Texas</p> |
| <p><b>Updated November 18th</b> to include voting results table.</p> |
| <h3>Attendees</h3> |
| <p>The list of attendees is provided <a href="AttendeeList.pdf">here</a>. </p> |
| <h3>Minutes</h3> |
| <h4>Executive Director Report</h4> |
| <p>Mike Milinkovich started the meeting with his Executive Director Report. A |
| copy of his presentation can be found <a href="ExecutiveDirectorReport.pdf">here</a>.<br> |
| </p> |
| <h4>Open Source Project Review</h4> |
| <p>Mike Milinkovich reviewed the status of the Eclipse top-level projects. A copy of his presentation can be found <a href="EclipseProjectUpdate.pdf">here</a>.<br> |
| </p> |
| <h4>Detailed Project Presentation - BIRT</h4> |
| <p>Paul Clenahan from Actuate introduced the Business Intelligence and Reporting project to the attendees. His presentation can be found <a href="EclipseBIRTProjectIntroduction2004-10-27.pdf">here</a>.<br> |
| </p> |
| <h4>Add-in Provider Requirements Session</h4> |
| <p>Todd Williams and Rich Main (Eclipse Add-in Provider Board Representatives) |
| lead a session to develop a list of themes and priorities from the perspective |
| of the Add-in Provider community. This list will be used as input into |
| the Requirements Council.</p> |
| <p>The process followed to develop the list of themes and priorities was as |
| follows:<br> |
| </p> |
| <ul> |
| <li>Rich Main led a brainstorming session to identify potential topics for break-out groups. 8 topics were identified: |
| <br> |
| <ul> |
| <li>Abstract Language Developer Toolkit</li> |
| <li>Business Intelligence and Reporting</li> |
| <li>Embedded</li> |
| <li>Marketing</li> |
| <li>Rich Client Platform</li> |
| <li>Testing and Performance</li> |
| <li>Web Tools Project<br> |
| </li> |
| </ul> |
| </li> |
| <li>Two sets of four break-out groups were given 1 hour to develop a list of requirements for the given topic. Each attendee could select which break-out group they would participate in. </li> |
| <li>All the break-out groups reported back and presented their list of requirements.</li> |
| <li>Each person was allowed to vote on their priority requirements. The process of voting was done by allowing each attendee 25 points that could be allocated across all the different requirements. All the votes were then tabulated to come up with the final list of priorities.</li> |
| </ul> |
| <p>The prioritized list is as follows:</p> |
| <ol> |
| <li>Raise awareness of Eclipse at CIO level<br> |
| - Success reports/stories</li> |
| <li>Market Research<br> |
| - Market size<br> |
| - Market profile</li> |
| <li>Abstract Language Toolkit<br> |
| - Editor<br> |
| - Debugger<br> |
| - Build</li> |
| <li>Better componentization in different DTs as many embedded project are multi-language and to enable easier plug-ins for specialized components (debuggers, managed builds, editors)</li> |
| <li>Reduce inconsistency among OS platforms</li> |
| <li>Enterprise Deployment<br> |
| - JNLP integration<br> |
| - Enterprise Update Manager<br> |
| - Managed updates<br> |
| - scalable Update Manager (mirrors/ BitTorrent)<br> |
| - push updates<br> |
| - license managed </li> |
| <li>Basic web-services tools<br> |
| - UDDI browser <br> |
| - XSL/T editor <br> |
| - WSDL tools</li> |
| <li>Support for common reports<br> |
| - listing reports<br> |
| - sorting, grouping, aggregation<br> |
| - crosstab reports<br> |
| - freeform reports (e.g., invoices)<br> |
| - charts</li> |
| <li>Eclipse pug-in certification service (through external service providers) </li> |
| <li>User interface improvements<br> |
| - SWT/JFace improvements<br> |
| - Improved SWT/ Swing interop.<br> |
| - More native hooks into Windows</li> |
| <li>Authentication/ Security<br> |
| - User authentication and credentials<br> |
| - Role-based security<br> |
| - Role-based plugin loading </li> |
| <li> Ease of use<br> |
| - be productive in 15 minutes</li> |
| <li>RCP Scalability<br> |
| - minimum runnable RCP and Update Manager<br> |
| - full IDE with complete hide/reveal (e.g., "Build") </li> |
| <li>Scalability</li> |
| <li>Unified View/Editor framework<br> |
| - Editor embedded in editor<br> |
| - Key bindings<br> |
| - Toolbar management</li> |
| <li>Abstract server definition</li> |
| <li>Expose capabilities and services through interfaces that can be accessed independent of CDT, JDT, etc.</li> |
| <li>More generic ways to connect to "targets" and launch applications. Run tests, run tools and gather data, etc.</li> |
| <li>Provide an interface that allows an additional agent to be used for data collection (i.e., for embedded devices)</li> |
| <li>Refactor data-tools and web-services feature-sets into separate development projects.</li> |
| <li>Eclipse package integration</li> |
| <li>Data Query APIs should be separate project<br> |
| - enables query features to be used by other tools</li> |
| <li>Concentrate more on extensible frameworks than end-user tools</li> |
| <li>Testing - need a universal client</li> |
| <li>Deployment to local and remote servers</li> |
| <li>TPTP/ Hyades should abstract ways to do tracing of hardware (at chip level), not just software tracing</li> |
| <li>TPTP/ Hyades should look at monitoring of deployed embedded systems (in addition to enterprise)</li> |
| <li>DT should abstract debugging more for hardware capabilities</li> |
| <li>JSR-88 compliance for J2EE deployment </li> |
| <li>Meta-information use for EJB developers.<br> |
| - EJB-3 metadata annotations<br> |
| - XDoclet support</li> |
| <li>EJB universal client</li> |
| <li>Improve transparency of architecture and requirements processes </li> |
| <li>Do not preclude other runtimes<br> |
| - J#</li> |
| <li>Clear market messaging/positioning for BIRT<br> |
| - BIRT is a new space for Eclipse</li> |
| </ol> |
| <br> |
| Detailed results of voting scores are <a href="Add-In%20providers%20requirements_0.pdf">available |
| here (.pdf) </a> |
| <h4><br> |
| Market Research Proposal</h4> |
| <p>Wayne Madden of Penton Media presented a proposal to have Penton conduct a market research study on the use of Eclipse.<br> |
| </p> |
| <h4>Marketing Report</h4> |
| <p>Ian Skerrett reviewed the current marketing activities around Eclipse. A copy of the presentation can be found <a href="MarketingUpdate.pdf">here</a>.</p> |
| <h4>Membership Report</h4> |
| <p>Skip McGaughey updated the attendees of the membership and recruitment activities. A copy of the presentation can be found <a href="MembershipUpdate.pdf">here</a>. </p></td> |
| </tr> |
| </table> |
| <tr> |
| <td> </td> |
| </tr> |
| <p> </p> |
| |
| <p></p> |
| <p></p> |
| </body> |
| </html> |
