Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Attendees:

  • RAMPS: Stephen Deems (v), Dave Hart

  • MATCH: Shelley Knuth (v), Alana Romanella

  • CONECT: Tim Boerner (v), Leslie Froeschl

  • MMS: Tom Furlani (v), Joe White

  • OpenCI: John Towns (v), Shawn Strande, Lavanya Podila, Lisa Kaczmarczyk, Shannon Bradley

  • NSF: Tom Gulbransen, Sharon Geva

  • Guest Speaker: RP Forum Chair

(v) indicates a voting member

Decisions made during the meeting:

  • Enabling Multi Factor Authentication for Atlassian Confluence and Jira - Approved

Use Decision Macro

Agenda/Notes

  1. Approval of summaries from prior EC meeting John Towns (5 mins)

  2. 16th Jan 2024 EC Meeting Summary

    1. We may need to consider more than an hour for each meeting OR moving meetings to weekly again

  3. Program Milestone Check John Towns (5 mins)

    1. Action item for the awardees to update their program milestones

      1. no additional comments or updates

    2. Reminder: Do not edit "Dashboard" tab, please edit "ACCESS program milestones" tab as needed

    3. Review To Do list: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1081359/Executive+Council+Meetings#To-Do-Tasks-for-ACO-Leadership-from-EC-Meetings

  4. ACCESS Quarterly Meeting - September 2023

    1. Confirm Date - 9/16 or 9/23

    2. Discuss location of event

      1. Stephen D - host the meeting at the PSC offices

        1. We have one large meeting room on the main floor and several breakout room options. Since these are our regularly-scheduled meeting rooms there should be no cost to reserve these spaces, pending there's no other event scheduled. 

        2. Event can be wholly hosted at PSC - no other location needed for additional space

  5. RP Forum Bylaws Vote

    1. Let’s clarify what is referred to as “ACCESS Requirements Mgt Process”

  6. Personas Working Group - Shelley Knuth

    1. Recommendations Document submitted for feedback: https://docs.google.com/document/d/1sYBUyFHdx-E1--lRSQXgs8ak5Z8UTGhtPrpb8y61sVw/edit#heading=h.izmimhj72m1q

    2. We are seeking feedback on this doc, and would ultimately like to bring to a vote that the EC is in agreement that these personas are what ACCESS will be focused on, which would drive any work we are doing (ie, communications, website development, etc). 

    3. For awareness, once the EC has provided feedback and approved the recommendations, the personas group will email the final doc to the other working group/standing committee chairs and will disband.

  7. SGX3 web usability engagement (Shawn Strande)

    1. Continuing discussion from December 19, 2023 meeting: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/379092993/2023-12-19+ACCESS+EC+Meeting+Agenda+Summary

  8. ACCESS Infrastructure Integration Standing Committee proposed charter- Leslie Froeschl

    1. https://docs.google.com/document/d/1lG-pOih4FK0iE2c0NNBIeWNTybBEfBlKxc_EsLiJIbs/

  9. NAIRR Pilot Update David Hart

    1. NAIRR Pilot will launch on January 24

      1. With 6 initial resources:

        1. Summit - DOE Oak Ridge National Laboratory

        2. Delta GPU - National Center for Supercomputing Applications

        3. Frontera - Texas Advanced Computing Center

        4. Lonestar6 - Texas Advanced Computing Center

        5. ALCF AI Testbed - DOE Argonne National Laboratory

        6. Neocortex - Pittsburgh Supercomputing Center

      2. Allocations WG has been formed

        • Dave/John have been leading

        • Dave is the liaison between the RPs

      3. Proposals will be accepted until March 1, 2024.

        1. More resources are expected to be looped-in after and opportunities will eventually re-open.

      4. It’s expected that an RFI will be included in parallel to the allocations submission window.

      5. The theme for projects will be: Safe, Secure and Trustworthy AI

        • Testing, evaluating, verifying, and validating AI systems.

        • Improving accuracy, validity, and reliability of model performance, while controlling bias.

        • Increasing the interpretability and privacy of learned models.

        • Reducing the vulnerability of models to families of adversarial attacks.

        • Advancing capabilities for assuring that model functionality aligns with societal values and obeys safety guarantees ​

      6. The process will be quite similar to the COVID19 consortium.

  10. Informational Items (10 mins)

    1. Allocations Stephen Deems

      1. A series of questions (smile)

        1. Presenting ACCESS Annual Metrics

          1. Would it be best to present calendar year? program year? …fiscal year?

          2. Calendar year would be the preference from Allocations.

          3. Would like to sync this with other teams before we go into annual report/review season.

        2. Question regarding ACCESS PEARC24 Plans

          1. BOF? Workshop? Are we thinking of anything here?

        3. Allocations Notifications

          1. Sharing a Google doc with notifications that go out to folks who request allocations.

          2. Looking for recommendations on how we can improve these, or better highlight specific areas of interest for each ACCESS team.

          3. Open question: Should we discuss a broader notifications strategy?

            1. e.g. after someone creates an account?

    2. MATCH Shelley Knuth

    3. CONECT Tim Boerner

    4. MMS Tom Furlani

    5. OpenCI John Towns

      1. Submitted IRB for surveys.

      2. EAB Chair Report Received

      3. External evaluator presented feedback from Dec focus group discussion

Misc Topics:

  1. Tapia Conference—Sep. 18-20, 2024—San Diego

    1. Should ACCESS be a supporter? staff a table?

  2. MFA for Atlassian Confluence and Jira Leslie Froeschl - approved

    1. Email sent to EC - 1/25/2024

    2. ACCESS Cybersecurity has asked if it would be possible to enable MFA/Two Factor Authentication on Confluence and JIRA.

      We have not had a problem with unauthorized access up to this point, but they would like to be prepared in advance of any attempts.

      Users will not experience any changes for public access sites.

      For sites that currently require logging in – people would just have the additional step to complete authentication.

    3. Is this something you would agree to or would you like this added as a discussion item to the next EC agenda?

    4. Approved via email:

      1. CONECT - Leslie Froeschl - Approved

      2. OpenCI - John Towns - Approved

      3. MATCH - Shelley Knuth - Approved

      4. Allocations - Stephen Deems - Approved

      5. MMS - Tom Furlani - Approved

Parking Lot

  • Risk Management progress = change in likelihood due to mitigation efforts?

  • Horizontal Leadership progress = compromises?

Next EC Meeting: 13th February 2024


Action Tracker:

  •  

Use Action Item Macro to track assigned To Do Items - check the box when it is complete

Format:


Reference:

Risk Register: https://access-ci.atlassian.net/jira/core/projects/RR/board

Project Change Request: https://access-ci.atlassian.net/jira/core/projects/PCR/board

  • No labels