Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[corona-dev] Corona Meeting Minutes - June 13, 2006

 

Corona Meeting Minutes - June 13, 2006

 

http://www.eclipse.org/corona/

 

Progress on Last Weeks Tasks

  • Slow progress on Project Join

 

Action Items

  • Debug use case for Project Container
    • Owner: unknown – suggested by Joel Hawkins
    • Status: open
    • Due: June 27, 2006
    • Notes:  Select a set of Specific Eclipse Projects from the set of Eclipse Project for debugging, Project Explorer use case. ???
  • Add Ant Tasks for Starting Corona Server and Client for Automatic Testing:
    • Owner: Dennis O’Flynn, Pawel
    • Status: open
    • Due: June 27, 2006
    • Notes: The bugzilla package names need update to match the updated corona package names.
  • Update Bugzilla package names:
    • Owner: Dennis O’Flynn
    • Status: open
    • Due: June 13, 2006
    • Notes: The bugzilla package names need update to match the updated corona package names.
  • Implementation: WSDM Packaging
    • Owner: Joel Hawkins
    • Status: done
    • Due: June 13, 2006
    • Notes: The packaging will include some code packaged with Apache and some code packaged with Corona – still in progress
  • Implementation: OSGi Packaging
    • Owner: Joel Hawkins
    • Status: open
    • Due: June 27, 2006
  • Design: Project Container
    • Owner: Glenn Everitt
    • Status: open
    • Due: June 13, 2006
    • Notes: put initial Project Container code into Corona CVS Incubator, need a consistent set of code including Corona Core Code from Joel  
  • Design: Project Container Turnover
    • Owner: Glenn Everitt, Edyta Kalka
    • Status: open
    • Due: June 27, 2006
    • Notes: turn over Project Container Code use VNC to get Edyta’s build working  
  • ECF / Collaboration Framework Sequence Diagram
    • Owner: Jim Wright 
    • Status: obsolete
    • Due: May 16, 2006
    • Notes:
  • ECF Chat for Corona Developers Set up
    • Owner: all
    • Status: pending: usage delayed due to firewall issues
    • Due: May 16, 2006
    • Notes: Network Support is working on monitoring setup
  • Preliminary Design: Corona “core” server
    • Owner: Joel Hawkins
    • Status: open
    • Due: May 23, 2006
    • Notes: post design to Corona wiki
  • Preliminary Design: SOA Web Services
  • Preliminary Design: Knowledge Base (Semantic Framework)
    • Owner: Glenn Everitt
    • Status: open
    • Due: June 20, 2006
    • Notes: post design to Corona Wiki
  • Build Process: Automate Testing
    • Owner: Pawel Kaczmarek
    • Status: open
    • Due: June 6, 2006
    • Notes: update build process to automate execution of unit test
  • Collaboration View GUI
    • Owner: Pawel Kaczmarek, Edyta, Marcin
    • Status: open
    • Due: ongoing
    • Notes:  see links to Compuware Usability Website for icons,  Brian Roberts will contact Dave Mitropoulos-Rundus (MR) about usability help from Yelana Babin

 

 

Topics:

 

ECF2 – Enterprise Component Framework how does this compare with Corona?

 

Server Side Startup

  • Pawel suggested making Corona a Server Side Application,  several other not sure this is the correct approach
  • Joel suggest using the OSGi declarative services
    • Glenn thought Immediate Service would be a solution but the Declarative Service Bundle itself needs to be started as well as the bundles implementing immediate services so more research into starting the Declarative Service Bundle and its Immediate Services before executing other bundles.

 

Corona Core

  • Joel working on packaging of SCA bundles?
  • Will revisit AbstractManagedContainer would manage all Container properties or just WSDM based properties
  • Glenn has been working on Corona Core to get enough working for the Join use case

 

Corona WSDM – Joel

  • Nearly complete with reintegration of new Muse 2.0 drop with Corona Core Code
  • Work creating the distribution as OSGi bundlesbuild meeting Thurs about OSGi with Daniel, Weitzel

 

Project Container – Glenn

  • Reading configuration from ZipConfigurationStore works
  • Started discussing issues regarding nested ProjectConfigurations
  • Started documentation of the communication flow using ECF connector between Collaboration Client and Collaboration Server – Dennis created a sequence diagram for this it still needs to be posted on wiki  
  • Working on implementation of Project Join user story

 

Project Container Client – Marcin, Edyta, Pawel

  • Work on implementation of Project Join user story from RCP client side – next 3 weeks

 

Collaboration View/Feature – Edyta, Marcin, Pawel

 

  • Collaboration View needs a way to display hierarchical set of Projects within Eclipse.
  • Investigate feature implementation for Collaboration Client update package to be posted on eclipse download site – Any progress?
  • Memory Usage grows with every event since they are kept in memoryAny progress?

-          Look at TPTP Common Base Events as a format to save the events

-          Find the Common Base Event Viewer and see if it is useful for looking at the event file logs

  • Icons/Graphics needed for Collaboration View – had a brief meeting about the icons usability group needs a long lead time since very busy.  Yelana will probably be doing the work
  • Corona Team will try to create a batch of icons to be done all at once so that they are built with a consistent look and feel.
  • The Collaboration View should be working on Linux.

 

 

Join User Story – Edyta, Marcin, Pawel, Glenn

  • How do we support nested ProjectContainers – ongoing discussion
  • Client Side needs a way to retrieve, hold, synchronize with ProjectContainer Hierarchical Structure from Corona Server.
  • Request / Response protocol to be built on Web Service calls from Client to Server code
  • Old Items

-          User story: http://wiki.eclipse.org/index.php/SharedProjectUserStory_1

-          Use case: http://wiki.eclipse.org/index.php/Corona_Use_Case_Project_Join

-          Web Service call Get List of ProjectContainers returns list of ProjectContainer names

-          User selects name from List and calls Web Service call to add User

-          Allow different client project names to be associated with a singe ProjectContainer

-          How to handle File New Project wait until Collaboration Nature is added to associate with ProjectContainer?

-          How to handle File Import Project –defer until after New Project is completed

 

Project Container Server/Client

  • Glenn sent initial cut of ProjectContainer interface for Review see corona-dev for postings
  • Need to decide on client-server communication will be done with Web Service Calls
  • Working on creating and expose IProjectManagerContainer interface, through AOP

 

Build – nothing new

  • Corona Server and Client need to execute at the same time for automated testing to work
  • The Corona Client Testing should not be started until Corona Server is running and available
  • Dennis and Pawel will work on Ant Parallel Target to start Server and Client Test execution
  • Corona will be built with projects using JDK 1.4 as the default and only some projects with dependencies on JDK 1.5
  • Build instructions are posted see Wiki on build: http://wiki.eclipse.org/index.php/Corona_Development_Build
  • The Build works on Linux too (run.sh and buildCorona.sh are created)

 

JUnit Testing - Pawel

  • Need a way to start both Client Eclipse and Corona Server for testing
  • Ongoing

 

 

Useful Links

 

Corona Wiki

http://wiki.eclipse.org/index.php/Corona_Development_Community

 

Corona Build Wiki

http://wiki.eclipse.org/index.php/Corona_Development_Build

 

Corona Conference Call will be scheduled on Google Calendar with iCal

http://www.google.com/calendar/ical/uqdmjoagam1374s3erc3i7scrc@xxxxxxxxxxxxxxxxxxxxxxxxx/public/basic

 

additionally there is an atom feed at:

http://www.google.com/calendar/feeds/uqdmjoagam1374s3erc3i7scrc@xxxxxxxxxxxxxxxxxxxxxxxxx/public/basic

 

 

 

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top