Skip to end of metadata
Go to start of metadata

Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday, August 4th 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-771 - Getting issue details... STATUS Planned end: Apr/21/2021

  • RFC-783 - Getting issue details... STATUS Planned end: July/31/2021

  • RFC-795 - Getting issue details... STATUS Planned end: Aug/24/2021
  • RFC-796 - Getting issue details... STATUS
  • RFC-798 - Getting issue details... STATUS
  • RFC-799 - Getting issue details... STATUS
  • RFC-800 - Getting issue details... STATUS




783 on hold


795 - partial plan, C++ out of utils  to some C++ utils package, move utils out of butler and pipe base out of butler, naming block . (ButlerUri)

796 - Yusra/Jim ? Board recommend.

798 - KT says ok only for AP .. not that big

799 and 800 are related enough .. could be combined. Has been condafied .. needed for auxtel so we have to accept to integrate on summit. There are pending cleanups - flake8 ok, github action missing, and docs not done .. board recommends - require Colin as reviewer.


Board Recommended RFCs
  • RFC-785 - Getting issue details... STATUS



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

RFC-638: Yusra AlSayyad added a note recommending withdrawing


797 - logging missing and no packages for notebooks - could be it specific to us since we run tasks and care about the output..

 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)



RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-793 - Getting issue details... STATUS
  • RFC-776 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 23.0.0:
    • Will be linked to version that we are confident will be used for the final DP0.2 run.
  • Patch releases
    • None


Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-11923 - Getting issue details... STATUS
  2. DM-12858 - Getting issue details... STATUS
  3. DM-4045 - Getting issue details... STATUS
  4. DM-8369 - Getting issue details... STATUS
  5. DM-8370 - Getting issue details... STATUS
  6. DM-12871 - Getting issue details... STATUS
  7. DM-7059 - Getting issue details... STATUS
  8. DM-12892 - Getting issue details... STATUS
  9. DM-12888 - Getting issue details... STATUS
  10. DM-12919 - Getting issue details... STATUS

Unresolved issues: 4119

DM-12803: (Qserv) Still relevant; low priority

Open Actions

AOB



Next DM-CCB September 1st


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