development/pmc_call_notes/2004-10-19.html

<?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>
<meta
    http-equiv="Content-Type"
    content="text/html; charset=iso-8859-1" />
<title>Eclipse Web Tools Platform Project Development</title>
<link
    rel="stylesheet"
    href="../../../default_style.css"
    type="text/css" />
<meta
    http-equiv="Content-Type"
    content="text/html; charset=windows-1252" />
</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 - October 19, 2004</font></b></td>
        </tr>
    </tbody>
</table>
<table
    border="0"
    cellpadding="2"
    cellspacing="5"
    width="100%">
    <tbody>
        <tr>
            <td>
            <p>Attending: Bjorn Freeman-Benson, David Williams, Jochen Krause, Mitch Sonies, Naci Dai</p>
            <p><b>Flexible Project Support Working Group</b> by David</p>
            <ul>
                <li>Who is on this working group?</li>
            </ul>
            <p><b>Charter</b> by Bjorn</p>
            <ul>
                <li>To resolve a potential ambiguity in the charter about voting, we propose to vote next week to
                propose to the Eclipse Board the following changes (highlighted) to the <a
                    href="../../project-charter.html">WTP Project Charter</a>:<br />
                &quot;Once a Developer is nominated, the Committers for the Project (or component) will vote. <span
                    style="background-color: #FFFF00">Voting will remain open for one week (seven calendar days).</span>
                If there are at least 3 positive votes and no negative votes <span style="background-color: #FFFF00">in
                that period</span>, the Developer is recommended to the PMC for commit privileges.&quot;</li>
            </ul>
            <p><b>Milestone Dates</b> by David and Naci</p>
            <ul>
                <li>We have changed <a href="../planning/milestone_plan_1_0.html">our milestone dates</a> to be one
                week after the corresponding Eclipse Platform milestone dates and have annotated our milestones with the
                Platform milestone version they will be built upon.</li>
            </ul>
            <p><b>FAQ</b> by Bjorn</p>
            <ul>
                <li>We don't have a FAQ yet, but we need one. We decided the best process to create the FAQ is to
                have a Bugzilla component for the FAQ and use that to drive the FAQ creation. We have requested the
                Eclipse infrastructure person to create the FAQ component.</li>
            </ul>
            <p><b>Adoption Rate of Contributed Code</b> by Jochen</p>
            <ul>
                <li>Continued discussion of how quickly to put the contributed code into CVS; whether the code
                should be put in CVS before being reviewed, after being reviewed but before being refactored, etc. The
                issue remains open.</li>
            </ul>
            <p><b>M1 How Did We Do?</b> by David and Naci</p>
            <ul>
                <li>A series of measures of our progress:
                <ul>
                    <li>Made the M1 date: <b><font color="#00CC66"><i>yes</i></font></b></li>
                    <li>Promised function: <i><b><font color="#00CC66">mostly</font></b></i></li>
                    <li>Unit tests complete and running as &quot;passed&quot;: <font color="#FF0000"> <i>no</i></font></li>
                    <li>Test plan with use cases: <i><font color="#FF0000">no</font></i></li>
                    <li>Function available one week before milestone: <i> <font color="#FF0000">no</font></i></li>
                    <li>Design and APIs reviewed and issues answered before milestone: <i> <font
                        color="#FF0000">no</font></i></li>
                    <li>Community-users buy-in and/or excitement: <i> <font color="#FF0000">no - no
                    announcement, no link to download page, no tutorials/examples/where to start, no new/noteworthy</font></i></li>
                    <li>Included community contributed code: <i><b><font color="#00CC66"> yes</font></b></i></li>
                </ul>
                </li>
                <li>For the M2 release, we need to behave more like a real software project including:
                <ul>
                    <li>A development process document including the freeze-build-test cycle and when to freeze,
                    when to provide the first integration build, testing, fixing, labeling in CVS, how to notify the
                    world, etc. Include the list of tasks that committers must complete to be part of the M-Build (no
                    more last minute dependency errors).</li>
                    <li>A list of the built packages: WTP binary, WST binary, WTP SDK, WST SDK, Tests. Not that JST
                    requires WST, so there is no separate JST binary or JST SDK.</li>
                    <li>A requirement that no component be included in the release if there are no tests. The lack
                    of unit tests and a test platform is our single biggest deficiency.</li>
                </ul>
                </li>
            </ul>
            <p><b>On the Queue for Next Week</b></p>
            <ul>
                <li>Discussion the WebDAV component</li>
                <li>Planning group report</li>
                <li>Milestone planning for M2</li>
            </ul>
            <p><font size="-1"><i>Minutes taken by Bjorn Freeman-Benson and posted by Bjorn
            Freeman-Benson, October 19, 2004</i></font></p>
            </td>
        </tr>
    </tbody>
</table>
</body>
</html>