Skip to main content

WTP PMC Agenda/Minutes for June 29, 2010 Conference Call

WTP PMC Agenda/Minutes for June 29, 2010 Conference Call

Call Info

Tollfree in the US: 877-421-0030
Alternate: 770-615-1247
Access code: 173098#
Full list of phone numbers

Call Time: 8:00 AM Pacific; 11:00 AM Eastern; 1500 UTC


PMC Members

  • David Williams: Y
  • Naci Dai: N
  • Raghunathan Srinivasan: Y
  • Neil Hauge: Y
  • Tim deBoer: Y
  • Kaloyan Raev: R

Announcements and General Business

Any general high level points of how to improve WTP?

Good writeup in Mylin wiki, about "being a contributor"

We didn't discuss much on this call, but was jokingly asked if we need a PR firm? Are we perceived as having closed meetings? (Even though not, lots of notes, public number, etc.). Are we perceived as not being innovative, when we see ourselves excelling in stability? We know the balance between innovation and stability is a hard balance to achieve ... but what leds to one perception over another? Stability is hard to "see"? Only miss it when its gone? Change is especially hard when so many committers are very busy, overbooked, overworked, working on their own things, so changing, even testing, even opening bugs for small breaks can seem like a lot of extra work (unless they understand the importance, reasons, need, etc. Case in point ... Eclipse 4.1 :)

Our plans for Eclispe 3.7 vs 4.1?

We should tentatively plan on supporting/running on both. One set of plugins, hopefully, running in compatibility mode. No current plans to exploit e4-only functionality. We need some experience and builds with it, to know if it is feasible.

Action: dw to send links on info, schedulue, downloads, etc. for 4.0

Faceted project plans

We discussed if latest proposal to wtp-pmc list was "legal" or not ... and we left it that we expect Wayne will clarify if branching/moving code in cvs is really not a move, since it is a branch (sounds like a move, but ... it is EPL code?), and if another project can release its own version of WTP namespace bundles/features? That would seem to break a lot of co-existence installs. If everything released as "product" it technically would be possible, but then PHP could not be installed into WTP (as an example, if PHP adopted new Technology code, and WTP did not). And it would be bad/hard to release everything as a "product". Whether legal or not, we could not really see the purpose (other than POC), or how it would work in practice, and seemed like a hard path to go down. So we expect more discussion.


What became of these?

  • WTP @ GSoC 2009. There are two project accepted:
    • Index search for Java EE metadata. See bug 233505
    • Embed OpenEJB in J2EE Preview server adapter. See bug 265952

Back to meeting list.

Please send any additions or corrections to David Williams.

Back to the top