Location
| Browser | Room System | Phone Dial-in |
|---|
| https://bluejeans.com/761546516/ | - Dial: 199.48.152.152 or bjn.vc
- 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, August the 26th.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
Discussion Items
| Item | Description | CCB Notes |
|---|
Flagged RFCs (To be approved by the DMCCB) | -
RFC-709
-
Getting issue details...
STATUS
Planned end Jul/24/2020
-
RFC-699
-
Getting issue details...
STATUS
Planned end: Jun/03/2020
-
RFC-695
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
| - RFC-709
- GPDF working on update DMS
- RFC-699 no progress still
- RFC-695
- due date end of September
|
| Board Recommended RFCs | -
RFC-710
-
Getting issue details...
STATUS
-
RFC-708
-
Getting issue details...
STATUS
-
RFC-711
-
Getting issue details...
STATUS
| - 708 adopted
- RFC-710:
- Leanne confirmed LCR has already been submitted
- RFC-711: KT to move forward to implement it
|
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-723
-
Getting issue details...
STATUS
Planned end: Aug/26/2020
-
RFC-722
-
Getting issue details...
STATUS
Planned end: Aug/26/2020
-
RFC-703
-
Getting issue details...
STATUS
Planned end: Aug/31/2020
-
RFC-697
-
Getting issue details...
STATUS
Planned end: June/11/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
| - RFC-723: no action from the CCB
- RFC-722: flagged
- this seems to be worrisome
- John pointed out that this may be a workflow problem
- This seems to be science pipelines code and not external, so it should not be added to the environment
- The other RFC are not to be discussed by the CCB
|
Adopted RFCs without Triggering issues (to create implementing DM issues) |
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-484
-
Getting issue details...
STATUS
-
RFC-721
-
Getting issue details...
STATUS
|
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-713
-
Getting issue details...
STATUS
-
RFC-721
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-713
-
Getting issue details...
STATUS
-
RFC-705
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 21.0.0
- Tentative schedule: November 2020
|
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity. -
DM-9582
-
Getting issue details...
STATUS
-
DM-9593
-
Getting issue details...
STATUS
-
DM-9592
-
Getting issue details...
STATUS
-
DM-9601
-
Getting issue details...
STATUS
-
DM-1459
-
Getting issue details...
STATUS
-
DM-9545
-
Getting issue details...
STATUS
-
DM-6912
-
Getting issue details...
STATUS
-
DM-9093
-
Getting issue details...
STATUS
-
DM-9733
-
Getting issue details...
STATUS
-
DM-9017
-
Getting issue details...
STATUS
3925 unresolved issues (3894 on August the 19th) | - DM-9593: Low priority, added comment.
- DM-9592: Low priority, added comment.
- DM-9601: Tim has commented. Is Architecture now the responsible team? (I think so, since this falls under middleware, but am not sure; pex_config isn't listed in DMTN-104).
- DM-6912: Tim & John both commented.
- DM-9093: Added comment.
|
| Open Actions |
| |
| AOB | | |
| Next DM-CCB | September 2nd. | Next week JSR, next DMCCB September the 9th |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.