2024-June Quarterly Meeting Notes and To Do Items - Resource Selector

 

Follow up

  • Jim - We might need to rename some things that have more focused goals. For example, ACCESS resource advisor might be an RP advisor. Different level of expertise and context, need for a wide variety of support solutions. Front end simple questions/guidance to guide them to the right system 

  • Has this been captured for sharing?

    • Megan Johnson - I do think mentioning the experts researchers have access to in the program as a resources is an important distinction. If someone were to go to AWS for compute time, that expertise isn't part of the basic package. Reminding people that they are getting into an ecosystem that gives them direct access to the people who are experts in HPC and research computing is a big selling point for ACCESS.  Shelley in chat: I think this is an important point.

  • This has not been done: Shawn - EC - how do we get to this point; before we embark on a major effort, we should share it and catch it before it becomes a major development effort. Let’s talk through it at the EC.

    • Is this decided? Dave - what collectively do we want to target for completion in year 3.

    • EC discussion - how far does it make sense to go in year 3? 12-18 months to rework leaves us a few months remaining. Should we do this or something different that produces something in a shorter amount of time that is “good enough.”

    • Dave - sounds like next steps go to EC. How we translate broad notions into actionable next steps. Decide on a North star and move us toward that.

  • Not created yet - JP - propose 2 general working groups building on what others have said

    • Working group on requirements of each persona for resource discovery and selection, user experience-focused group

    • Working group(s) on building the back-end infrastructure to enable those user interfaces

  • Improving and synchronizing communication between working groups and up to the EC

    • Dina in chat: I think the working groups/standing committees are where work happens but we need to be better at communicating even within our groups. And with each other and the EC

    • Megan Johnson - Maybe a working groups slack channel where they post their updates? that's open to everyone in ACCESS staff so they can see what is happening and offer support if they have some skills or ideas that could help 

    • JP Navarro - Maybe formal check-points where WGs synchronize with other WGs