Location
| Browser | Room System | Phone Dial-in |
|---|---|---|
| https://bluejeans.com/761546516/ |
| Dial-in numbers:
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
- #dm-ccb slack channel
Discussion Items
| Item | Description | CCB Notes |
|---|---|---|
Flagged RFCs (To be approved by the DMCCB) | 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 |
| Still waiting on Eli |
| Adopted but not implemented LDM RFCs (only document RFCs) | ||
Proposed RFCs (to review, do not require DMCCB approval) | ||
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 withdraw) since the last DMCCB (to review, no action required) | ||
Releases
|
| 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:
|
3996 unresolved issues | DM-3257: Still relevant; upcoming. |
| Open Actions | ||
| AOB | ||
| Next DM-CCB | March 31st |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.