development/pmc_call_notes/2005-03-29.html - www.eclipse.org/webtools - Git at Google

 <html>
 <head>
 <title>WTP PMC Minutes for March 29, 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 29, 2005</font></b></td>

   </tr>
   </tbody></table>
 <table border="0" cellpadding="2" cellspacing="5" width="100%">
   <tbody><tr>
     <td>

 Attending:

 Tim Wagner [TW],

 David Williams [DW],

 Dominique De Vito [DV],

 Arthur Ryman [AR],

 Bjorn Freeman-Benson [BB],

 Jochen Krause [JK],

 Naci Dai [ND]

 Others: Lawrence Mandel (representing WTP community) [LM]


 <h2>Procedural matters </h2>

 <ul>

 <li>Update on last weeks request that EMO investigate IRC server for telecon use: will be delayed for several months.

 </ul>


 <h2>Community [LM]</h2>

 <ul>

 <li>EclipseWorld submissions: tutorial would be good [AR], target audience is end users rather than plug-in developers  could reuse material from EclipseCon overview (plus updates from 1.0 release). AR, TW, and Tim deBoer may all be submitting talks.

 <li>Help system  build working, will push out to public machine this week. General convention in Eclipse is to ship help <em>with</em> the download. While we will have something ready by 1.0 ship, concern is that we will not have enough manpower to have this ready in time; if we have a quarterly maintenance release, may need to use that as the documentation release vehicle. Doc build <em>is</em> separate from code, so we will need to use a later (1.0.1) release vehicle the first time around to complete documentation. One suggestion is to have developers try to update some of the areas of significant change (like flexible project model). Build periodicity: part of N-builds for simplicity. (Requires 2-3 minutes to run, produces about 3M of output.) Currently a separate feature.

 <li>(External) Link breakage / Cross Project Coordination: (M3 separate download no longer works because of broken links.) Two options  asking other teams to keep the links alive, or maintaining local copies of the material we need. I-builds from other projects are needed for fixes or platform milestone compatibility, but if another team deletes an I-build, we should no longer be relying on it. Resolved to copy I-builds from other projects (not platform, where we use only milestone builds).

 </ul>


  [PMC members only for the remaining portion of the meeting]


 <h2>Requirements Group Report [JK] </h2>

 <ul>

 <li>Will be discussing themes this week, and will send out results to wtp-pmc mailing list.

 <li>Still have two milestone plans linked on our website; see AIs.

 </ul>


 <h2>Architecture Group Report [DW]</h2>

 <ul>

 <li>WTP Browser support migrated to platform

 <li>Tabbed property sheet migrated to platform

 <li>(See A-G notes for further details.)

 <li>Component open house scheduling  will be open to any interested parties as well as WTP devs. Format: telecon + eMeeting. Proposed agenda: One hour apiece, six meetings, one meeting per week, component leads would be presenters.

 </ul>


 <h2>AXE Proposal [AR]</h2>

 <ul>

 <li>Form-based UI for XML documents, proposed by Anywhere, based on Jelly (an Apache project).

 <li>Arthur sent a follow-up requesting an example and some exploration of the ease of use.

 <li>Too late for 1.0; discussion is whether this should be a 1.1 feature.

 <li>Since they appear inclined to proposing a technology project, well evaluate that when/if it occurs.

 </ul>


 <h2>DTP Update</h2>

 <ul>

 <li>Technical meetings getting started.

 <li>Proposal timeframe: June; component move targeted for August

 <li>Package prenaming: low confidence that this will happen in time for WTP 1.0

 </ul>


 <h2>Release Review [BB]</h2>

 <ul>

 <li>Precedes each major release (WTPs 1.0)

 <li>Scheduled for early in endgame

 <li>Purposes: verify no outstanding IP issues, set of released features vs. roadmap, verify that API is appropriate quality, defect status.

 </ul>


 <h2>API Review</h2>

 <ul>

 <li>PMC reviewed API statistics

 <li>Time series / convergence tracking not yet available

 <li>Down to ~6K APIs (still high, but substantial progress versus starting point)

 <li>SSE and other components will have trouble meeting M4 exit criteria [DW], resolution is to defer API definition where necessary to meet quality goals

 </ul>


 <h2>Action Items:</h2>

 <ul>

 <li>ND: copy I-builds referenced from other projects.

 <li>AR: update milestone plan on website

 <li>TW: finalize dates for release reviews with EMO

 <li>TW/AR/DW: finalize trip logistics for BEA visits

 <li> LM: coordinate EclipseWorld submissions with AR, TW

 </ul>


 <small>Minutes taken by Tim Wagner, March 29, 2005</small>
   </tr>

     <tr>
     <td>
       &nbsp;</td>

   </tr>

   </tbody></table>
 </html>
	<html>
	<head>
	<title>WTP PMC Minutes for March 29, 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 29, 2005</font></b></td>

	</tr>
	</tbody></table>
	<table border="0" cellpadding="2" cellspacing="5" width="100%">
	<tbody><tr>
	<td>

	Attending:

	Tim Wagner [TW],

	David Williams [DW],

	Dominique De Vito [DV],

	Arthur Ryman [AR],

	Bjorn Freeman-Benson [BB],

	Jochen Krause [JK],

	Naci Dai [ND]

	Others: Lawrence Mandel (representing WTP community) [LM]




	<h2>Procedural matters </h2>

	<ul>

	<li>Update on last weeks request that EMO investigate IRC server for telecon use: will be delayed for several months.

	</ul>



	<h2>Community [LM]</h2>

	<ul>

	<li>EclipseWorld submissions: tutorial would be good [AR], target audience is end users rather than plug-in developers could reuse material from EclipseCon overview (plus updates from 1.0 release). AR, TW, and Tim deBoer may all be submitting talks.

	<li>Help system build working, will push out to public machine this week. General convention in Eclipse is to ship help <em>with</em> the download. While we will have something ready by 1.0 ship, concern is that we will not have enough manpower to have this ready in time; if we have a quarterly maintenance release, may need to use that as the documentation release vehicle. Doc build <em>is</em> separate from code, so we will need to use a later (1.0.1) release vehicle the first time around to complete documentation. One suggestion is to have developers try to update some of the areas of significant change (like flexible project model). Build periodicity: part of N-builds for simplicity. (Requires 2-3 minutes to run, produces about 3M of output.) Currently a separate feature.

	<li>(External) Link breakage / Cross Project Coordination: (M3 separate download no longer works because of broken links.) Two options asking other teams to keep the links alive, or maintaining local copies of the material we need. I-builds from other projects are needed for fixes or platform milestone compatibility, but if another team deletes an I-build, we should no longer be relying on it. Resolved to copy I-builds from other projects (not platform, where we use only milestone builds).

	</ul>



	[PMC members only for the remaining portion of the meeting]



	<h2>Requirements Group Report [JK] </h2>

	<ul>

	<li>Will be discussing themes this week, and will send out results to wtp-pmc mailing list.

	<li>Still have two milestone plans linked on our website; see AIs.

	</ul>



	<h2>Architecture Group Report [DW]</h2>

	<ul>

	<li>WTP Browser support migrated to platform

	<li>Tabbed property sheet migrated to platform

	<li>(See A-G notes for further details.)

	<li>Component open house scheduling will be open to any interested parties as well as WTP devs. Format: telecon + eMeeting. Proposed agenda: One hour apiece, six meetings, one meeting per week, component leads would be presenters.

	</ul>



	<h2>AXE Proposal [AR]</h2>

	<ul>

	<li>Form-based UI for XML documents, proposed by Anywhere, based on Jelly (an Apache project).

	<li>Arthur sent a follow-up requesting an example and some exploration of the ease of use.

	<li>Too late for 1.0; discussion is whether this should be a 1.1 feature.

	<li>Since they appear inclined to proposing a technology project, well evaluate that when/if it occurs.

	</ul>



	<h2>DTP Update</h2>

	<ul>

	<li>Technical meetings getting started.

	<li>Proposal timeframe: June; component move targeted for August

	<li>Package prenaming: low confidence that this will happen in time for WTP 1.0

	</ul>



	<h2>Release Review [BB]</h2>

	<ul>

	<li>Precedes each major release (WTPs 1.0)

	<li>Scheduled for early in endgame

	<li>Purposes: verify no outstanding IP issues, set of released features vs. roadmap, verify that API is appropriate quality, defect status.

	</ul>



	<h2>API Review</h2>

	<ul>

	<li>PMC reviewed API statistics

	<li>Time series / convergence tracking not yet available

	<li>Down to ~6K APIs (still high, but substantial progress versus starting point)

	<li>SSE and other components will have trouble meeting M4 exit criteria [DW], resolution is to defer API definition where necessary to meet quality goals

	</ul>



	<h2>Action Items:</h2>

	<ul>

	<li>ND: copy I-builds referenced from other projects.

	<li>AR: update milestone plan on website

	<li>TW: finalize dates for release reviews with EMO

	<li>TW/AR/DW: finalize trip logistics for BEA visits

	<li> LM: coordinate EclipseWorld submissions with AR, TW

	</ul>





	<small>Minutes taken by Tim Wagner, March 29, 2005</small>
	</tr>

	<tr>
	<td>
	</td>

	</tr>

	</tbody></table>
	</html>