Jump to: navigation, search

COSMOS Management Enablement

Revision as of 14:42, 23 December 2008 by Jason.losh.sas.com (Talk | contribs)

COSMOS Main Page


Management Enablement

Meeting Title: COSMOS Management Enablement Weekly Meeting
Link to information on Wiki:
Date & Time: Tuesday at 11:00 EDT / 11:00am EDT
Toll-free Dial-in number: 1-888-682-4285
Primary International Dial-in: + 1-973-368-0695 (Requires International prefix first)
SAS Employees: x40000
Conference Code: 3358100246

Contact

Email [Jason Losh]


Working Design Documents

Misc Documents

Agenda (12/16/08)


Agenda (12/9/08)

Agenda (12/2/08)

  • 1.1 plans
    1. Need ERs identified for i1 as well as designs
    2. i1 ends 1/9/09
  • Change analyzer status
    1. Copyrights updated - need someone w/ delete authority to remove the old CA - Jason to find the right person and explore getting delete authority
  • BTG update
    1. Rules status - sprint to December update
  • Change resolver status update
  • P2 integration update
  • SDD alignment with the reconciliation taxonomy (RTX)
    1. For software resources do we need inheritence/hierarchy?
    2. RM team meets Wed at 9AM as part of architecture call - need participants
  • Around the room

Agenda (11/25/08)

  • 1.1 schedule overview
    1. http://www.eclipse.org/projects/timeline/index.php?projectid=technology.cosmos
    2. Iteration 1 ends 1/9/09
    3. GA date set at 6/26/09
  • Change analyzer status
    1. Copyrights updated - will check in source this week
  • BTG update
    1. Rules status
  • Change resolver status update
  • P2 integration update
  • SDD alignment with the reconciliation taxonomy (RTX)
    1. SDD needs from an information model
    2. Separate resources from usage?
    3. Resources defined in a "dictionary" -- the words
    4. Usage -- the grammar for how to use the words
    5. Participation in RM group to align efforts

Agenda (11/18/08)

  • COSMOS 1.0 RELEASED!
    1. http://www.eclipse.org/cosmos/project_info/cosmos_V1.0_announcement.php
  • Change analyzer status
    1. Submission package conditionally approved
    2. Need to clean-up some copyright notices in generated classes
  • BTG update
  • Change resolver status update
  • P2 integration update
  • SDD alignment with the reconciliation taxonomy (RTX)
    1. SDD needs from an information model
    2. SDD "profile" -- how would we support varying usage patterns?

Agenda (11/4/08)

  • Change analyzer status - awaiting IP approval
    1. JAXB declared and approved as a dependency
    2. Submission package attached and scanned - may seek to check-in under parallel IP process
  • BTG update
  • Change resolver status update
  • P2 integration update

Agenda (10/28/08)

  • Status on Tuscany replacement with JAXB
  • Change resolver status update
  • P2 integration update
  • Growing the community

Agenda (10/21/08)

  • SDD tools building and included in the download - be sure what is expected is there
  • Discuss for inclusion in COSMOS 1.0:
    • 240065 - Document APIs for SDD Programmatic Interface
  • Status on Tuscany replacement with JAXB
    1. We are good to go with using JAXB - need to know version so it can be declared as a dependency in Orbit
    2. We will not change the Java requirement for COSMOS 1.0+
  • Change resolver status update
  • P2 integration update
  • Growing the community

Agenda (10/07/08)

From Eric - Discuss defects for COSMOS 1.0 inclusion:

  • 249652 - SPI outputs incorrect date format for lastModified attribute
  • 249655 - SPI: descriptorID getter/setter should return/take a byte[] instead of String
  • 249349 - SDD Validator JUnits use incorrect Schematron location
  • 249714 - SPI: createAdditionalContent() creates element with incorrect attribute name
  • 249873 - SDD Validator: Schematron validation is non-functional
  • Schema checkin status
  • TPTP test checkin status
  • Bugzilla cleanup.
  • Documentation updates for SDD tooling
  • SDD tooling build updates
    1. Saurahb reported a problem building SPI, Validator, and Change Analyzer -- have these been resolved?
  • JAXB implementation for Change Analyzer - requires IPzilla approval from Eclipse Legal OR COSMOS 1.1/2.0 to require JRE/JDK 1.6
  • Change resolver status update


2009 Minutes of prior meetings

2008 Minutes of prior meetings