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, February the 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: Feb/26/2021

  • RFC-755 - Getting issue details... STATUS
  • Board recommending RFC-755
Board Recommended RFCs
  • RFC-699 - Getting issue details... STATUS

Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-754 - Getting issue details... STATUS Planned end: Jan/28/2021
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-754, comments from Phil integrated. No further comments received, we are ready to issue this. 

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-737 - Getting issue details... STATUS
  • RFC-709 - Getting issue details... STATUS
    • Waiting for LCR-2543

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-741 - Getting issue details... STATUS
  • RFC-753 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 22.0.0
    • May 2021
    • Activity to start in March
  • Patch releases
    • None requested at the moment
  • May want to synchronize with DP0.2 feature freeze milestone
  • But may also be useful to have a 22.0.0 as a "practice" followed by an official 22.1.0 for DP0.2
  • DP0.2 needs to be an official release, not just a weekly
  • Playbook is in SQR-016; skills required are Community posting, git manipulation, running ci.lsst.codes jobs, chasing after people for documents
  • Yusra AlSayyad will identify people from Science Pipelines who could do this  

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-2034 - Getting issue details... STATUS
  2. DM-55 - Getting issue details... STATUS
  3. DM-6827 - Getting issue details... STATUS
  4. DM-2083 - Getting issue details... STATUS
  5. DM-2505 - Getting issue details... STATUS
  6. DM-2676 - Getting issue details... STATUS
  7. DM-297 - Getting issue details... STATUS
  8. DM-2084 - Getting issue details... STATUS
  9. DM-3361 - Getting issue details... STATUS
  10. DM-2108 - Getting issue details... STATUS

4023 unresolved issues

DM-2034: K-T commented; out for comment from Colin

DM-2108, DM-2084: still relevant; upcoming

Open Actions

AOB


RFC-552 - Getting issue details... STATUS : still valuable to have a person in each README, though it may just be "head of Science Pipelines".  Assigned to KTL

  • Probably useful to go through the oldest adopted but not implemented RFC each week to see what should be done about it
Next DM-CCB February 3rd


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)