Location

(Back to the DMCCB page)

Time

From 12.30 to 13.00 PT, Tuesday January the 15th.

Attendees

• Wil O'Mullane
• Unknown User (gcomoretto)
• Leanne Guy
• Tim Jenness
• Margaret Gelman
• John Swinbank

Regrets

• Kian-Tat Lim 

DMCCB Meeting Goals

• See DMCCB responsibilities listed in LDM-294 section 7.4 (see also changes in https://ldm-294.lsst.io/v/RFC-561/index.html )

First DMCCB (kickoff meeting)

• Agree on Responsibilities as per LDM-294:
  • Determine when deliverables (controlled documents and software) are of sufficient maturity and quality to be baselined (placed under configuration controlled status) or released.
  • Review and approve/reject proposed changes to baselined items - any LCR must go through the DMCCB
  • Review and approve/reject proposed changes to the planned releases and their content
  • Review  all RFCs and and approves ’flagged ’ RFCs
  • Monitor DM Jira issues status (in support to the monitoring activity done by J.Swinbank )
  • Ensure that the DM Technical Baseline (LDM-xxx) documents  follow  LSST and DM configuration control processes
  • Monitor and approve  DM software releases
• Agree on Membership as per LDM-294:
  • Core members: 
    • DM Project Manager (or deputy)
    • DM Subsystem Scientist (or deputy)
    • DM System Engineer (DMCCB chair)
    • DM Operations Architect
    • Software Architect
    • DM Configuration and Release Manager (DMCCB Secretary)
  • Optional Members (involved when topics require their expertise):
    
    • Pipelines Scientist
    • Science Pipelines / Interface Scientist
    • T/CAMs

Discussion Items

Meeting outcome

Wil O'Mullane chaired the meeting, explaining the intention to have a body smaller than the DMLT, that requires a smaller quorum to take decisions.

The DMCCB reviewed the list of core members

• No objections have been raised
• There is the need to identify a time in the week where all core members can participate

• • Kian-Tat Lim revisit doodle poll to see if there is any way to make it work 18 Jan 2019 
  • Leanne Guy revisit  doodle poll  to see if there is any way to make it work 18 Jan 2019 

• The DMCCB will be chaired by Tim Jenness
• The DMCCB will meet weekly, and skip if there are no agenda items

The DMCCB reviewed the the proposed responsibilities. Some small changes have been made:

• Agreement has been reached that DMCCB core members will monitor all RFCs and ensure that the ones relevant for the DMCCB are flagged (changes to LDM documents, API changes, data model changes)
• For all proposed LCR to the LSST CCB, an RFC shall be submitted and approved by the DMCCB before submission of the LCR

• Unknown User (gcomoretto) update LDM-294 to describe cases for which an RFC needs to be flagged (LDM docs, API and DB Schema changes). Update deprecation policy in dev guide/ and state which RFC needs to be flagged to be consistent with LDM-294 22 Jan 2019 
• All DMCCB core members to ensure that they agree with all proposed responsibilities. 22 Jan 2019