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.
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.
Walked through the LSP FDR charge, leading to submission of RFC;
Walked through User DB Workspace issues; Leanne asked to provide formal set of use cases; must be digested into design in time for the review;
Reviewed authorization architecture alternatives; rejected "pure capabilities-based" architecture as poorly suited to needs, at least with our resources; KT to write up memo with BvK on the pure-identity and mixed models discussed, with pure-identity, group-membership-based auth'z'n as an initial phase;
Reviewed new plan for internal and external use of IVOA standards (see DMTN-090); Gregory will RFC as a change to LSP Design, LDM-542;
Adopted CADC TAP service Java code base as the core of our planned TAP service (following Christine's nice demo); Fritz to document this and describe the development required to fully adapt/extend it to our design (edited)
Examined demo of Dask integrated with Jellybean; discussed Dask, Spark, and other "next-to-DB" issues
Looked at demos of closer Firefly-JupyterLab integration and of Firefly LSST detection footprint browsing