blob: f868c8ea4c38a633bf6ce7849e4463016b82184c [file] [log] [blame]
<?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 September 27, 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 - September 27, 2005</font></b></td>
</tr>
</tbody>
</table>
<table
border="0"
cellpadding="2"
cellspacing="5"
width="100%">
<tbody>
<tr>
<td>Attending: Raghunathan Srinivasan [RS], Arthur Ryman [AR], David Williams [DW], Lawrence Mandel
[LM], Tim Wagner [TW] <!--PMC MEMBERS NOT PRESENT ON THIS CALL:
Christophe Ney [CN],
Jochen Krause [JK]
Naci Dai [ND],
-->
<h1>WTP PMC Minutes for September 27, 2005 Conference Call</h1>
<h2>Community Update [LM]</h2>
<ul>
<li>Website partitioning update: Reorg mostly complete - 1.0 plans have been moved, need some
existing link fixup from old summary plans. Also need to generate reports from Bugzilla and make them
look like milestone plan (Arthur). Tutorial cleanup complete; tutorials are now each self contained.
Next step is to reorganize subproject pages (groups by component).</li>
<li>EclipseCon - WTP slot use. Raghu: Oracle preparing submissions for EJB 3.0 and JSF (the latter
could use one of the WTP reserved slots). AR: One of our slots should be the overview presentation, and
we should submit as many additional abstracts as we can for deep dives on specific topics.</li>
</ul>
<h2>Procedural matters [TW]</h2>
<ul>
<li>Mike Milinkovich did not include the WTP charter modifications in the pre-meeting materials for
the Board face-to-face in Chicago last week, so the vote will occur on the next board call. I presented
the changes, and all but the "emerging specs" part were considered acceptable. The Board suggested an
amendment of that one to use the following language: "...new revisions of existing standards..." to
constrain pre-release tooling work.</li>
</ul>
<h2>Architecture Update [DW]</h2>
<ul>
<li>Progress on flexible project planning and alignment with platform plans, led by Chuck (call to
occur Wednesday). Discussed approach of having a wizard that would migrate a multi-module app to
multiple projects.</li>
<li>Feature reorg in flight; partial progress will be made in 1.0, with the remainder going into
1.5.</li>
<li>"Aspects" went into the (M9) build; integration will proceed this week.</li>
<li>Migration of code to base in time for joining the train is a current risk factor (tabbed
properties, extensible navigator, Internet proxy settings).</li>
<li>Need to resurrect API scanning tool to enable PMC progress review.</li>
</ul>
<h2>0.7.1 (Maintenance Stream) Status</h2>
<ul>
<li>Currently reviewing/testing release candidate. Each team is being asked to spend one day to run
through use cases/scenarios.</li>
<li>Looking to declare publically Friday if all goes well.</li>
</ul>
<h2>1.0 Status</h2>
<ul>
<li>New and Noteworthy - need to ensure that Oracle adapter is described.</li>
<li>M9 component plans complete.</li>
<li>Risk analysis: facet integration, multi-module migration, performance problems</li>
</ul>
<h2>JSF Status</h2>
<ul>
<li>Paperwork complete! JSF devs are now committers (3 from Oracle, one from Exadel)!</li>
<li>Planning update: Talking to other companies interested in project, Website milestone being
updated, Exadel will not be making a code contribution (starting from scratch).</li>
</ul>
<h2>Action Items</h2>
<ul>
<li>[TW] Get platform dates and drive process of setting 2006 WTP milestone dates (help up on
planning info from platform).</li>
<li>[TW] Work with Board on charter modification vote (October call).</li>
</ul>
<small>Minutes taken by Tim Wagner, September 27, 2005</small></td>
</tr>
</tbody>
</table>
</body>
</html>