Skip to end of metadata
Go to start of metadata

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

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. 

ItemWho

Notes

Joint Status Review

Report on last week's Joint Status Review.



November DMLT F2FJohn Swinbank

Select dates: see this Doodle poll. Best run of three dates as of 2017-09-11 is Monday 13 – Wednesday 15 November, missing Michael Wood-Vasey, Margaret Gelman (will Donald Petravick be available?), Mario Juric, Jeff Kantor.

Select venue: suggestions? Volunteers?

  • Venue will likely depend upon dates; Tucson last week in November, perhaps IPAC or SLAC earlier.
Spring 2018 DM All HandsWil O'Mullane
  • Wil O'Mullane create & distribute Doodle poll for DM All Hands meeting in Spring 2018.  
Access to Stripe 82 data/PDACGregory Dubois-Felsmann

Request received by Gregory Dubois-Felsmann from an (external) scientist. How do we handle this? See this mail to DMLT of 2017-09-01.

  • This person probably stumbled onto a Winter 2013 data release, which has its own data release policy.
  • The older Winter 2013 server may still have all the old data loaded.
DM websiteJohn Swinbank

The DM website at http://dm.lsst.org/ is infrequently updated and may be outdated (in particular, re job openings — as far as I'm aware, none of the current openings within DM have been added to it, while the one job listed at time of writing was obsolete — this will be fixed by the date of this DMLT meeting).

  • Do we actually want this website?
  • Who is responsible for maintaining it?

The answer: this should grow into our community-focused website. As such, the DM-SST (Mario Juric) is responsible for maintaining it (and coordinating its contents with Jonathan Sick if necessary).

Overdue RFCs

RFCs with "Planned end" past "now".

Key Summary T Status
Loading...
Refresh

  • RFC-365 - Getting issue details... STATUS discussed. Ticket is ready for Wil O'Mullane to make a decision.
  • Gregory Dubois-Felsmann Write a plan for implementation of RFC-243 - Getting issue details... STATUS as a DMTN for discussion at the November DMLT.  
  • Tim Jenness to add triggering tickets to RFC-325 - Getting issue details... STATUS  
Change Control Board report

Change requests of interest to DM

  • LCR-1064 (LSE-61 priorities) waiting for final approval.
  • LCR-1013 (LSE-319 LSP vision) waiting for final approval.
  • LCR-1024 (DPDD/OSS tie in) approved but not yet in OSS.
  • LCR-908 (older data releases): Finalizing OSS wording of requirements.
Data Compression WGMario Juric

Per DM Leadership Team Meeting 2017-08-28, the charge and membership for this WG are at DM-11819 - Getting issue details... STATUS . We request the DMLT to agree to the membership, and Wil O'Mullane to create it.

Python 2 deprecation timeline

For v14 release notes we should make a clear statement as to how long Python 2 will be supported.

Agreed within the DMLT that:

  • v15.0 will be the last release to support Python 2; major fixes will be back-ported
  • v14.0 will announce this policy
  • Tim Jenness file an IT-RFC to reflect the DM Python 3 transition plan.  
Butler WGTim Jenness

Status update.

Use cases are solid; started writing requirements.

Outstanding DMLT actionsWil O'Mullane

See links and action item report below.

DMLT Travel & Availability this week
Matters arising






DescriptionDue dateAssigneeTask appears on
  • Fritz Mueller — Draft an technote describing operational procedures for database ingest.  
03 Aug 2020Fritz MuellerDM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
  • Colin Slater — Augment LDM-153 to provide a description of the semantics of NULL, NaN, inf, and other database vocabulary.  
06 Jul 2020Colin SlaterDM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
06 Jul 2020Wil O'MullaneDM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
  • Fritz Mueller — engage with the LDF and, as necessary, AP team to best understand the data structures required for the APDB.  
06 Jul 2020Fritz MuellerDM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
  • Gregory Dubois-Felsmann  — update the Science Platform design documentation to reflect that data access services should be tested with PyVO.  
01 Jul 2020Gregory Dubois-FelsmannDM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
29 Jun 2020John SwinbankDMLT Meeting - 2020-06-22
  • Wil O'Mullane — make sure a L2 milestone for the Science Platform exists in P6.  
15 Jun 2020Wil O'MullaneDMLT Meeting - 2020-06-08
  • DMTN-148 is almost there suggest 2 weeks review by DMLT.  
15 Jun 2020 DM Leadership Team Virtual Face-to-Face Meeting, 2020-05-12/14
  • 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