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, March 3rd 2021.


Attendees


Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-695 - Getting issue details... STATUS Planned end: Mar/31/2021

  • RFC-768 - Getting issue details... STATUS

RFC-695: Science Pipelines should comment to reflect that they're familiar with the proposal from SST.

RFC-768: KT: Do we want it? Is the name OK? are there any dependencies? check, check, and check

YA: Maybe see if it need a code review before adding to lsst_distrib


Board Recommended RFCs
  • RFC-699 - Getting issue details... STATUS
Still waiting on Eli
Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

  • RFC-760 - Getting issue details... STATUS Planned end: Mar/30/2021

  • RFC-764 - Getting issue details... STATUS Planned end: Mar/23/2021
  • RFC-765 - Getting issue details... STATUS  Planned end: Apr/01/2021


 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-762 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)



Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 22.0.0
    • May 2021 / linked to DP0.2 version
    • Activity to start in March
  • Patch releases
    • None requested at the moment

Someone or Yusra will do this. 

"linked to DP0.2 version" doesn't mean that we will rather than we will discuss the connection. 

The weekly that we'll use for DP0.2 will come later than 22.0. We should do a release for that weekly so we keep it. 

JFB: We can tag 23.0, and then during processing make a branch of that as it evolves 23.1, 23.2, etc... rather than the newest weekly.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-2410 - Getting issue details... STATUS
  2. DM-3135 - Getting issue details... STATUS
  3. DM-2081 - Getting issue details... STATUS
  4. DM-2130 - Getting issue details... STATUS
  5. DM-4812 - Getting issue details... STATUS
  6. DM-3527 - Getting issue details... STATUS
  7. DM-624 - Getting issue details... STATUS
  8. DM-368 - Getting issue details... STATUS
  9. DM-2317 - Getting issue details... STATUS
  10. DM-1199 - Getting issue details... STATUS

3996 unresolved issues

DM-3257: Still relevant; upcoming.

Open Actions

AOB



Next DM-CCB March 31st


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
  • Tim Jenness investigate astropy warnings filter for tests.
05 Oct 2022Tim JennessDMCCB#142 (2022 - 09 - 28)
21 Jun 2023Kian-Tat LimDMCCB#165 (2023 - 06 - 07)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)