development/pmc_call_notes/2008-03-25.html - www.eclipse.org/webtools - Git at Google

 <?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 Agenda/Minutes for March 25, 2008 Conference Call</title>
 </head>
 <body>
 <h1>WTP PMC Agenda/Minutes for March 25, 2008 Conference Call</h1>
 <h2>Call Info</h2>
 <p>Tollfree in the US: 877-421-0030 <br />
 Alternate: 770-615-1247<br />
 Access code: 800388# <br />
 <a href="http://wiki.eclipse.org/images/f/f6/WTP_status_phone_access.pdf">Full list of phone numbers</a><br />
 <br />
 <a
     href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
 &amp;month=10
 &amp;day=16
 &amp;year=2007
 &amp;hour=11
 &amp;min=0&amp;sec=0&amp;p1=207">Call
 Time: 1500 UTC</a></p>
 <h2>Attendees</h2>
 <h3>PMC Members</h3>
 <ul>
     <li>David Williams: Y</li>
     <li>Naci Dai: N</li>
     <li>Raghunathan Srinivasan: Y</li>
     <li>Neil Hauge: Y</li>
     <li>Tim deBoer: Y</li>
 </ul>
 <!--
 <h3>Invited Guests</h3>
 <ul>
 <li>Philippe Ombredanne (ATF): N</li>
 </ul>
 -->
 <h2>Reports, Actions, Issues</h2>
 <h3>Planning: David Williams</h3>
 <ul>
     <li>We need a <b>another</b> 2.0.2 patch. (and put on update site) See <a
         href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=222531">bug 222531</a></li>
     <li>We are moving to P2 based builds this week</li>
     <li>In future, we (or, I) need to emphasize coordination better when asking teams to update minor version
     fields -- give a few days for teams to adjust.</li>
 </ul>
 <h4>Reference</h4>
 <ul>
     <li><a href="http://wiki.eclipse.org/WTP_Planning_Lead">WTP Planning Role</a></li>
     <li><a href="http://wiki.eclipse.org/WTP_Patches_for_Release_2.0.2">patch process document</a></li>
 </ul>
 <h3>Quality: Neil Hauge</h3>
 <ul>
     <li>Good progress ... or, flat (which is good :)</li>
 </ul>
 <h4>Reference:</h4>
 <ul>
     <li><a href="http://wiki.eclipse.org/WTP_Quality_Lead">WTP Quality Lead</a></li>
     <li>See also <a href="http://wiki.eclipse.org/WTP_Quality">Quality Page</a></li>
 </ul>
 <h3>Architecture: Tim deBoer</h3>
 <ul>
     <li>Neil asked, and Tim agreed to suppliment current API Policy Doc., on non-API use within WTP. Something to
     the effect of:
     <p>"Clean API use is encourage, but not critical, since no independent releases are anticipated anytime soon.
     Where feasible, bugs should be open with "API Requests" just as we expect from others, but there will be no focused
     effort to make sure that's done, since not a high priority, and since can easily see it when all source is loaded
     up."</p>
     </li>
 </ul>
 <h4>Reference</h4>
 <ul>
     <li><a href="http://wiki.eclipse.org/WTP_Architecture_Lead">WTP Architecture Lead Role</a></li>
     <li>Tracking meetings and work at <a href="http://wiki.eclipse.org/WTP_Architecture_Working_Group">WTP
     Architecture Working Group</a></li>
 </ul>
 <h3>Requirements: Raghu Srinivasan</h3>
 <ul>
     <li></li>
 </ul>
 <dl>
     <dt>Notes:</dt>
     <dd>We may need a mid-year release.</dd>
     <dd>Strategic Advisory Council (Raghu will be going).</dd>
 </dl>
 <h4>Reference</h4>
 <ul>
     <li><a href="http://wiki.eclipse.org/WTP_Requirements_Lead">WTP Requirements Lead Role</a></li>
 </ul>
 <h3>Education: Naci Dai</h3>
 <ul>
     <li>Phase 1, orgainize what we have, done by end January.</li>
     <li>Phase 2, self guided new materials. some available by EclipseCon.</li>
     <li>phase 3, shutdown .. scenerios</li>
 </ul>
 <dl>
     <dt>Notes:</dt>
     <dd>Orgainizing "current" now, should be ready by EclipseCon.</dd>
     <dd>Will be organized better for narrowing selection and sorting.</dd>
     <dd>For now, the "database" will be one XML file, with various attributes/qualities to search and sort on.</dd>
 </dl>
 <h4>Reference</h4>
 <ul>
     <li><a href="http://wiki.eclipse.org/WTP_Education_Lead">WTP Education Lead</a></li>
 </ul>
 <h2>General business?</h2>
 <ul>
     <li>JSF to lead the way on Exceptions to feature freeze. Need to emphasize, repeat process in Thursday's
     meeting</li>
     <li>Good feedback on EclipseCon
     <ul>
         <li>fee-less tutorials helped ... more attendees, still interested and engaged (not just gawkers "because
         it's free").</li>
         <li>should have power for tutorials</li>
         <li>+/- evaluation system was good</li>
         <li>invited guests (as whole) were not as good as last year's (as a whole)</li>
         <li>hack-a-thon -- did anyone attend?-- not well publicized</li>
         <li>webtools uncovered: good attendance. no minus ones</li>
         <li>webtools adopted: not heavily attended (could/should consolidate next year, have less time allotted</li>
     </ul>
     </li>
     <li>Potential resource issues?
     <ul>
         <li>Product plugin for EPP and welcome screen</li>
         <li>Refactoring Doc features (and moving to appropriate sub-projects).</li>
         <li>Refactoring SDK (source and JavaDoc) features/bundles (and moving to appropriate sub-projects)</li>
         <li>Platform/OS coverage for testing and support? -- probably suffices to simply record coverage. Perhaps
         ask for community help.</li>
         <li>Performance Tests -- Kayolan making some progress.</li>
     </ul>
     <dl>
         <dt>Notes:</dt>
         <dd>
         <ul>
             <li>No obvious resouce solutions.</li>
             <li>Needs some JSF features, at least for build</li>
         </ul>
         </dd>
     </dl>
     </li>
 </ul>
 <h2>Action Items</h2>
 <h3>To Do</h3>
 <ol>
     <li>David: Will call for Project Lead vote on <a
         href="http://wiki.eclipse.org/WTP_Policy_on_Package_Visibility">WTP Policy on Package Visibility</a></li>
     <li>Raghu: create a wiki page: a checklist for how to lower the barrier to participation for all projects</li>
     <li>David: create wiki page for 3rd-party requirements</li>
     <li>David: post instructions and reminders for our "community resources" and presentations page, especially,
     even, for eclipseCon 2007, and Eclipse Summit</li>
 </ol>
 <h3>Done</h3>
 <ol>
     <li>Bob Frasher, all: WTP Refactor followup: Need to update website. Project Leads will need to take ownership
     of their own pages. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=201331">bug 201331</a></li>
     <li>David: Reorg CVS. See <a href="http://wiki.eclipse.org/WTP_CVS_Restructuring">CVS Restructuring
     Proposal</a></li>
     <li>David: update our "planning" documents with dates for both Ganymede and Winter maintenance.</li>
 </ol>
 <h2>PMC Calendar</h2>
 <ul>
     <li>EclipseCon</li>
 </ul>
 <hr />
 <p>Back to <a href="../index_pmc_call_notes.php">meeting list</a>.</p>
 <p>Please send any additions or corrections to David Williams.</p>
 </body>
 </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>
	<title>WTP PMC Agenda/Minutes for March 25, 2008 Conference Call</title>
	</head>
	<body>
	<h1>WTP PMC Agenda/Minutes for March 25, 2008 Conference Call</h1>
	<h2>Call Info</h2>
	<p>Tollfree in the US: 877-421-0030 <br />
	Alternate: 770-615-1247<br />
	Access code: 800388# <br />
	<a href="http://wiki.eclipse.org/images/f/f6/WTP_status_phone_access.pdf">Full list of phone numbers</a><br />
	<br />
	<a
	href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
	&month=10
	&day=16
	&year=2007
	&hour=11
	&min=0&sec=0&p1=207">Call
	Time: 1500 UTC</a></p>
	<h2>Attendees</h2>
	<h3>PMC Members</h3>
	<ul>
	<li>David Williams: Y</li>
	<li>Naci Dai: N</li>
	<li>Raghunathan Srinivasan: Y</li>
	<li>Neil Hauge: Y</li>
	<li>Tim deBoer: Y</li>
	</ul>
	<!--
	<h3>Invited Guests</h3>
	<ul>
	<li>Philippe Ombredanne (ATF): N</li>
	</ul>
	-->
	<h2>Reports, Actions, Issues</h2>
	<h3>Planning: David Williams</h3>
	<ul>
	<li>We need a <b>another</b> 2.0.2 patch. (and put on update site) See <a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=222531">bug 222531</a></li>
	<li>We are moving to P2 based builds this week</li>
	<li>In future, we (or, I) need to emphasize coordination better when asking teams to update minor version
	fields -- give a few days for teams to adjust.</li>
	</ul>
	<h4>Reference</h4>
	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_Planning_Lead">WTP Planning Role</a></li>
	<li><a href="http://wiki.eclipse.org/WTP_Patches_for_Release_2.0.2">patch process document</a></li>
	</ul>
	<h3>Quality: Neil Hauge</h3>
	<ul>
	<li>Good progress ... or, flat (which is good :)</li>
	</ul>
	<h4>Reference:</h4>
	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_Quality_Lead">WTP Quality Lead</a></li>
	<li>See also <a href="http://wiki.eclipse.org/WTP_Quality">Quality Page</a></li>
	</ul>
	<h3>Architecture: Tim deBoer</h3>
	<ul>
	<li>Neil asked, and Tim agreed to suppliment current API Policy Doc., on non-API use within WTP. Something to
	the effect of:
	<p>"Clean API use is encourage, but not critical, since no independent releases are anticipated anytime soon.
	Where feasible, bugs should be open with "API Requests" just as we expect from others, but there will be no focused
	effort to make sure that's done, since not a high priority, and since can easily see it when all source is loaded
	up."</p>
	</li>
	</ul>
	<h4>Reference</h4>
	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_Architecture_Lead">WTP Architecture Lead Role</a></li>
	<li>Tracking meetings and work at <a href="http://wiki.eclipse.org/WTP_Architecture_Working_Group">WTP
	Architecture Working Group</a></li>
	</ul>
	<h3>Requirements: Raghu Srinivasan</h3>
	<ul>
	<li></li>
	</ul>
	<dl>
	<dt>Notes:</dt>
	<dd>We may need a mid-year release.</dd>
	<dd>Strategic Advisory Council (Raghu will be going).</dd>
	</dl>
	<h4>Reference</h4>
	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_Requirements_Lead">WTP Requirements Lead Role</a></li>
	</ul>
	<h3>Education: Naci Dai</h3>
	<ul>
	<li>Phase 1, orgainize what we have, done by end January.</li>
	<li>Phase 2, self guided new materials. some available by EclipseCon.</li>
	<li>phase 3, shutdown .. scenerios</li>
	</ul>
	<dl>
	<dt>Notes:</dt>
	<dd>Orgainizing "current" now, should be ready by EclipseCon.</dd>
	<dd>Will be organized better for narrowing selection and sorting.</dd>
	<dd>For now, the "database" will be one XML file, with various attributes/qualities to search and sort on.</dd>
	</dl>
	<h4>Reference</h4>
	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_Education_Lead">WTP Education Lead</a></li>
	</ul>
	<h2>General business?</h2>
	<ul>
	<li>JSF to lead the way on Exceptions to feature freeze. Need to emphasize, repeat process in Thursday's
	meeting</li>
	<li>Good feedback on EclipseCon
	<ul>
	<li>fee-less tutorials helped ... more attendees, still interested and engaged (not just gawkers "because
	it's free").</li>
	<li>should have power for tutorials</li>
	<li>+/- evaluation system was good</li>
	<li>invited guests (as whole) were not as good as last year's (as a whole)</li>
	<li>hack-a-thon -- did anyone attend?-- not well publicized</li>
	<li>webtools uncovered: good attendance. no minus ones</li>
	<li>webtools adopted: not heavily attended (could/should consolidate next year, have less time allotted</li>
	</ul>
	</li>
	<li>Potential resource issues?
	<ul>
	<li>Product plugin for EPP and welcome screen</li>
	<li>Refactoring Doc features (and moving to appropriate sub-projects).</li>
	<li>Refactoring SDK (source and JavaDoc) features/bundles (and moving to appropriate sub-projects)</li>
	<li>Platform/OS coverage for testing and support? -- probably suffices to simply record coverage. Perhaps
	ask for community help.</li>
	<li>Performance Tests -- Kayolan making some progress.</li>
	</ul>
	<dl>
	<dt>Notes:</dt>
	<dd>
	<ul>
	<li>No obvious resouce solutions.</li>
	<li>Needs some JSF features, at least for build</li>
	</ul>
	</dd>
	</dl>
	</li>
	</ul>
	<h2>Action Items</h2>
	<h3>To Do</h3>
	<ol>
	<li>David: Will call for Project Lead vote on <a
	href="http://wiki.eclipse.org/WTP_Policy_on_Package_Visibility">WTP Policy on Package Visibility</a></li>
	<li>Raghu: create a wiki page: a checklist for how to lower the barrier to participation for all projects</li>
	<li>David: create wiki page for 3rd-party requirements</li>
	<li>David: post instructions and reminders for our "community resources" and presentations page, especially,
	even, for eclipseCon 2007, and Eclipse Summit</li>
	</ol>
	<h3>Done</h3>
	<ol>
	<li>Bob Frasher, all: WTP Refactor followup: Need to update website. Project Leads will need to take ownership
	of their own pages. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=201331">bug 201331</a></li>
	<li>David: Reorg CVS. See <a href="http://wiki.eclipse.org/WTP_CVS_Restructuring">CVS Restructuring
	Proposal</a></li>
	<li>David: update our "planning" documents with dates for both Ganymede and Winter maintenance.</li>
	</ol>
	<h2>PMC Calendar</h2>
	<ul>
	<li>EclipseCon</li>
	</ul>
	<hr />
	<p>Back to <a href="../index_pmc_call_notes.php">meeting list</a>.</p>
	<p>Please send any additions or corrections to David Williams.</p>
	</body>
	</html>