| <?xml version="1.0" encoding="ISO-8859-1" ?> |
| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <title>WTP PMC Minutes for March 8, 2005 Conference Call</title> |
| </head> |
| <body |
| alink="#ff0000" |
| bgcolor="#ffffff" |
| link="#0000ee" |
| text="#000000" |
| vlink="#551a8b"> |
| <table |
| border="0" |
| cellpadding="2" |
| cellspacing="5" |
| width="100%"> |
| <tbody> |
| <tr> |
| <td |
| colspan="2" |
| align="left" |
| bgcolor="#0080c0" |
| valign="top"><b> <font |
| color="#ffffff" |
| face="Arial,Helvetica">PMC Conference Call - March 8, 2005</font></b></td> |
| </tr> |
| </tbody> |
| </table> |
| <table |
| border="0" |
| cellpadding="2" |
| cellspacing="5" |
| width="100%"> |
| <tbody> |
| <tr> |
| <td>Attending: Tim Wagner [TW], Arthur Ryman [AR], David Williams [DW], Dominique De Vito [DV], Jochen |
| Krause [JK], Naci Dai [ND] Others: Lawrence Mandel (representing WTP community) [LM] |
| <h2>Procedural matters time and administration of PMC conference call</h2> |
| <ul> |
| <li>PMC agreed to continue meeting on a weekly basis to ensure timely review of all WTP matters</li> |
| <li>Meeting will commence one hour later (7am PST), starting next week</li> |
| <li>Meeting will move to a US conference service: 1-888-722-7907 (alt: 1-816-650-0713), passcode |
| 9262945. Note that there are no local numbers outside the US with the Sprint service (let me know if |
| this is an issue).</li> |
| </ul> |
| <h2>Community from Lawrence Mandel</h2> |
| <ul> |
| <li>WTP help system initial content should be available by next week</li> |
| <li>Conference response: generally good, although code clinic was not advertised sufficiently (and |
| far enough in advance); this was a general conference issue, and not specific to WTPs use of it Some |
| general discussion around whether a code clinic was helpful given the prerelease state of WTP (DW), and |
| whether condensing it to fewer hours in the future would be an improvement (JK). Whether code clinics |
| should overlay the conference at all, or whether there simply isnt enough time for them to be useful |
| was also raised as an issue (ND).</li> |
| <li>EclipseCorner looking for contributions from WTP. This would also help communicate to the wider |
| community what WTP has made available so far and possibly help drive adoption. Publishing in broader |
| forums (JDJ, e.g.) would also be helpful, and contributions here are actively solicited; talk to |
| Lawrence if youre interested.</li> |
| </ul> |
| [PMC members only for the remaining portion of the meeting] |
| <h2>Requirements group reboot [JK]</h2> |
| <ul> |
| <li>Requirements group is currently composed of Jochen and Arthur.</li> |
| <li>BEA will appoint someone (either Tim or a WTP dev or pgm) to this group to participate as well. |
| </li> |
| <li>Process: Group will reconstitute and meet; mechanism to solicit requirements from WTP consumers |
| and possibly additional members to be its first order of business</li> |
| <li>Community is actively encouraged to participate at multiple levels, and committers or consumers |
| of WTP interested in membership should identify themselves to JK or TW</li> |
| </ul> |
| <h2>EclipseCon Debrief</h2> |
| <ul> |
| <li>General consensus that WTPs presence and message at conference was successful</li> |
| <li>Web Services generated interest from the press and several articles [JK]</li> |
| <li>WTP not on high download list; needs improved stability to drive adoption and more advertising |
| of available features [ND]</li> |
| </ul> |
| <h2>M3 Release Debrief</h2> |
| <ul> |
| <li>Significant improvements in process and code quality w.r.t. previous milestones, but more work |
| on stability is needed to reach production quality and enable widespread adoption [ND]</li> |
| <li>Demos at conference generally went well and succeeded at illustrating new functionality</li> |
| </ul> |
| <h2>Packaging Issues</h2> |
| <ul> |
| <li>Arthur noted that packaging is problematic too many loose files, too many 3rd party downloads |
| (14!), etc.</li> |
| <li>Licensing issues affecting 3rd party redistribution rights are being worked through with the |
| EMO, but it will take time.</li> |
| <li>WTP investigating the use of Eclipse update sites as a distribution mechanism for milestone |
| releases; will require 4th component to version numbering (Jeffrey Liu working on this already)</li> |
| <li>Two ZIPped bundles proposed: all WTP, and all WTP + Eclipse platform; should ease installation |
| hassles</li> |
| <li>Request to maintain some useful editing features (XML, e.g.) as separable from the entirety of |
| WTP [JK]</li> |
| <li>New and Noteworthy isnt on the download page [JK]. Should add link to upper right box in WTP |
| home page. Main Eclipse page downloads reference is still to M2, and needs to be updated.</li> |
| </ul> |
| <h2>New Committers</h2> |
| The PMC reviewed the community voting results and accepted the following WTP committers: Jeffrey Liu, Kathy |
| Chan, Keith Chong, Vijay Bhadriraju, Lawrence Dunnell |
| <h2>1.0 Rampdown / GA Process Description</h2> |
| <ul> |
| <li>Between M5 and GA, WTP will be in rampdown mode, and some description of the process and the |
| release criteria is needed [TW].</li> |
| <li>Existing documentation for milestone builds and exit criteria to be reviewed [DW, TW] in |
| preparation for this.</li> |
| <li>In general, following the platform seems reasonable, and we also need to respect documentation |
| and help file status [ND].</li> |
| <li>On a related topic, integration builds will move from Thursday to Tuesday to allow for two days |
| to address problems if the test status is not green [ND]. API discussion</li> |
| <li>Process surrounding the definition and freezing of APIs; see |
| http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg00705.html [AR]. David Williams agreed that the |
| architecture group would play a significant role in reviewing and admitting APIs for WTP as a whole.</li> |
| <li>Finalized process should be posted to the website [DV]</li> |
| <li>Platform tool to analyze component metadata (component.xml) and scan for API violations was |
| described [AR]; we are not yet compliant in many areas.</li> |
| <li>Discussed nomenclature surrounding provisional APIs; a significant percentage of WTPs APIs |
| may be in this category for 1.0</li> |
| <li>WTP to have standing agenda item until 1.0 GA to review status of component.xmls / API |
| conformance metrics</li> |
| <li>Release-to-release API change process: PMC will adopt some combination of its own policies and |
| the platforms approach to managing and communicating the change; details TBD.</li> |
| </ul> |
| <h2>Clarifying JST Use of Standards vs. Tooling Technologies</h2> |
| Discussed use of xdoclet by WTP, since questions were raised about its non-J2EE standardness at the |
| EclipseCon project sprint. PMC clarified that tooling of any form xdoclet, ant, editors, etc. is |
| acceptable for project use, but that *runtime* infrastructure and platforms targeted by JST will be limited |
| to J2EE standards. |
| <h2>Data Tools Project and Future of WTP RDB Component</h2> |
| Arthur provided a description of meetings between IBM and Exadel with Sybase over the charters of the WTP |
| RDB component and the newly proposed toplevel Data Tools Project (DTP) WTP PMC agreed that 1.0 release, and |
| currently planned requirements for it, will not be affected apart from API definitions in this arena, which |
| require either renaming or provisional status (outcome TBD based on subsequent discussions with Sybase/DTP |
| representatives) RDB EMF models will continue to exist, and WTP consumers can continue to rely on them; |
| Sybase is planning to contribute upgraded SQL editing and debugging capabilities as well as technology that |
| expands on the RDB component scope into administration and DB design |
| <h2>Help System</h2> |
| <ul> |
| <li>Help content was not included in original IBM contribution, but will be made available shortly |
| </li> |
| <li>Lawrence Mandel will be technical contact for help build system and tools</li> |
| <li>Help system is XML based (DITA), with open source processors on SourceForge</li> |
| <li>IBM may be contributing a writer as well; first priority is correcting/augmenting content to |
| match current WTP APIs and architecture; subsequent work would probably include some localization |
| effort, at least for major languages</li> |
| <li>Other companies may be able to contribute once infrastructure and content is present</li> |
| </ul> |
| <h2>Action Items:</h2> |
| <ul> |
| <li>[TW] By 3/15: Identify BEA employee to serve on WTP requirements group</li> |
| <li>[TW/JK] By 3/15: Reconstitute requirements group and set date for initial meeting.</li> |
| <li>[AI] Bundled M3 releases (see minutes)</li> |
| <li>[JK] Add new and noteworthy link and correct main Eclipse download page reference to be M3 |
| instead of M2</li> |
| <li>[TW] Draft language for endgame / rampdown based on Davids milestone release document; will |
| circulate to PMC when ready.</li> |
| <li>[TW] Pending community feedback on Arthurs API adoption process, post it to the website.</li> |
| <li>[TW] Update website to clarify that tool (not runtime) technologies are admissible in JST and |
| unrelated to the JCP requirement</li> |
| <li>[AR] Manage ongoing conversation with Sybase surrounding the RDB/DTP merge/migration.</li> |
| </ul> |
| <small>Minutes taken by Tim Wagner, March 8, 2005</small></td> |
| </tr> |
| <tr> |
| <td> </td> |
| </tr> |
| </tbody> |
| </table> |
| </body> |
| </html> |
