Location

BrowserRoom SystemPhone Dial-in

https://bluejeans.com/293724745/

  1. Dial: 199.48.152.152 or bjn.vc
  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)

Time

10:00am PT

Attendees

Please add yourself to the attendee list as you connect to the meeting.

Regrets:

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. 

TimeItemWhoNotes
5minActions from past meetingsMario Juric
  • Review status of outstanding actions
  • Do we have convergence on ADASS representation?
  • Do we have a preference for the policy on community use of the Prototype DAC?
10minNews & progress over the past weekJacek Becla, Mario Juric
  • Director's review: Jacek & MJ will work on the agenda this week

  • Monthly status report overdue (need input from Arch, UW, NCSA)

  • "cloud feasibility" plan: do not show disinterest in the next month, start discussions with Amazon in ~1 month

  • W16 milestones: 10 need to be dealt with

  • X16 milestones: 4 need to be dealt with

  • X16 epics: many epics need to be dealt with: Arch 9, Infra 8, ProcM 7, DAX 4, DRP 4, SQuaRE 1
  • F16 milestones: 73 feels a bit high, I created DM-6536
  • F16 epics: need to review descriptions
  • international trip planning, see Conferences and Workshops with DM Involvement. ADASS - need input from IPAC. DESC looks ok (5 going)
  • we are doing poorly with dealing with actions from past meetings. Proposal: turn unresolved actions into JIRA stories ~2 weeks after each meeting
  • need to decide on Calibration Review timing
10minWG UpdatesWG Chairs
5minSystems Engineering UpdatesGregory Dubois-Felsmann
  • A new LCR has been created, asking to change the default from two 15-second snaps/visit to a single 30-second snap
5minDefining the Task Framework Work Package (informational item)Kian-Tat Lim
5minLSST 2016 preparations

Mario Juric

5minCommunity management on community.lsst.orgZeljko IvezicZeljko Ivezic asks: How do we handle requests/postings such as
https://community.lsst.org/t/advanced-methods-for-background-subtraction/817
That is, who is responsible for providing a meaningful response?
 DMLT Travel & Availability This Week  

 

Postponed for subsequent DMLT / proposed for future DMLT:

TimeItemWhoNotes
5minUpdates re recent Nebula activity & processesDonald Petravick
  • Lessons learned from the Nebula security incident
5minDM source code license policyMario Juric
  • Proposal is to move to the BSD license, in line Jim Bosch's proposal in DM-5031 - Getting issue details... STATUS and the series of comments that followed.
    • Postponed: no time to discuss
 Overdue RFCsKian-Tat Lim
 Status of unhandled work/technical debt. 
  • Following discussion at the May DMLT, Jim Bosch filed tickets describing some technical debt issues.
  • There may be other work in danger of falling through cracks: Jim is probably not infallible.
  • Identifying and assigning this work is necessary for producing resource loaded plans.
 --- Add more proposed topics here. 

 

Action items