Skip to end of metadata
Go to start of metadata


BrowserRoom SystemPhone Dial-in

  1. Dial: or
  2. Enter Meeting ID: 293724745 -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: 293724745

(back to the list of all DMLT meeting minutes)


10:00am PT



DMLT Meeting Goals

  • Weekly meeting to keep the DM leadership team coordinated, informed, and in agreement on the vision, priorities, and challenges facing DM construction, including surfacing and resolving issues and ambiguities needing our attention. The goal of this meeting is to provide information and decisions that help each one of us better direct our own (or our team's) activities.

Discussion Items

Guidelines: Propose items in line with the meeting rationale (see above); include as much information in the agenda notes; summarize, don't go into details while on the call; maximize time available for discussion. 

Begin Meeting at XX:XX PT




Prep for September status review: slide deadline 2017-08-11. Plenary Draft , Breakout (VERY DRAFT)

Wil O'Mullane and John Swinbank will physically attend - all welcome to listen in and may be needed for breakout session (Thursday 9am-12pt)

DM-11466 - Getting issue details... STATUS

ReleasesReminder to review Release Feature list in LDM-564
Overdue RFCs

RFCs with "Planned end" past "now".

Key Summary T Status

RFCs discussed: No RFCs past due at time of meeting.

Jim Bosch expecting to flag RFC-365 - Getting issue details... STATUS today.

Change Control Board report

Change requests of interest to DM

New change requests:

  • LCR-921 (DM to Provide Service for Publishing Predicted Visit Sequence) voted on. Pending approval.
  • LCR-1024 (Tie LSE-163 into OSS) being voted upon.

Other issues for CCB:

  • Still need to finalize LSE-61 priorities so we can submit to CCB ( DM-10647 - Getting issue details... STATUS ).
Butler Working GroupCharge accepted as LDM-563. First meeting held.
Community interactions

SAC want to know policy on interactions with community. Relates I suppose to DM-7675 - Getting issue details... STATUS   and DM-6825 - Getting issue details... STATUS . Is it like:

Slack - informal and ephemeral discussions quick questions

Approach designated leads in the area (we all then need to be ready to say "I can not answer that we would need to talk to X" (where X=product owner or manager)

Raise issue on GitHub for specific algo problems or suggestion (small effort based WP to monitor that - respond/fox or mirror issue in JIRA if longer term action required)  - GitHub issues would then have to be monitored by DMCCB

Outstanding DMLT actions

See links and action item report below.  Creating issues for you ... like DM-11509 - Getting issue details... STATUS and

DM-11510 - Getting issue details... STATUS

RFC-325 - Getting issue details... STATUS

  • Mario Juric proposed a meeting to be held at AHM to discuss this issue and RFC-336 - Getting issue details... STATUS with Beth Willman and others.
  • This will happen on  Wednesday  @ 12:30
DMLT Travel & Availability This Week

Margaret Gelman driving to Tucson

Matters arising

End Meeting at XX:XX PT

Past action items

Open DMLT actions:

DescriptionDue dateAssigneeTask appears on
  • Michelle Butler  & Gregory Dubois-Felsmann  — identify existing requirements, or suggest new requirements, for a user-facing ”bulk-download“ service (but not under that name).  
05 Jun 2020Michelle ButlerDM Leadership Team Virtual Face-to-Face Meeting, 2020-02-25 to 27
  • Kian-Tat Lim  & Michelle Butler  — propose a design and schedule for deploying a rapid processing system at the LDF.  
29 May 2020Kian-Tat LimDMLT Meeting - 2020-03-02