Attendees * Hank Mauldin - Cisco * Drummond Reed - Parity
* Jim Sermersheim - Novell
* Brian Walker - Parity
- We are planning to do M5 build tomorrow 16-Jan.
- Have updated the M5 wiki page (link above), created new link for M6 milestone build (http://wiki.eclipse.org/Higgins_1.1M6) as well as sent out an update status email.
- In parallel to this, have started working on a milestone based plan in support of Higgins 1.1 candidate tasks (http://wiki.eclipse.org/Higgins_1.1_Plan). Currently focusing on just identify what items off this list have the best probability, based on priority of being completed for a June Higgins 1.1 release goal.
2. [Hank] Higgins White Paper Progress update. - Have started the white paper and currently in very rough draft state. Will release the rough draft in near future to offer more specific insight on what additional content is needed. Will need help in creating content in several areas (solution and component level technical details) Would ask that appropriate domain experts collaborate with Hank and contribute content to this white paper. The goal is to publish the white paper on concert with the Higgins 1.1 release targeted for June of 2009.
- Also developing ideas of including stories to show the value proposition of Higgins, and what problems Higgins can solve. Will touch base with Drummond on data portability concepts and how this can be positioned. Will also include thoughts of future Higgins directions as well.
- Major thrust around solutions and what problems it can solve and where Higgins is headed in the future.
- It would ideal to have as part of Higgins 1.1 release, a bundled deployment package to enable a rapid lab-based deployment without having to do manual builds.
3. [Brian, Andy, Alexander] Selector Architecture Harmonization
Project update [1]
- We had initial kickoff discussions this week with Andy H. and Alexander about next steps to develop a functional prototype in the model of that outlined in link [1] below. The goal is to have a working prototype by mid-Feb as an operational proof point.
- The initial next step is to define the existing I-Card Service API that could be consumed by the proposed client for basic card operations (including cache and card synchronization, card history, remember card pw etc).
- As these definitions and details become available, they will be shared with Higgins dev community via updated posting on the Higgins wiki page noted in [1]. It is estimated that there won't be any material, content substantial updates for another 2 weeks.
Links [1] http://wiki.eclipse.org/Selector_Architecture_Harmonization
Brian Walker =brian.walker VP of Engineering Parity Communications Inc cell: 781-801-0254
|
