Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Ticketing Working Group Updates Winona Snapp-Childs James Griffioen (15 mins)

    1. Reviewed the charter and completed the work that's given in the charter

    2. Ops is responsible for adding new users and enabling new features

    3. Next steps - is still a need for minor touchpoints? We need to either re-charter the group or calling us something different? There will be a discussion during program wide meeting about WG's and standing committees

    4. As part of ops evaluation, there will be info share kind of sessions like what features need to be enabled? These will be monthly basis meetings and will continue this for a year, then maybe moved on a quarterly basis

    5. Team might be asked later to share lessons learned, how the WG process worked etc? what worked and didn’t work etc?

    6. Ticketing working group breaks resolved?

      1. Yes the issues have been resolved, we have been able to bring in new people

    7. what you envisioned that was beyond scope? Patterns in tickets, analytics etc? There's a possibility what opportunities could be available that others might benefit from?

      1. multiple requests for the XSEDE unarchived tickets, particularly there are tickets that are stuck

    8. Discussion on RP’s responsibility regarding handling the tickets

      1. Its possible the responsibility lies with the researchers and not ACCESS

      2. RP's do they have other options, except for Closing the tickets they can reassign the tickets, one specific question was when do they send to MATCH team?

      3. It is important to understand if higher level of service is what is expected? Or they are expecting an expertise that we cant can't provide? or they really tapped into the resources available?

      4. Jim would reach back to the RP forum and get more clarity. Ideally, we could get some recommendations then EC can vote/decide it

      5. This new WG or standing committee need to be able to help with some of these policy decisions

  2. Ombudspersons Winona Snapp-Childs (10 mins)

    1. Discussion regarding a recent breach of code of conduct and subsequent investigation

    2. Questions regarding responsibilities if misconduct happens virtually?

    3. Current reporting process includes contacting ombudspersons, and next step are evaluated on a case by case basis

    4. We may want some type of a playbook to answer questions like jurisdiction, what happens during a virtual event versus in-person events? and also provide additional trainings to the ombudspersons

    5. Action item for ACO to take this back and work through a flowchart with Lizanne.

  3. Approval of summaries from prior EC meetings John Towns (5 mins)

    1. 13 June 2023 EC Summary

  4. Program Milestone CheckJohn Towns (10 mins)

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

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

  5. ACCESS PIs meeting with ACCESS Resource PIs – collaboration and cohesion? Shelley Knuth (15 mins)

    1. Added to the EC backlog

  6.  Communications Year 2 Plan Dina Meek (10 mins)

    1. This topic could not be covered

    2. The plan will be presented during the program wide meeting

    3. https://docs.google.com/document/d/1cgA1RAHgPO9lF4NWz5OK3zTLyE0X52C5JNNablzkGoY/edit

  7. Prep for ACCESS Program Wide Meeting Shawn Strande (10 mins)

    1. June 2023 ACCESS Program Wide Meeting

    2. Ensure that your flights, hotel reservations and travel to/from Denver to Boulder are complete

    3. Amy and Bill Miller from OAC will be joining in-person on Day 1

  8. Informational Items (10 mins)

    1. RAMPS David Hart Stephen Deems

      1. RAMPS planning meeting will be held Wednesday and Thursday (June 28/29) next week @ NCAR Mesa Labs.

    2. MATCH Shelley Knuth

      1. We would like to get an up to date list of the software that each of the RPs are running. Can Operations assist with getting this list? Otherwise we would need to do a workaround.

    3. CONECT Tim Boerner

    4. MMS Tom Furlani

    5. OpenCI John Towns


...