blob: e0ff45c2734522890cae2315c3e8c7b1414612b5 [file] [log] [blame]
<html>
<head>
<title>WTP PMC Minutes for April 12, 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 - April 12, 2005</font></b></td>
</tr>
</tbody></table>
<table border="0" cellpadding="2" cellspacing="5" width="100%">
<tbody><tr>
<td>
<title>WTP PMC Minutes for April 12, 2005 Conference Call</title>
Attending:
Tim Wagner [TW],
David Williams [DW],
Arthur Ryman [AR],
Dominique De Vito [DD],
Christophe Ney [CN],
Jochen Krause [JK],
Naci Dai [ND]
Others: Lawrence Mandel (representing WTP community) [LM]
<h1>WTP PMC Minutes for April 12, 2005 Conference Call</h1>
<h2>Procedural matters - None</h2>
<h2>Community [LM] </h2>
<ul>
<li>EclipseWorld tutorial proposal in flight.
<li>AR created presentation archive – see email on WTP list. This is intended to be a repository for presentation materials.
<li>AR talking at Colorado Software Summit on Web Services development in Eclipse and WSDL 2.0.
<li>Help system: successful internal build; should be incorporated into this week’s I-build. Requested Bugzilla “documentation” component (PMC approved request). Will be contacting BEA for help with documentation content work.
</ul>
[PMC members only for the remaining portion of the meeting]
<h2>API Review</h2>
<ul>
<li>PMC reviewed API statistics
<li>j2ee.core component identified as not making sufficient progress; the bulk of its models will need to be turned provisional. Potential migration of flexible project model to platform in 3.2 is a possible stumbling block in finalizing API in that area.
<li>Clarified renaming/repackaging strategy to be complete by end of M4.
<li>Continued progress on removing unintended APIs: dropped from 4,326 to 3,349. Overall metric for 4/11 build is 59.
<li>Summary from April 11th build report: 35% JUnit coverage, 95% JavaDoc coverage, 9/14 overview docs.
See <a href='http://download.eclipse.org/webtools/downloads/drops/N-N20050411-200504111848/apitools/api-progress.html'>
http://download.eclipse.org/webtools/downloads/drops/N-N20050411-200504111848/apitools/api-progress.html</a>.
</ul>
<h2>Requirements Group Report [JK] </h2>
<ul>
<li>No news to report; will begin including this in the agenda on a bi-weekly basis.
</ul>
<h2>Architecture Group Report [DW] </h2>
<ul>
<li>Validation framework API deferred.
<li>XML resolver/catalog API deferred.
<li>See flexible project model notes above.
<li>Separate XERCES plugin build likely this week.
<li>XML and WSDL dependency on JDT should be removed this week.
<li>GEM’s M6 readiness is late; may cause us to introduce a late dependency change into our own build.
</ul>
<h2>XPDL Proposal and Discussion of WTP Criteria for Submissions [JK] </h2>
<ul>
<li>AR: standard body must be recognized, but standard must also be popular and open source runtime available, and standard must be in scope.
<li>AR: Criteria for standards body: open to new members, broad industry participation, established/history.
<li>CN: Maturity and adoption of standard should be part of our criteria.
<li>ND: XPDL and BPEL would be better placed in a technology project; too far from general audience of WTP.
<li>PMC resolved to suggest a technology project, but agreed to review the proposal when written to review vis-à-vis WTP charter.
</ul>
<h2>WTP 1.0 Product Forums [JK] </h2>
<ul>
<li>Idea would be to get interested parties to build on WTP 1.0, drive adoption, and gather requirements for 1.1.
<li>Timeframe: post 1.0 ship (easier to do once churn stops).
<li>Requirements group will take this on and report back to the PMC when proposal is complete.
</ul>
<h2>Eclipse Booth at JavaOne [TW] </h2>
<ul>
<li>CN, DD, and TW will assist with staffing the booth; TW to respond to Ian.
</ul>
<h2>Creation of XSL Component [DW] </h2>
<ul>
<li>Discussed contribution request (for 1.1; not on table for 1.0 release).
<li>Normal committership process must be followed, despite size of contribution.
<li>Can be made part of build so that it’s available for evaluation by committers and rest of community.
</ul>
<h2>Upcoming Milestone Build Process Ownership [DW] </h2>
<ul>
<li>Setting dates / versions for upstream components, driving test plans with component leads, evaluation of candidates and convergence toward acceptance.
<li>AR offered to support DW in this effort.
</ul>
<h2>Build Status Reports [ND] </h2>
<ul>
<li>New distribution list will be set up for build reports.
<li>Progress on build status/result reporting – compile failures now attached to email.
<li>Will increase number of warmup builds.
</ul>
<h2>Status Update on Ongoing Projects [AR] </h2>
<ul>
<li>Janet making progress on 3rd party content agreements; ETA is M4.
<li>AXE will be going into the Lepido technology project.
<li>DTP: Sybase and others meeting with IBM to go over code and make progress (see email to PMC).
</ul>
<h2>Action Items:</h2>
<ul>
<li>TW: finalize dates for release reviews with EMO (week of June 20th being discussed)
</ul>
<small>Minutes taken by Tim Wagner, April 12, 2005</small>
</tr>
<tr>
<td>
&nbsp;</td>
</tr>
</tbody></table>
</html>