blob: a71fd9ebda77ee465b66a64988381858c5dc0086 [file] [log] [blame]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<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 name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Project Documentation</title>
</head>
<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
<tr>
<td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b> <font face="Arial,Helvetica" color="#FFFFFF">Requirements
Conference Call - August 30, 2004</font></b></td>
</tr>
</table>
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
<tr>
<td bgcolor="#FFFFFF"><p>Agenda:</p>
<ul>
<li>Flexible Project Structure</li>
<li>Requirement Priorities</li>
</ul>
<p>Attending: Arthur Ryman, Vladislav Pernin, Todd Williams, Jochen Krause</p>
<P>General</P>
<li>With regard to publishing documents we follow the principle “early and often”, not “perfect but late” </li>
<p>Flexible project model</p>
<li>We will make initial requirements document available on a wiki, as well
as Naci’s and Thomas notes. The wiki will become publicly usable.</li>
<li>Request making the wiki public from Dominique / Christophe</li>
<li>Objection: This will make it much harder to read to document / follow the
main ideas (but a revision system is available - make that more visible
(Jochen) )</li>
<br>
<li>Flexible project structure, scope is wider than stated, valid as well
for WST, we have to specify the requirements for WST only</li>
<li>We should make sure that our needs are heard by the platform team (specifically
links). David Williams will go to the EMO meeting.</li><br>
<li>Use exploded archives as default layouts</li>
<blockquote>One use case:
<li>Import a project from CVS and be able to adapt the Web Project Structure
to the one in cvs.</li></blockquote>
<li>Provide comments to the requirements document in the wiki to get a discussion
going</li>
<p>Requirements Priorities</p>
<li>Priorities as agreed during the last conf call will be published
on the webtools web site</li>
<p>Use cases</p>
<li>Find a way to combine Bugzilla with a better structured method
of specifying requirements – suggest a template (Arthur / Jochen)</li></td>
</tr>
</table>
</body>
</html>