2022-01-31 DM-SST Agenda and Meeting Notes

Short : ls.st/dmsst 

Zoom: https://noirlab-edu.zoom.us/j/97839121776?pwd=K1JPeUpSMXFvSXJSa2xORGkyVk5zdz09

Zoom Meeting ID: 978 3912 1776 
Zoom Password: 512314

If not joining audio from computer or mobile device, you may dial-in via phone:

    +1 253 215 8782 (US Toll) or +1 346 248 7799 (US Toll)

    Meeting ID: 978 3912 1776

    Password: 512314

    International numbers available: https://noirlab-edu.zoom.us/u/abyLUx8cga

No PST meeting last week due to AMCR

• No updates

Keith will provide a summary of the LoI received in response to the commissioning AO

• Had intended since long ago to involve the community in commissioning. International in-kind process created an impetus to set up a formal mechanism to start up a process for US-Chile.
• Once US-Chile teams and international teams are onboarded, they'll be effectively equivalent.
• Mostly proposing ~science-validation related work, only a few are "hardware" related or hands-on.
• Many of these groups already have strong connections to the project; this effectively formalizes those connections and ensures they have data access.
• Boundary conditions: no science publications until the data previews, and pubs go through the pub board.
• MLG: Are these groups being "onboarded" more like rubin staff or like DP0 delegates?
  • Expect many of these contributions to come in the form of PRs, so more developer-like access.
  • Might be different "levels" of onboarding.
  • Yusra: start them off working on the science platform at the USDF.
  • CTS: Please keep a spreadsheet of onboarding status and progress. Can be chaotic if people are getting onboarded by different people at different times to different degrees.
  • Yusra: ran into issues with contributors who could use the RSP but were later blocked by lack of batch access.
• Once it's May 1, where do these teams go? How do they start?
  • JB: worried about the load on existing meetings to add this many additional people. Gradually bring people in instead of all at once?
  • YA: was planning to increase the cadence of monthly cadence meetings, could accommodate some additional breadth from these efforts. EB: Agree w.r.t. the AP meeting. Concern about duplication of effort, takes work to make sure these groups aren't doing something that AP is already doing.
• GPDF: Are we "subcontracting" out the validation to the team, or is the point of contact still responsible?
  • Keith: formally not allowed to rely on these groups to demonstrate construction completeness.
  • So should they not "click the button" in Jira? Not ruled out, but can't formally delegate.
  • Workflow is that somebody caries out the test plan, caries out the test, creates a document, submits the doc for review. Ok for someone else to do these steps, but a project person still signs off and is responsible for completion.