development/pmc_call_notes/2011-10-04.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 October 4, 2011 Conference
 	Call</title>
 </head>


 <body>
 	<h1>WTP PMC Agenda/Minutes for October 4, 2011 Conference Call</h1>
 	<h2>Call Info </h2>
 	<p>
 		Toll free (in US and Canada): 888-426-6840 <br /> Access code:
 		5019600# <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=08
 &amp;day=25
 &amp;year=2011
 &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;">Chuck
 			Bridgham: 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: N</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
 			Raev: Y</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
 			Williams: Y</li>
 	</ul>
 -->

 	<h2>Announcements and General Business</h2>


 	<h3>Discuss API policy revision proposals</h3>
 	<p>We discussed proposing some clarifications to our API policy, and Chuck sent a draft to the mailing list</p>

 	<ul>
 		<li><a href="http://wiki.eclipse.org/WTP_API_Policy">WTP API Policy</a></li>
 	</ul>

 	<p>
 	<ul>
 		<li> Amend the "Declared API" section to include the following (borrowed from the platform description):
 "The API (Application Programming Interface) is the entire public programming surface of the framework,
  thus it includes not only Java classes, packages, and interfaces, but also extension points, file formats, generated meta-data, and even objects that are passed through to internal packages. A good example
 of extension point metadata is the use of defined facets representing a collection of Java classes, libraries, and attributes that define a specific domain.</li>

 <li> Create a new section named "Process to evolve an API"

 "There is a promise of stability from release to release, and evolving an api by various techniques that don't break adopters and maintain the current API behavior, can be proposed with required approval by the project lead.
  If a need for breaking api or behavior changes of existing api is deemed necessary, these exceptions must be brought to the PMC for approval, and will only be considered in new development  releases(Not maintenance)"</li>

 	</ul>
 	</p>

 	<h3>Possible proposal for m2e-wtp incubation project coming...</h3>
 	<p>In last weeks Java EE planning meeting, Max Anderson (JBoss) indicated this project is essentially owned by RedHat now,
 	and they would be interested in bringing to Eclipse.  Both Konstantin and I jumped at this possibility, and have offered our help creating a proposal.
 	Max has very limited resources at the moment, but I think we (WTP PMC) should do all we can to encourage a proposal (Help with examples etc..)
 	</p>

 	<h3>Other Business ... ?</h3>

 	<p>Git adoption progress    Continue polling - re-evaluate by M4
 	- Should we put a stake in the ground mandating when we need to see some progress in educating our committers?
 	- investigate a subproject that could "pilot" a git repo feeding into our overall PDE build
 	- More discussion on CVS - GIT transition - should replace CVS feature for feature
 	- Platform HAS put a stake in the ground....
 	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=358980"> CVS Retirement bug (Target: December 21, 2012)</a>
 	</p>

 	<p>3.4 Release planning
 		<a href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools">Top-level plan</a>
 	</p>
 	<ul>
 		<li>M2: Initial Planning document.</li>
 		<li>M3: Iterate/Review plans</li>
 		<li>M4: Final Plans due</li>
 	</ul>

 	<p>
 		webtool.website Progress from <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=356874">tracking bug</a>
 	</p>


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


 		<li>Discuss our model and assignments of "PMC Roles". Do they
 			still make sense?</li>


 	</ul>
 	<h2>References</h2>
 	<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 Chuck Bridgham.</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 October 4, 2011 Conference
	Call</title>
	</head>


	<body>
	<h1>WTP PMC Agenda/Minutes for October 4, 2011 Conference Call</h1>
	<h2>Call Info </h2>
	<p>
	Toll free (in US and Canada): 888-426-6840 <br /> Access code:
	5019600# <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=08
	&day=25
	&year=2011
	&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;">Chuck
	Bridgham: 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: N</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
	Raev: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
	Williams: Y</li>
	</ul>
	-->

	<h2>Announcements and General Business</h2>


	<h3>Discuss API policy revision proposals</h3>
	<p>We discussed proposing some clarifications to our API policy, and Chuck sent a draft to the mailing list</p>

	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_API_Policy">WTP API Policy</a></li>
	</ul>

	<p>
	<ul>
	<li> Amend the "Declared API" section to include the following (borrowed from the platform description):
	"The API (Application Programming Interface) is the entire public programming surface of the framework,
	thus it includes not only Java classes, packages, and interfaces, but also extension points, file formats, generated meta-data, and even objects that are passed through to internal packages. A good example
	of extension point metadata is the use of defined facets representing a collection of Java classes, libraries, and attributes that define a specific domain.</li>

	<li> Create a new section named "Process to evolve an API"

	"There is a promise of stability from release to release, and evolving an api by various techniques that don't break adopters and maintain the current API behavior, can be proposed with required approval by the project lead.
	If a need for breaking api or behavior changes of existing api is deemed necessary, these exceptions must be brought to the PMC for approval, and will only be considered in new development releases(Not maintenance)"</li>

	</ul>
	</p>

	<h3>Possible proposal for m2e-wtp incubation project coming...</h3>
	<p>In last weeks Java EE planning meeting, Max Anderson (JBoss) indicated this project is essentially owned by RedHat now,
	and they would be interested in bringing to Eclipse. Both Konstantin and I jumped at this possibility, and have offered our help creating a proposal.
	Max has very limited resources at the moment, but I think we (WTP PMC) should do all we can to encourage a proposal (Help with examples etc..)
	</p>

	<h3>Other Business ... ?</h3>

	<p>Git adoption progress Continue polling - re-evaluate by M4
	- Should we put a stake in the ground mandating when we need to see some progress in educating our committers?
	- investigate a subproject that could "pilot" a git repo feeding into our overall PDE build
	- More discussion on CVS - GIT transition - should replace CVS feature for feature
	- Platform HAS put a stake in the ground....
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=358980"> CVS Retirement bug (Target: December 21, 2012)</a>
	</p>

	<p>3.4 Release planning
	<a href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools">Top-level plan</a>
	</p>
	<ul>
	<li>M2: Initial Planning document.</li>
	<li>M3: Iterate/Review plans</li>
	<li>M4: Final Plans due</li>
	</ul>

	<p>
	webtool.website Progress from <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=356874">tracking bug</a>
	</p>


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


	<li>Discuss our model and assignments of "PMC Roles". Do they
	still make sense?</li>


	</ul>
	<h2>References</h2>
	<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 Chuck Bridgham.</p>
	</body>
	</html>