Corona
Meeting Minutes - May 16, 2006
Progress on Last Weeks Tasks
- No Corona Code is currently
committed to CVS
Action
Items
- ECF / Collaboration Framework
Sequence Diagram
- Owner:
Jim Wright
- Status: open
- Due: May 16, 2006
- Notes:
- Post links to Apache Muse Code
on Jira
- Owner:
Joel Hawkins
- Status: closed
- Due: May 16, 2006
- Notes:
- Get email links listed on the
Corona Web Site
- Owner:
Dennis O’Flynn
- Status: closed
- Due: May 16, 2006
- Notes:
links are posted on Corona’s
website under “Resources”
- ECF Chat for Corona Developers
Set up
- Owner:
all
- Status: pending: usage delayed due to firewall
issues
- Due: May 16, 2006
- Notes:
- Collaboration Demo: Prepare for initial commit to Eclipse
Corona CVS repository
- Owner:
Dennis O’Flynn (Marcin, Edyta, Pawel)
- Status: open
- 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 download and instructions for demo
- Build Process
- Owner:
Edyta Kalka
- Status: open
- 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: open
- 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: open
- Due: May 30, 2006
- Notes:
post design to Corona
wiki
- Preliminary
Design: Project Container
- Owner:
Glenn Everitt
- Status: open
- 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
Topics:
Eclipse Wiki – setup and ready to go http://wiki.eclipse.org/index.php/Corona_Development_Community
- Ready for Design Documentation
to be posted
ECF Chat – Compuware Network Security is currently
blocking access, should be available to others
Package/Plugin Naming
- Possible approaches
- Discussed several alternatives
on how to best organize CVS repository.
- Agreement to use qualifier
(‘client’, ‘common’, ‘server’) in
plugin and package names
- See wiki for structure and
naming convention
Collaboration Demo Code Check In – Jim, Dennis
- Defined new directory structure
to distinguish between Client Code, Corona Server Code, Common Code (code
used both by client and server)
- Refactored to new package news
based upon new directory structure
- Cleaned bundle/plugin
definition files, added about.html, initial version .2, added source code
header (EPL license)
- Fixed some bugs
Corona Core
– Joel
- Had been working on Inversion
of Control (IoC) architecture
- stopped working on Corona Core
to work on Corona WSDM
Corona WSDM
– Joel
- Downloaded and built Apache
Muse 2.0
- Working creating the
distribution as OSGi bundles
- The packaging will include some
code packaged with Apache and some code packaged with Corona
- 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.
- Currently working through
various class loader issues
- Have Muse Core starting up and registering
muse.xml-based resources.
- Have Axis 1.3 redirector
working with pojo’s to deploy POJOs as simple web services.
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
Collaboration View/Feature – Edyta, Marcin, Pawel
- investigate feature implementation
for Collaboration Client update package to be posted on eclipse download
site
- update the Collaboration Client
View with more information will continue working on better information
presentation
- will merge with Dennis’
refactored Collaboration Code which autostarts required services –
Yea!!!! No more manual start.
Build
- Working on using Headless
Eclipse for build – headless just means no user interface
- Starting with ECF build as the
basis for our build
- Need to update the plug-ins/bundles
to be built based upon new naming conventions and packages
- Build instructions need to be
posted to the corona-dev list
- Need to work on adding
automatic junit testing to the build process
- After plug-ins/bundles updated
switch from local build machine to the eclipse build machine
JDK
- Eclipse foundation has not set
a date when projects will start to support JDK 1.5.x
- Corona default should be set to
JDKS 1.4.x until further notice
- However some new Eclipse
Projects already require JDK 1.5.x (Mylar, ECF) so we need to limit the
need for JDK 1.5.x to very specific bundles which need to document
Conference Call will be scheduled on Google Calendar with
iCal
- Marcin will figure out how to
give others access to the calendar
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
Test Staff
- Do we have a test person to
verify milestone code?
-
No we will rely upon the Corona
Community and Corona Committers to do testing
-
Automated Junit Testing during the
build process should be created for every plug-in/bundle
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.
