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 29th.


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-593 - Getting issue details... STATUS Planned end: Jun/14/2019

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



Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-600 - Getting issue details... STATUS Planned end: Jun/29/2019

RFC-599 - Getting issue details... STATUS Planned end: May/30/2019

RFC-598 - Getting issue details... STATUS Planned end: Jun/01/2019

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


  • RFC-600 to be flagged:
  • RFC-599: DMCCB agrees on the RFC but no action from to be taken
  • RFC-598: should have been flagged
    • if no comments, the RFC is approved
  • RFC-585: no rush


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-596 - Getting issue details... STATUS



RFCs implemented since last CCB

(to review, no action required)

RFC-591 - Getting issue details... STATUS

RFC-596 - Getting issue details... STATUS


Changes to the planned releases
  • 18.0 Release status
    • Community post out
    • Planned first Release Candidate based on w_2019_22 (June the first)
  • DM-19147 - Getting issue details... STATUS

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-4803 - Getting issue details... STATUS
  2. DM-3036 - Getting issue details... STATUS
  3. DM-887 - Getting issue details... STATUS
  4. DM-1243 - Getting issue details... STATUS
  5. DM-1757 - Getting issue details... STATUS
  6. DM-4308 - Getting issue details... STATUS
  7. DM-4439 - Getting issue details... STATUS
  8. DM-1605 - Getting issue details... STATUS
  9. DM-1606 - Getting issue details... STATUS
  10. DM-1639 - Getting issue details... STATUS

4061 unresolved issues (4053 on May the 21st)

Pre-meeting notes from DMCCB#17 (2019 - 05 - 29):

  • With the exception of DM-4803, these are all Qserv issues. We should ask DMCCB#17 (2019 - 05 - 29) to address them.
  • DM-4803 is broadly part of the same grouping as the persistence format questions we addressed last week (DM-4621, DM-4629). It's less unambiguously correct than those, though: we can clearly say that FITS files ought to be documented and/or self-documenting, but I struggle to get excited about whether they contain radians or degrees.
Open-Actions

AOB


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)