- David Williams: Y
- Naci Dai: N
- Raghunathan Srinivasan: Y
- Neil Hauge: Y
- Tim deBoer: N
- Kaloyan Raev: Y
- Chuck Bridgham: Y
Announcements and General Business
Discuss and document change in PMC Lead.
While we have discussed this for several weeks, the purpose of this agenda item is to document our proposed plan:
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.
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".)
But, under the current circumstances, having current members agree with the plan will undoubtedly make the Board's decision easy and non-controversial.
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.
The plan is to have this change proposed (on the agenda) at the next Eclipse Board meeting agenda, on 9/21.
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.
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.
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.
Nomination was done on wtp-dev list, with 4 of 5 +1 votes. (Tran has been on vacation.) Does the PMC approve? Any discussion?
The PMC approves and thanks Carl for his help.
Other Business ... ?
Kaloyan asked about some IBM contributions to Libra. Chuck will follow up with Zina.
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.)
There was some discussion of WTP migrating to Git:
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:
- Start a Wiki page (Raghu)
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.
- Form a task force?
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.
- Remind committers how to get educated on git
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.
Future Agenda items
- Discuss our model and assignments of "PMC Roles". Do they still make sense?
Back to meeting list.
Please send any additions or corrections to David Williams.