Data Management
Space shortcuts
Page tree
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, May the 22nd.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-596 - Getting issue details... STATUS Planned end: May/19/2019

RFC-593 - Getting issue details... STATUS Planned end: Jun/14/2019

RFC-581 - Getting issue details... STATUS Planned end: Mar/15/2019

  • RFC-596: KT will comment on it
  • RFC-593: still due date in the future, no action for now
  • RFC-581
Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-585 - Getting issue details... STATUS Planned end: Jun/14/2019

  • No actions to be taken by the DMCCB

Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None



RFCs adopted since last CCB

(to review, no action required)

RFC-597 - Getting issue details... STATUS


RFCs implemented since last CCB

(to review, no action required)

None


Changes to the planned releases
  • 18.0 Release to be planned
    • start working end of May with due date end of June

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-946 - Getting issue details... STATUS
  2. DM-3655 - Getting issue details... STATUS
  3. DM-4664 - Getting issue details... STATUS
  4. DM-4684 - Getting issue details... STATUS
  5. DM-4618 - Getting issue details... STATUS
  6. DM-4621 - Getting issue details... STATUS
  7. DM-4737 - Getting issue details... STATUS
  8. DM-4738 - Getting issue details... STATUS
  9. DM-4629 - Getting issue details... STATUS
  10. DM-2697 - Getting issue details... STATUS

4053 unresolved issues (4051 on May the 15th)

John Swinbank notes:

  • DM-946 is outside my area of expertise. I assume Qserv isn't still hard-coded to use a salnikov/qserv-run/2014_05.0 directory, so this may be resolved, but I haven't checked.
  • DM-3655 likely still valid.
  • DM-4664 → Won't Fix.
  • DM-4684 — Suspect this material is out of date, but should check with Jonathan (when he returns) before closing this.
  • DM-4618 — I suggest this can't be “Won't Fix”ed with the agreement of the DM-CCB.
  • DM-4621 — Still valid in principle. Upcoming changes to Exposure may be relevant here; would not schedule work here until they are done (and, if we are smart, the documentation will be written as part of that implementation.)
  • DM-4737 — Up to Fritz Mueller
  • DM-4738 — Up to Fritz Mueller
  • DM-4629 — Probably the same as DM-4621.
  • DM-2697 — Up to Fritz Mueller
Open Actions

AOB
  • LSST CCB, two DM points open:
    • LSE 400 on KT. 
    • Requirements flow down on Gregory


Pending Flagged RFCs

Key Summary
Refresh

Pending Proposed RFCs

Key Summary
Refresh

Oldest issues

Key Summary
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • 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)