Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Planning Council/Dec 03 2008"

m
m (Regrets)
Line 15: Line 15:
 
=== Regrets ===
 
=== Regrets ===
 
* Karsten Schmidt
 
* Karsten Schmidt
 +
* Markus Knauer (I'll try to be on the conference call, but I am not sure if I can make it...)
 
* TBD
 
* TBD
  

Revision as of 12:03, 3 December 2008

Meeting Title: Planning Council Conference Call
Date & Time: Wednesday Dec 03, 2008 at 1600 UTC / 0900 SFO / 1200 NYC / 1700 London / 1800 Berlin
Dial-in: For the call-in numbers, please see the Portal page.

Attendees

  • TBD

Regrets

  • Karsten Schmidt
  • Markus Knauer (I'll try to be on the conference call, but I am not sure if I can make it...)
  • TBD

Topics

  • Bundles as jar requirement: applies to source jars as well? See bug 252800
  • Capabilities, the next round of defining this requirement. See bug 252807
  • TPTP questions on requirements (see below)
  • Provider names in the About dialog. See bug 198941
  • Continue discussion of SDK Composition

Reminders

  • December 10-11, 2008 - plenary session with Board

Additional Topics

  • TBD

TPTP Questions

There has been much discussion regarding the Must and Should do's for Galileo. At today's TPTP PMC call, we went over each of the Must and Shoulds with regard to TPTP and also with regard to the others on the train.

We weighed the effort for each against the expected benefits for each. Overall, we thought the list was fine. We have the following comments:

  • New and Noteworthy - the bugzilla

(https://bugs.eclipse.org/bugs/show_bug.cgi?id=252805) says that these are done on each milestone. The Requirements page (http://wiki.eclipse.org/Galileo_Simultaneous_Release#Requirements_For_Participation) says RC (Release Candidate). TPTP agrees with this for the Release Candidate but it seems a bit much to have it as a must do for each and every milestone.

  • Capabilities - TPTP will provide a single point of capability 'TPTP'

in a plugin that will enable user to disable/enable TPTP UI contributions (import/export, launch configurations, views, preferences, and perspective). 254151 is already opened by Anne for such requirement. Does this single point comply with the must do?

  • Also, we have a question regarding dependencies as TPTP has features

that depend on other projects (e.g., Profile on server has a dependency on WTP). Do we leave the choice to the user or do we act smart and enable all the optional dependencies for the user?

  • Performance - Please add that TPTP is appropriate for profiling and

performance work. As you know, we are putting resources into the community profiler and this is exactly the kind of thing that we are trying to encourage. We will do good support.

Action Items

  • Send out a note to mailing list when Galileo plan.xml is visible (Rich)
  • Send out a note with instructions on how to update build contribution files (Rich)

Carry over items

  • Look into having a "name that train" contest to coincide with EclipseCon each year (artwork as well?) (Bjorn)

Back to the top