development/pmc_call_notes/2011-08-16.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 August 16, 2011 Conference
	Call</title>
</head>
<body>
	<h1>WTP PMC Agenda/Minutes for August 16, 2011 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=08
&amp;day=16
&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;">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: 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;">Chuck
			Bridgham: Y</li>
	</ul>

	<h2>Announcements and General Business</h2>

	<h3>Discuss and document change in PMC Lead.</h3>

	<p>While we have discussed this for several weeks, the purpose of
		this agenda item is to document our proposed plan:</p>

	<p>It is proposed to have Chuck Bridgham take over as WTP PMC Lead.
		David Williams will stay on the WTP PMC, just not as lead. David to
		continue as WTP PMC's representative to Planning Council (and, as
		chair of Planning Council, coordinating Juno release). The goal here
		is to simply spread out leadership roles, and allow David to dabble in
		other things after nearly 5 years as PMC Lead. In other words, there
		is no change in strategy or commitment.</p>

	<p>Technically, the EDP and by-laws specify that only the Board of
		Directors votes and approves the PMC Lead ... that is, there is not a
		public vote of current PMC members or projects required. (This is
		likely related to the historical idea that Eclipse Strategic Members
		are expected to "lead a project" which, when Eclipse started, meant
		what we currently call a "top level project".)</p>

	<p>But, under the current circumstances, having current members
		agree with the plan will undoubtedly make the Board's decision easy
		and non-controversial.</p>

	<p>To document it explicitly, from previous meetings and emails,
		there is unanimous agreement with this plan: all PMC members have
		complete confidence in Chuck's ability to lead the PMC and take WTP
		through its next generation of development. While Chuck has only been
		on the PMC since early 2011, he has been lead of the JEE sub project,
		and heavily involved with WTP since its beginning in 2004. He is
		committed to the success of WTP, both for adopters and users and will
		continue to lead WTP to be one of the outstanding projects at Eclipse.</p>

	<p>The plan is to have this change proposed (on the agenda) at the
		next Eclipse Board meeting agenda, on 9/21.</p>

	<p>It is proposed to have Chuck start leading the weekly PMC
		Meetings, though he will not formally be the PMC Lead until the Board
		votes and agrees in September.</p>

	<p style="font-style: italic;">The PMC agreed. It was decided to
		send a note to wtp-pmc with a link back to these meeting minutes,
		especially when announcing change in call-in number. While that does,
		already, make it "public information", later, after the board
		approves, we will officially announce on wtp-dev just to make sure we
		communicate well with the WTP community.</p>

	<h3>WTP Releng</h3>

	<p>Carl Anderson to take over central releng responsibilities,
		while we continue to look for ways to distribute releng work and
		responsibilities. Carl has been nominated as "WTP Releng Project
		Lead". David will stay on as a releng committer and help if/when
		issues come up.</p>

	<p>Nomination was done on wtp-dev list, with 4 of 5 +1 votes. (Tran
		has been on vacation.) Does the PMC approve? Any discussion?</p>

	<p style="font-style: italic;">The PMC approves and thanks Carl for
		his help.</p>

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

	<p style="font-style: italic;">Kaloyan asked about some IBM
		contributions to Libra. Chuck will follow up with Zina.</p>

	<p style="font-style: italic;">Some discussion of "feed back"
		sessions. If/when PMC should discuss. I _think_ conclusion was, Chuck
		would lead more discussion at status meetings, perhaps a "vote" to
		come up with a "top ten" list of most important things that can
		concretely be improved. (Chuck, Raghu, feel free to correct if I
		misheard.)</p>

	<p style="font-style: italic;">There was some discussion of WTP
		migrating to Git:</p>

	<p style="font-style: italic;">Some think we should not do it until
		after Juno. Some think we should at least investigate it more closely
		and come up with a concrete plan, steps, advantages and inhibitors
		(fearing that if we simply "wait till after Juno" then we will be just
		as unprepared then.) Either way, at any time, it will take some
		non-trivial investment in education and transition efforts, so we want
		to be clear on what advantages/requirements there are to do so. The
		advantage of waiting is we can let others work out the kinks in
		software and process, so our transition will be smoother. The
		following actions were agreed:</p>
	<ul>
		<li>Start a Wiki page (Raghu)
			<p>Purpose would be to to list resources/links/experience to "how
				to" and educational material as specific to WTP as we can make it.
				Also to start a list or discussion (with links to bugzilla when
				appropriate) to detail what WTP can do now (or, needs to do, over
				time) to do the migration, or make it easier.</p>
		</li>
		<li>Form a task force?
			<p>Consider, after Indigo SR 1 is done, asking, say, three
				committers representing a cross-section of WTP to form a "task
				force" to do a deep dive on what it would take for WTP to migrate,
				maybe even work in a "sandbox"?, and report back to WTP PMC and
				committers with recommended steps of what steps should come next, or
				concrete steps on getting from cvs to git.</p>
		</li>
		<li>Remind committers how to get educated on git
			<p>Even before WTP migrates, as more Eclipse projects move to
				Git, WTP committers will need to become familiar with Git, to check
				out others code, submit patches, etc.</p></li>
	</ul>

	<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 David Williams.</p>
</body>
</html>