You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
(back to the list of all DMLT meeting minutes)
In Location
Browser | Room System | Phone Dial-in |
---|
https://bluejeans.com/293724745/ | - Dial: 199.48.152.152 or bjn.vc
- 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 |
Time
10:15am PT
Attendees
Regrets
Discussion Items
Item | Who | Notes |
---|
Project updates | | |
DM-CCB | | |
Reviews | | - Confluence page with key dates & agenda: JDR2020/JSR2020
- JSR: August 31 – 3 September (4 weeks away)
- Updates to be made post-JDR (have we made them yet?):
- Risk slides — adding architecture risk, and new requirements on security exposure needs to be increased (could bump this exposure further, due to Huawei regulations; Jeff Kantor will review).
- Milestone Gantt chart needs to be added.
- Document pack.
- Some documents have already been RFCed and will be in CCB this week.
- Otherwise, please finish your docs that were in draft for the JDR and make sure they don't say “draft” on them for the JSR.
|
DMLT vF2F | | - 2020-09-15/17; six weeks away.
- As usual, there's a suggestion box on the wiki page: please add topics.
|
Ops Rehearsal #2 | | - Happened last week... how did it go?
|
Operations Readiness Criteria | | - Chuck Claver has approached various members of the DM team and requested they contribute to the Operations Readiness Criteria on Confluence in advance of the JSR.
- Members of the Science Pipelines group discussed this and agreed that:
- This may need to be a cross-DM effort (e.g. readiness for Data Release Production includes readiness of hardware systems, execution middleware, QA harnesses, etc, not just that of Pipelines);
- The definition of “operations readiness” seems a little unclear (can it introduce new requirements? can it relax existing requirements? what about things like documentation, which are only implicitly required?)
- Proposal for a focused DMLT session, with Chuck as an invited guest, to figure out these details.
|
L2 Milestones | | Test Plans due in the next 45 days
Key
|
Summary
|
T
|
Created
|
Updated
|
Due
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
Milestones due in the next 45 days
Key
|
Summary
|
T
|
Created
|
Updated
|
Due
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
|
Risks or Schedule | | Overdue risks (obligation date passed)
T
|
Key
|
Summary
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
Created
|
Updated
|
Due
|
Risk mitigations due at the end of this month
Key
|
Summary
|
T
|
Created
|
Updated
|
Due
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
Overdue risk mitigations
T
|
Key
|
Summary
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
Created
|
Updated
|
Due
|
|
Any other business | Wil O'Mullane |
|
Availability | | |
Overdue
Key
|
Summary
|
Reporter
|
Assignee
|
Created
|
planned end
|
Due this week
Key
|
Summary
|
Reporter
|
Assignee
|
Created
|
planned end
|
Action Items
Confluence Quick Tasks
DMLT-relevant Jira Tickets
Key
|
Summary
|
Reporter
|
Assignee
|
Created
|
Due
|