Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[corona-dev] Corona Meeting Minutes - May 24, 2006

 

Corona Meeting Minutes - May 24, 2006

 

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

 

Progress on Last Weeks Tasks

  • Corona Collaboration Demo Code is currently committed to CVS – Yea!

 

 

Action Items

  • ECF / Collaboration Framework Sequence Diagram
    • Owner: Jim Wright 
    • Status: open
    • 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
  • Collaboration Demo: Prepare for initial commit to Eclipse Corona CVS repository
    • Owner: Dennis O’Flynn (Marcin, Edyta, Pawel)
    • Status: closed – yea!!!
    • Due: May 16, 2006
    • Notes: Refactoring to following plugin / package naming
  • Collaboration Demo: release to general public
    • Owner: Dennis O’Flynn (Marcin, Edyta, Pawel)
    • Status: open
    • Due: May 30, 2006
    • Notes: post zip file download and instructions setup up and running demo
  • Build Process
    • Owner: Edyta Kalka
    • Status: closed
    • Due: May 23, 2006
    • Notes: refactoring to follow plugin / package naming
  • Simple Mock up of Collaboration View
    • Owner: Edyta Kalka, Pawel Kaczmarek, Marcin Okraszewski
    • Status: closed
    • Due: May 23, 2006
    • Notes: merging new view(s) with existing demo code
  • 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
    • Owner: Joel Hawkins
    • Status: open
    • Due: May 23, 2006
    • Notes: post design to Corona wiki
  • Preliminary Design: Build Process
    • Owner: Edyta Kalka
    • Status: ongoing
    • Due: May 30, 2006
    • Notes: post design to Corona wiki, Dennis will create initial page
  • Preliminary Design: Project Container
    • Owner: Glenn Everitt
    • Status: closed
    • Due: May 23, 2006
    • Notes: post design to Corona wiki
  • 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

 

 

Topics:

 

ECF Chat – Compuware Network Security is currently working on giving us access, should be available to others

 

 

Package/Plugin Naming

  • plugins should match package names
    • longer but less confusing
    • Agreement to use qualifier (‘client’, ‘common’, ‘server’) in plugin and package names
    • See wiki for structure and naming conventions

 

Collaboration Demo Code Check In – Jim, Dennis, done

 

Corona Core – Joel

  • Had a couple of conversations with Glenn about Core – plan on implementing an AbstractManagedContainer class to handle getting/setting properties
  • I don’t remember if AbstractManagedContainer would manage all Container properties or just WSDM based properties
  • stopped working on Corona Core to work on Corona WSDM - again
  • received new drop of Apache Muse code, which is supposed to be put into Apache CVS respository this week

 

Corona WSDM – Joel

  • Downloaded and rebuilt the newest Apache Muse 2.0 drop
  • Updated Corona Core Code to work with new Muse 2.0 drop
  • Working creating the distribution as OSGi bundles – meeting Thurs about OSGi with Daniel, Weitzel
  • The packaging will include some code packaged with Apache and some code packaged with Corona – still in progress
  • Resolving with Mark/Daniel how to deal with the dynamic nature of OSGi-based resources with respect to WSRF’s more static view of the world.

 

Project Container – Glenn

  • Writing basic design and API information to be posted on Corona Wiki
  • Trying to abstract out any ECF communication information
  • Working on defining an AbstractRepository object so that ProjectContainer can reference Resources through the Respository objects via a URI based identifier
  • Needs to allow different Corona Collaboration Clients with different Project names to refer to the same ProjectContainer. 
  • Started documentation of the communication flow using ECF connector between Collaboration Client and Collaboration Server – will post on Corona Wiki
  • Need to figure out how to add preliminary code to add an incubator folder that would mirror structure of main project folders.
  • Put preliminary ProjectContainer code into incubator folder
  • Work on implementation of Project Join user story – next 3 weeks

 

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

  • investigate feature implementation for Collaboration Client update package to be posted on eclipse download site – ongoing  
  • merged with Dennis’ refactored Collaboration Code which autostarts required services – Yea!!!! No more manual start.
  • update the Collaboration Client View with more information will continue working on better information presentation

-        looks similar to the bookmark view

-        pop-up displays event details

-        add/remove column implemented

-        implemented an action for sorting and filtering events, but it is not defined in the plugin.xml.

-        started internationalization  - column names are externalized and are available in both Polish and English.

 

  • Memory Usage Grows with every event since they are kept in memory

-        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

  • Should the Collaboration View open automatically?

-        Most Views are added by the user to a particular perspective we should follow that until we have a full perspective

  • Icons/Graphics needed for Collaboration View

-        Brian will contact Dave MR and help will usability

-        Brian will send out the Compuware internal usability site to Collaboration View implementors

 

Join User Story – Edyta, Marcin, Pawel, Glenn

  • User story: http://wiki.eclipse.org/index.php/SharedProjectUserStory_1
  • Use case: http://wiki.eclipse.org/index.php/Corona_Use_Case_Project_Join
  • Get List of ProjectContainers
  • User selects from List (starts action)
  • Request / Response protocol built on ECF but abstracted so ECF specific code is not coded into Client  or Server code
  • Allow different client project names to be associated with a singe ProjectContainer
  • Determine how ECF can support a conversation between one client RCP and one  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

 

Build

  • Working on using Headless Eclipse for build
  • Features were added so build will create two separate distributions
  • zip archives containing required plugins for a client and a server distribution are now built
  • plug-ins/bundles were updated to be built based upon new naming conventions and packages
  • Build instructions are posted to the corona-dev list -in process

-        There are 2 build types: client and server see Wiki on build: http://wiki.eclipse.org/index.php/Corona_Development_Build

 

JUnit Testing

  • Need to work on adding automatic junit testing to the build process
  • Need a way to start both Client Eclipse and Corona Server for testing
  • Eclipse automated testing uses JUnit4 that requires Java 5. Can we assume that Java 5 is available for automated testing?
  • Test plugin and feature have been created and prepared for automated testing.
  • Initial changes have been made to the build process.
  • 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