...
| Item | Who | Notes |
|---|
| Notes |
| last time |
| Project Updates | | - AHM this week
- AAS town hall - Monday rehearsal in AURA room. Seattle convention center.
- Schedule updated - OCT is in now but work to be done
- block schedule now also in DMTN-232.
- 7am Pacific Dec 15 next schedule meeting.
- SF2 still not there so accounts may look empty (less so for DM i think)
- there will be a standard naratives from Kevin if needed
- this will be for some months ..
- Managers should work with teams to recognize the next two weeks (Dec 21) are going to be quiet. Cancel meetings as necessary and reasonable. (DM Choose dec 26, SLAC Dec 21)
- Victor asks for advance notice of any visitors - need saftey briefing, driving training if on summit over night etc. takes planning.
- accommodation short
- going back to 1 bus .. 38 seats will be mostly full
- need the base (remote) control room.
|
| DEI | | See #inclusion and https://www.lsst.org/about/dei Community link: https://community.lsst.org/c/eji/45 |
|
| Review of Project Milestones | | https://www.lsst.org/about/project-status |
| Level 2 Milestones | | See also LSST Verification & Validation Documentation and LDM-692 (VCD). Test Plans due in the next 45 days | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | labels = TESTPLAN and resolution = Unresolved and due <= 45d order by id asc |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
Milestones due in the next 45 days | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = DM and labels = L2Milestone and team not in ("Telescope and Site") and resolution = Unresolved and due <= 45d order by id asc |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
|
| Risk Review | |
Risk items needing review | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,status,days since review |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Days Since Review" >= 60 ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
Overdue risks (obligation date passed) | Jira |
|---|
| server | JIRA |
|---|
| jqlQuery | project = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Obligation Date" < now() ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
Risk mitigations due at the end of this month | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Obligation Date" < now() ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
Overdue risk mitigations | Jira |
|---|
| server | JIRA |
|---|
| jqlQuery | project = rm AND issuetype = rm-handling AND status = Planned AND component = "Data Management" AND "Anticipated completion date" <= endOfMonth() AND "Anticipated completion date" <= now() ORDER BY status DESC, component ASC, assignee ASC, reporter ASC |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
|
|
| DMLT Travel & Availability this week | |
|
| Any Other Business | | YA: Draft JTM block schedule NO DMLT Jan 26 and Jan 3 – we will meet Jan 19. |
| TCAM Stamdup | | lets not have multiple streams of summit EFD data. How to deploy new service at USDF - Yee has a branch which is long lived. Keep the fork and deploy off it - or turn it into a branch (He has done a PR to phalanx production) - we should drop the fork lets have a branch in phalanx perhaps labelled USDF . Ideally merge but if it needed more than 4 weeks make it a branch. FERAMP - google is approved but they want RSP comliant compliant and we do not know what that means. KT says FEDRAMP is a qualification of the vendor.. not the application. Richard will look into it.There is approval to operate from DOE site office - FEDRAMP justification made it fast. Approval to operate complete and signed and good to go. Google contract is in progress. |
| Action review | |
|
DMLT Action Items (Confluence quick tasks)
...