Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Logistics

Dates - July
Schedule  - 9am-5:30pm M-Th, 9am-12:30pm F
Work Location - TBD
Travel Info - Fly into Portland International Airport

Attendees

  1.  

Not Attending

Goals

  •  

Agenda

Day 1: Monday, July 16th

Location: TBD

9:00 - 12:30

Work

 

 

12:30 - 1:30

Lunch

everybody


1:30 - 5:30

Work

 

 

Day 2: Tuesday, July 17th

Location: TBD

9:00 - 12:30

Work

 

 

12:30 - 1:30

Lunch

everybody


1:30 - 5:30

Work

 

 

Day 3: Wednesday, July 18th

Location: TBD

9:00 - 12:30

Work

 

 

12:30 - 1:30

Lunch

everybody


1:30 - 5:30

Work

 

 

Day 4: Thursday, July 19th

Location: TBD

9:00 - 12:30

Work

 

 

12:30 - 1:30

Lunch

everybody


1:30 - 5:30

Work

 

 

Day 5: Friday, July 20th

Location: TBD

9:00 - 12:30

Work

 

 

12:30 - 1:30

Lunch

everybody


1:30 - 5:30

Work

 

 

Leisure Activities

Notes

Day 1

KNS to KRAD:

  • plans of the apps
  • KC and KFS are looking, have a presentation in September, post 2.2 to help them along
  • Rice projects plan to convert from KNS to KRAD
  • Plans for tooling and conversion
  • 2.2 - help and dialog in scope, had a milestone item for lookup and maintenance functionality
    • going to be at a pretty good point for people to start looking at it
    • i would like for it to be as smooth as possible
  • if we did our upgrade first that would help get the issues out there
  • we should look at implementing JPA and converting existing KNS applications

KRAD Architecture and Vision and Random stuff Discussion:

  • should be able to get started quickly
  • would be nice to be able to bring up a simple client application skeleton without any external dependencies on Rice standalone server or without a need to bundle the entirety of Rice
  • parameter service puts a dependency to remote service right away
  • should be able to use doc framework without KEW
  • establishing conventions...
  • Data Dictionary should be able to "enrich" information available in DB metadata or in the ORM
  • In the Data Dictionary, things should have reasonable defaults as much as possible
    • DB -> ORM -> POJO -> DD
    • default in from lowest layer up and allow overrides at each level
  • Modular architecture
    • easy way to "extend" and plugin
    • make it easy for people to publish/create their own stuff
      • similar to rubygems/github
      • publish to clearinghouse
    • use OSGi or Jigsaw to drive this architecture?
  • Data access should be flexible
  • Messages for I18N - mapping them in rather than having to point out with a key...
  • A better/more consice way to define the UI for KRAD, Spring XML being very verbose
  • XStream is a problem...should look at other default options for maintenance framework (i.e. new column in the db?)
  • HTML5
  • Integration with Mobile
  • separate versioning/packaging of KRAD vs. the Rice Middleware Stack?
  • Action Item: Develop a vision document for KRAD (whitepaper) and create roadmap items from those and present to ARC/TRC. Eric will take the first stab at this.
  • No labels