See #inclusion and https://www.lsst.org/about/dei
Community link: https://community.lsst.org/c/eji/45
|report due this week.. https://docs.google.com/document/d/1DjQ62u1G4qkewLyoGckBVgcmYz1FJL8E1ukF-k91lKw/edit#heading=h.m2nv7zs59upm
At least on one Epic for each ops milestone (l3) - they are all linked up.
I think this shows Milestones with NO epic blocking it
|Review of Project Milestones
|Level 2 Milestones
Test Plans due in the next 45 days
Milestones due in the next 45 days
Risk items needing review
Overdue risks (obligation date passed)
Risk mitigations due at the end of this month
Overdue risk mitigations
|DMLT Travel & Availability this week
|Any Other Business
Discussion of what DP1 means now that ComCam is no longer going on the telescope. Pre-cursor data release should involve our pipelines generating the data and should consider what would happen if the outputs do not match the quality of existing data releases. Also need to understand that work is needed beyond what the default pipelines generate (such as HiPS) if a non-Rubin team is generating the data products. Some discussion of treating DP1 as a small set of LSSTCam data from early commissioning. Should not use Data Previews driving commissioning. LATISS is not going to be useful for a public DP. A DP of early LSSTCam data might distract from team focus on trying to improve image quality. The formal HSC PDR4 data would be acceptable for DP1 – the data have been verified, are using our pipeline, and there is scientific interest from the community.