Skip to end of metadata
Go to start of metadata


Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 761546516 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 761546516

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday January the 30th.

Attendees

Regrets

  • tbd

DMCCB Meeting Goals

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-561 - Getting issue details... STATUS

RFC-538 - Getting issue details... STATUS

  • RFC-561 already implemented before CCB starts
  • RFC-538: draft in docushare LDM-148, LDM-151, DMCCB review docs during the telecon.
    • John Swinbank : document consistent with the actual baseline. If NCSA disagree with the content, that will require a different change request. Status set to Board Recommended.

Proposed RFCs

(to review, do not require DMCCB approval)

RFC-569 - Getting issue details... STATUS

RFC-533 - Getting issue details... STATUS

RFC-563 - Getting issue details... STATUS

RFC-552 - Getting issue details... STATUS

RFC-541 - Getting issue details... STATUS


Adopted RFCs without Triggering issues

(to create implementing DM issues)

RFC-134 - Getting issue details... STATUS

RFC-414 - Getting issue details... STATUS

RFC-423 - Getting issue details... STATUS

RFC-431 - Getting issue details... STATUS

RFC-516 - Getting issue details... STATUS

  • RFC-134: Kian-Tat Lim to withdraw
  • all other RFC have IHS tickets (script to extract this information need to be improved)


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

RFC-449 - Getting issue details... STATUS

RFC-551 - Getting issue details... STATUS

  • RFC-449: the RFC has changed the scope, Kian-Tat Lim is asking if we need to change it or withdraw and open an new one. John Swinbank suggest to withdraw it. DMCCB decided to retire the RFC, that imply the RFC is close (final status).
  • RFC-551 new comments added

RFCs implemented since last CCB

(to review)

RFC-491 - Getting issue details... STATUS

RFC-536 - Getting issue details... STATUS

RFC-530 - Getting issue details... STATUS

RFC-560 - Getting issue details... STATUS

RFC-567 - Getting issue details... STATUS

RFC-398 - Getting issue details... STATUS

RFC-544 - Getting issue details... STATUS

RFC-401 - Getting issue details... STATUS

Informational, no action to be taken by the DMCCB
Changes to the planned releases
  • 17.0 planned for end of 2018, shifted at the beginning of 2019
  • LDM-564 need to be updated

DMCCB to approve scheduled release and patch releases proposal (schedule and content)

17.0 should be ready next week to start

Tim Jenness moved astro_metadata_translator to external to avoid confusions

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity

  1. DM-795 - Getting issue details... STATUS
  2. DM-747 - Getting issue details... STATUS
  3. DM-748 - Getting issue details... STATUS
  4. DM-749 - Getting issue details... STATUS
  5. DM-1089 - Getting issue details... STATUS
  6. DM-1084 - Getting issue details... STATUS
  7. DM-900 - Getting issue details... STATUS
  8. DM-1080 - Getting issue details... STATUS
  9. DM-1081 - Getting issue details... STATUS
  10. DM-746 - Getting issue details... STATUS

All 10 tickets have been closed before the DMCCB starts.

AOB
  • RFC status "BOARD RECOMMENDED" is still needed?
  • Are risks to be discussed by the DMCCB?
  • John Swinbank suggest to have an intermediate state in any case. For documents we don't need implementation tikets. Kian-Tat Lim Board recommended means the CCB approved it, but there are still no triggered issues.
    • Gabriele Comoretto to update the dev guide: DMCCB approve RFCs setting the status to "BOARD RECOMMENDED"; the RFC status is set to ADOPTED once triggering issues have been opened, RFC for the approval of baselined documents do not require triggering issues, and can be set to adopted immediately.
  • Proposal to discussing in the DMCCB risks due soon (in 45 days). This may bring up lots of riscks to discuss. Tim Jenness suggest to add these events to P6. Wil O'Mullane related the rick to the milestone.
    • Discussion on retiring risks that will not be possible to mitigate, like "Adherence to coding standard", that will be difficult to get resources to resolve it.


  • Kian-Tat Lim ask where the scripts to generate the list are: in lsst-sqre/sqre-jirakit


Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
Gabriele ComorettoDMCCB#60 (2020 - 08 - 05)
Kian-Tat LimDMCCB#60 (2020 - 08 - 05)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)