Difference between revisions of "Equinox Summit 2007 topics"

From Eclipsepedia

Jump to: navigation, search
Line 50: Line 50:
 
** Programming models: Can we leverage the lazy activation model in the OSGi extender models (DS, spring etc.).  Will this make DS and other extender models more attractive to the Eclipse community?
 
** Programming models: Can we leverage the lazy activation model in the OSGi extender models (DS, spring etc.).  Will this make DS and other extender models more attractive to the Eclipse community?
 
** Programming models: Interests in DS vs Spring.  What should Eclipse use, if any, and what are the tooling considerations.
 
** Programming models: Interests in DS vs Spring.  What should Eclipse use, if any, and what are the tooling considerations.
 +
 +
* BJ Hargrave
 +
** Discuss subdividing equinox.bundles component: what is helpful in getting more clarity and participation in the various bundles under the Equinox umbrella. Should we do more bugzilla components? Should we do more commit groups? Do some level of (arbitrary) grouping help. We need to agree on what the goals are for subdivision to decide if some particular subdivision is useful.
 +
** Set up a branch (or something else) for development of the framework (and other bundles) RI for the next release of the OSGi specifications (since 3.4 will probably ship before OSGi spec closes.)
 +
** Discuss what is coming in the next OSGi specification release and impact on Equinox.
 +
** Discuss what in Equinox can/should be brought to OSGi for standardization. e.g. Extention Registry, P2, etc.
 +
  
 
== Interests by topics ==
 
== Interests by topics ==

Revision as of 15:28, 14 September 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?
    • PDE Build and Incremental Build. How do we make PDE Build do incremental build? How does this intersect with provisioning?
  • Scott Lewis
    • Security: Authentication and platform login. Integration of JAAS. Extension points and services for extensibility? see https://bugs.eclipse.org/bugs/show_bug.cgi?id=200299
    • Security: Any connection between login and profiles in provisioning? Can login be tied to a certain profile/class of profile (e.g. role)?
    • Framework: Spring-OSGi support?
    • Bundle distribution: How to allow component-level (groups of plugins, with various dependencies) be easily distributed/installed? How do (bundle) repositories (e.g. OBR, JSR-something) fit in?
    • Related to bundle distribution: How to support EF project component distribution (without features).
    • PDE: Accessing PDE programmatically: Need PDE APIs...e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=169340
    • ECF: what enhancements are needed for file transfer both at API and impl: e.g. pause/resume enhancements, file caching, monitoring/transfer statistics collection?, support more/other providers, etc.
    • ECF: How to get/test/make available more providers (e.g. bittorrent, custom protocols, etc).
  • Pascal Rapicault
    • Explore the intersection of the equinox provisioning and security work. Is the intersection secure provisioning, what does that mean, does it need to be built-in?
    • What integration are we seeking between PDE (UI/Build) and equinox provisioning?
    • Looking forward with PDE Build, should we just build in the workspace?
    • Making multi-user / shared install scenarios first class in the new provisioning story
    • In the previous update manager, transport was the number one source of complaints from the community (freezing download, various proxy pb, https, etc.). Are we on track to do better? What are we missing (e.g. auto detection of proxy settings from the OS, test suites), does that translate in any requirement on ECF?
  • Stefan Liebig
    • Incorporating of post processing steps. With the introduction of post processing (e.g. unpack200, deltas) an artifact key is no longer a unique id for picking an artifact. There might be multiple artifact descriptors all with the same artifact key but different post processing. How does this affect artifact repository, download manager,..?
    • Logging. Logging is an essential tool for checking the health of deployed applications and tracking down problems. There are a lot of attempts in this area. Is there a preferred solution in sight?
    • Security and provisioning. Authentication and authorization (JAAS) are necessary for a controlled provisioning (governance). Trusted connections to ´update sites´ (client trusts server/server trusts client) are a requirement for secure applications (banking/finance). How does that impact provisioning?
  • John Arthorne
    • Programming models: Coming up with an easier client story for service lookup; scalable (lazy starting) declarative services
    • Tooling: Interested in defining what is API, what constitutes breaking vs. compatible changes
    • Provisioning: Filtering and selectors on dependencies, director resolution algorithm, repository APIs; support for installs with multiple bundle pools; server-managed clients.
  • Oleg Besedin
    • Framework: extension registry – discuss possible scenarios for future growth. How much dynamic support do we need?
    • Framework: component models in general – extension registry, OSGi, DS. Are we there yet?
    • Tooling: API tooling – what we have now; where we would like to be. Discuss common repository for API and reference information to be used by a mix of open source and commercial developers. Usage of Javadoc tags to specify API rules.
    • Security: What are the real needs of end users / developers / administrators? The org.eclipse.equinox.security contribution for JAAS support.
  • Tom Watson
    • Framework: Constraint resolving implementations. How to tackle the NP-Complete problem of the OSGi constraint resolver.
    • Framework: Security/Trusted bundles what it means to enable this at runtime.
    • Future OSGi work: How much change to the core Framework will the new Enterprise Expert Group require? Is it time to consider a major restructure of the Framework implementation? What would we gain or loose from such a large undertaking? and who would contribute?
    • Programming models: Can we leverage the lazy activation model in the OSGi extender models (DS, spring etc.). Will this make DS and other extender models more attractive to the Eclipse community?
    • Programming models: Interests in DS vs Spring. What should Eclipse use, if any, and what are the tooling considerations.
  • BJ Hargrave
    • Discuss subdividing equinox.bundles component: what is helpful in getting more clarity and participation in the various bundles under the Equinox umbrella. Should we do more bugzilla components? Should we do more commit groups? Do some level of (arbitrary) grouping help. We need to agree on what the goals are for subdivision to decide if some particular subdivision is useful.
    • Set up a branch (or something else) for development of the framework (and other bundles) RI for the next release of the OSGi specifications (since 3.4 will probably ship before OSGi spec closes.)
    • Discuss what is coming in the next OSGi specification release and impact on Equinox.
    • Discuss what in Equinox can/should be brought to OSGi for standardization. e.g. Extention Registry, P2, etc.


Interests by topics

At the recent gathering we tried to estimate how many people registered for the summit would be interested in each of the four topics. We ended up with something like:

Topic # of People
Framework 7
Provisioning 16
Server Side 5
Tooling 9