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, June the 22nd..


Attendees

Regrets

  • None

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-704 - Getting issue details... STATUS Planned end: Jun/24/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Jun/03/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-704: Coling working on it with Gregory. Still needs some work before DMCCB can comment on it.
  • RFC-699:
    • be sure files written can be read back
    • on gen3 that should be better addressed
    • Migration scripts can be used to keep data repositories usable
    • John Swinbank : each release N should provide migration scripts to migrate data repositories created with release N-1.
    • The RFC requires more thoughts.
  • RFC-695: DPDD, still open
Board Recommended RFCs
  • RFC-651 - Getting issue details... STATUS
  • RFC-652 - Getting issue details... STATUS
  • RFC-700 - Getting issue details... STATUS
  • RFC-702 - Getting issue details... STATUS
  • Tim Jenness iterated with GPDF to adopt them after opening triggered tickets
Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-703 - Getting issue details... STATUS Planned end: Jun/30/2020
  • RFC-698 - Getting issue details... STATUS Planned end: Jun/24/2020
  • RFC-697 - Getting issue details... STATUS Planned end: June/04/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-703: discussion on-going. 
  • RFC-698: KT still have to look at it
  • the other 2 RFC-697 and RFC-638 not to discuss at DMCCB

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-414 - Getting issue details... STATUS
  • RFC-423 - Getting issue details... STATUS
  • RFC-701 - Getting issue details... STATUS
  • Gabriele Comorettoto ping assignee for RFC-414 and RFC-423 that a triggered ticket is required.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since last CCB

(to review, no action required)

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

RFCs implemented (or withdraw) since last CCB

(to review, no action required)



Releases

  • Planned
  • Changes to the release schedule
  • Release Note should be ready
  • Release happening today
  • Announced as soon as everything is ready

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity.

  1. DM-8829 - Getting issue details... STATUS
  2. DM-1510 - Getting issue details... STATUS
  3. DM-3115 - Getting issue details... STATUS
  4. DM-6122 - Getting issue details... STATUS
  5. DM-8591 - Getting issue details... STATUS
  6. DM-9145 - Getting issue details... STATUS
  7. DM-5305 - Getting issue details... STATUS
  8. DM-5655 - Getting issue details... STATUS
  9. DM-9214 - Getting issue details... STATUS
  10. DM-9215 - Getting issue details... STATUS

3876 unresolved issues (3861 on June the17th)

  • DM-1510: Up to Kian-Tat Lim. The fact we've lived with this issue since almost the start of construction at least implies it's not urgent.
  • DM-3115: Should be withdrawn? Tim requested a ruling from Kian-Tat Lim .
  • DM-6122: Are there still parts of the Dev Guide where this is an issue? I think the coding standards are clearly marked, and other material is covered by my PR (I know, I know, still in review...). Suggest closing as “Won't Fix”.
  • DM-8591: Effectively done. John Swinbank will take care of it after this meeting.
  • DM-9145: Examples are still broken. Given that they have been since 2014 and ~nobody has complained, I don't see this as urgent, but it is embarrassing. Suggest there's no point in making significant efforts to fix until we have a way of CIing examples, though.
  • DM-5305: Old; low priority; added comment to ask product owner if they still care.
  • DM-9214: Old, low priority, still valid. Added comment.
  • DM-9215: Old, low priority, still valid. Added comment.
Open Actions

AOB
License/copyright discussion for accepting external code.
Next DM-CCB July the 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
John SwinbankDMCCB#64 (2020 - 09 - 16)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)