(back to the list of all DMLT meeting minutes)

NOTE: For this meeting and future dates we are conducting the meeting on Blue Jeans (use web browser or below):

> Connecting directly from a room system?

> 1) Dial: 199.48.152.152 or bjn.vc
> 2) Enter Meeting ID: 293724745 -or- use the pairing code

 
> Just want to dial in? (all numbers)
> 1) Direct-dial with my iPhone or 
> +1 408 740 7256+1 408 740 7256 
> +1 888 240 2560+1 888 240 2560 (US Toll Free)
> +1 408 317 9253+1 408 317 9253 (Alternate Number)

> 2) Enter Meeting ID: 293724745

Date

Attendees

(sorry if I missed anyone)

 

Goals
  • Weekly coordination meeting to discuss and resolve management items, project communications, external contacts, etc.

Discussion items

 

Item
Who
Notes
LSST 2015 MeetingJeff Kantor
Registration is open. Tuesday and Wednesday are devoted mostly to DM-specific sessions. Plan to use available slots on Monday and Thursday afternoon and Friday morning as possible. Some people will have conflict with Cadence workshop and hackathon. All suggestions for topics should be sent to Jeff Kantor

DM Leadership Team Meeting

Jeff Kantor

Some Monday agenda changes in the works to focus on LDM-240 update.

LDM-240 updatesJeff Kantor

Latest integration by Gregory Dubois-Felsmann is in confluence, a few edits to make then post to docushare (leaf, not preferred version). Next step is for all of DMLT to review, assess dependencies, ask questions for expanded explanation, clarity of milestones.

Project Science Team DebriefMario Juric
Email sent after last PST meeting, nothing new since then.
Hardware procurementDonald PetravickDP working on procurement contract, how to avoid overhead on cloud services, how to handle property management (several classes, e.g. remaining at NCSA, shipping to Chile, etc.)
Software releasesFrossie Economou
FE planning for 10.1 release this week with astrometry fixes, lsst-distrib
MJ suggest adding pointers to Fabio Hernandez distribution work, contributions
KTL suggest doing so on “getting started” page (stack contributions acknowledgements would go in release notes)
Software Copyrights and licensesFrossie EconomouNeed license policy and agreement for all code contributors, whether in LSST contracted institution or outside.  RFC-45 addresses going forward only, and focuses on contracted institutions, not others and not legacy issues.  We do not need institutions on contract to assign copyright to us, we will do via licensing.  Still need to address legal right to re-license, legacy copyrights, and HSC contributions.

 Action items

REMINDER:  T/CAMs Turn in Monthly Progress Report inputs, variance reports in eCAM tool by 15th of following month

  • Donald PetravickKian-Tat Lim coordinate Alex Wither input on SCADA enclave to OCS workshop this week  
  • Kian-Tat Lim KTL look at copyright RFC-45 and give FE agreement to adopt  
  • Frossie Economou verify existing MREFC contracts have language that can legally be verified as allowing re-licensing (especially UW)