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 "Equinox Summit 2007 topics"

(New page: * Jeff McAffer ** More contributions. This might be a meta-topic but there are likely tangible steps that the current team can take to be more open to new contributions. ** Security direc...)
 
Line 4: Line 4:
 
** Services.  Prosyst has contributed several new services recently.  We should review these with an eye to graduating and integrating them into the main stream.
 
** Services.  Prosyst has contributed several new services recently.  We should review these with an eye to graduating and integrating them into the main stream.
 
** PDE build.  How can we make it better (incremental, easier to setup, ...) and  how will the provisioning work impact build.
 
** PDE build.  How can we make it better (incremental, easier to setup, ...) and  how will the provisioning work impact build.
 +
 +
* Chris Aniszczyk
 +
** PDE Build. How can we tool PDE Build... in terms of having an easy way to get a user started with an automated build. Similar to how PDE provides a .product file for helping build/package RCP applications, maybe we need something similar for an automated build.
 +
** PDE and "Components." PDE has notions of groups of plug-ins in various places... (target definitions, product files, features, etc...) does it make sense to abstract this concept out a bit so it can be reused by other places.
 +
** PDE and Provisioning. How will tooling for provisioning work, what happens to features and update sites?

Revision as of 10:21, 26 June 2007

  • Jeff McAffer
    • More contributions. This might be a meta-topic but there are likely tangible steps that the current team can take to be more open to new contributions.
    • Security directions. We have new contributions for JAAS, JCA, Keystore etc. Lets talk about where this work will take us
    • Services. Prosyst has contributed several new services recently. We should review these with an eye to graduating and integrating them into the main stream.
    • PDE build. How can we make it better (incremental, easier to setup, ...) and how will the provisioning work impact build.
  • Chris Aniszczyk
    • PDE Build. How can we tool PDE Build... in terms of having an easy way to get a user started with an automated build. Similar to how PDE provides a .product file for helping build/package RCP applications, maybe we need something similar for an automated build.
    • PDE and "Components." PDE has notions of groups of plug-ins in various places... (target definitions, product files, features, etc...) does it make sense to abstract this concept out a bit so it can be reused by other places.
    • PDE and Provisioning. How will tooling for provisioning work, what happens to features and update sites?

Back to the top