development/pmc_call_notes/2010-11-23.html - www.eclipse.org/webtools - Git at Google

 <?xml version="1.0" encoding="ISO-8859-1" ?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
 <title>WTP PMC Agenda/Minutes for November 23, 2010 Conference
 Call</title>
 </head>
 <body>
 <h1>WTP PMC Agenda/Minutes for November 23, 2010 Conference Call</h1>
 <h2>Call Info</h2>
 <p>Toll free (in US and Canada): 888-426-6840 <br />
 Access code: 6460142# <br />
 Caller pay alternative number: 215-861-6239<br />
 <a
 	href="https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6460142&accessNumber=2158616239">Full
 list of global access numbers</a><br />
 <br />
 <a
 	href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
 &amp;month=11
 &amp;day=23
 &amp;year=2010
 &amp;hour=11
 &amp;min=0&amp;sec=0&amp;p1=207">Call
 Time: 11:00 AM Eastern</a></p>


 <h2>Attendees</h2>
 <h3>PMC Members</h3>
 <ul>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
 	Williams: Y</li>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Naci Dai: N</li>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Raghunathan
 	Srinivasan: Y</li>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Neil Hauge:
 	Y</li>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Tim deBoer:
 	Y</li>
 	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
 	Raev: Y</li>
 </ul>


 <h2>Announcements and General Business</h2>
 <ul>

 	<li>What about that JPA Diagram Editor!? <br />
 	Now on track? <br />
 	Recommend to start "move to Dali" process in January.
 	<p style="font-style: italic;">Will move to Dali Project (not
 	subproject) and follow social conventions. Seperate feature for
 	packaging. Prereqs Graphiti. Needs to "get up on" JPA 2.0 in months
 	ahead, before Indigo.</p>
 	</li>
 	<li>EclipseCon Coordination? <br />
 	OSGi Enterprise Tools? <br />
 	WTP Tutorials? <br />
 	(Nitin plans to propose something for JSDT)
 	<p style="font-style: italic;">Some ideas kicked around. Kaloyan
 	encouraged to submit something about OSGi Enterprise Tools Project ...
 	even if exact content not finalized for month or two. Neil likely to
 	submit tutorial covering JPA 2.0 and JAXB, mabye standalone vs. web
 	app, maybe pull in a web services angle. Via email, Naci likely to
 	propose something to the effect of "using WTP with other Eclipse
 	projects (such as maven)". General agreement that the large "what is
 	and how to use WTP" was getting &quot;old hat&quot;.</p>
 	</li>
 	<li>Who's to build OSGi Enterprise Tools? <br />
 	Is it a good candidate for GIT repository?
 	<p style="font-style: italic;">No firm decisions (or discussions)
 	... but, leaning towards GIT.</p>
 	</li>
 	<li>Can we review that so called "non-standard" part of OSGi
 	Enterprise Tools? (i.e. educate me :) <br />
 	Does it "compete" with one of the standards? <br />
 	Is it just a "defacto" standard (technique) before there were
 	standards?
 	<p style="font-style: italic;">Non-standard since it depends on a
 	specific run-time container, running on equinox. It did sound like it
 	has "been around" a long time, so to some extent, a defacto standard.
 	Also sounded like (from what I heard) did not "compete" with an OSGi
 	standard (though ... that might be a matter of conceptual debate ...
 	for some people, any alternative, to some extent, competes with people
 	using the standard.). I did emphasize that doing Virgo/Gemini specific
 	stuff does not violate the "vendor neutrality" rules at Eclipse
 	Foundation, since they are part of Eclipse Foundation. (Though, there
 	is a perception that it is "vendor specific". I guess since new, and I
 	guess since primarily one-vendor dominiated projects?). But, for the
 	non-standard "app model" issues, it makes sense to exclude those, since
 	those specs are actively being worked on, and while we want to support
 	the development of the spec, we do not want to prempt the spec with an
 	implementation, that might make it harder to come up with a good spec.,
 	or to move to the spec., if its different than a current
 	implementation.</p>
 	</li>


 </ul>
 <h3>Future Agenda items</h3>
 <!--  <ul style="text-indent: 5em; font-style: italic;"> -->
 <ul style="font-style: italic;">

 	<li>Retrospect Helios quick maintenance release. Does it mean we
 	weren't ready to release? Any way to improve timing in future?</li>
 	<li>Disuss our model and assignments of "PMC Roles". Do they still
 	make sense?</li>


 </ul>
 <h3>References</h3>
 <ul>

 	<li><a
 		href="http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_32">Continuous
 	Improvement Notes</a></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 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<title>WTP PMC Agenda/Minutes for November 23, 2010 Conference
	Call</title>
	</head>
	<body>
	<h1>WTP PMC Agenda/Minutes for November 23, 2010 Conference Call</h1>
	<h2>Call Info</h2>
	<p>Toll free (in US and Canada): 888-426-6840 <br />
	Access code: 6460142# <br />
	Caller pay alternative number: 215-861-6239<br />
	<a
	href="https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6460142&accessNumber=2158616239">Full
	list of global access numbers</a><br />
	<br />
	<a
	href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
	&month=11
	&day=23
	&year=2010
	&hour=11
	&min=0&sec=0&p1=207">Call
	Time: 11:00 AM Eastern</a></p>


	<h2>Attendees</h2>
	<h3>PMC Members</h3>
	<ul>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
	Williams: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Naci Dai: N</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Raghunathan
	Srinivasan: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Neil Hauge:
	Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Tim deBoer:
	Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
	Raev: Y</li>
	</ul>


	<h2>Announcements and General Business</h2>
	<ul>

	<li>What about that JPA Diagram Editor!? <br />
	Now on track? <br />
	Recommend to start "move to Dali" process in January.
	<p style="font-style: italic;">Will move to Dali Project (not
	subproject) and follow social conventions. Seperate feature for
	packaging. Prereqs Graphiti. Needs to "get up on" JPA 2.0 in months
	ahead, before Indigo.</p>
	</li>
	<li>EclipseCon Coordination? <br />
	OSGi Enterprise Tools? <br />
	WTP Tutorials? <br />
	(Nitin plans to propose something for JSDT)
	<p style="font-style: italic;">Some ideas kicked around. Kaloyan
	encouraged to submit something about OSGi Enterprise Tools Project ...
	even if exact content not finalized for month or two. Neil likely to
	submit tutorial covering JPA 2.0 and JAXB, mabye standalone vs. web
	app, maybe pull in a web services angle. Via email, Naci likely to
	propose something to the effect of "using WTP with other Eclipse
	projects (such as maven)". General agreement that the large "what is
	and how to use WTP" was getting "old hat".</p>
	</li>
	<li>Who's to build OSGi Enterprise Tools? <br />
	Is it a good candidate for GIT repository?
	<p style="font-style: italic;">No firm decisions (or discussions)
	... but, leaning towards GIT.</p>
	</li>
	<li>Can we review that so called "non-standard" part of OSGi
	Enterprise Tools? (i.e. educate me :) <br />
	Does it "compete" with one of the standards? <br />
	Is it just a "defacto" standard (technique) before there were
	standards?
	<p style="font-style: italic;">Non-standard since it depends on a
	specific run-time container, running on equinox. It did sound like it
	has "been around" a long time, so to some extent, a defacto standard.
	Also sounded like (from what I heard) did not "compete" with an OSGi
	standard (though ... that might be a matter of conceptual debate ...
	for some people, any alternative, to some extent, competes with people
	using the standard.). I did emphasize that doing Virgo/Gemini specific
	stuff does not violate the "vendor neutrality" rules at Eclipse
	Foundation, since they are part of Eclipse Foundation. (Though, there
	is a perception that it is "vendor specific". I guess since new, and I
	guess since primarily one-vendor dominiated projects?). But, for the
	non-standard "app model" issues, it makes sense to exclude those, since
	those specs are actively being worked on, and while we want to support
	the development of the spec, we do not want to prempt the spec with an
	implementation, that might make it harder to come up with a good spec.,
	or to move to the spec., if its different than a current
	implementation.</p>
	</li>


	</ul>
	<h3>Future Agenda items</h3>
	<!-- <ul style="text-indent: 5em; font-style: italic;"> -->
	<ul style="font-style: italic;">

	<li>Retrospect Helios quick maintenance release. Does it mean we
	weren't ready to release? Any way to improve timing in future?</li>
	<li>Disuss our model and assignments of "PMC Roles". Do they still
	make sense?</li>


	</ul>
	<h3>References</h3>
	<ul>

	<li><a
	href="http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_32">Continuous
	Improvement Notes</a></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>