2023-10-25 OpenCI Leadership Meeting Agenda & Summary

Agenda/Notes

1. Debrief on EC Meeting @Shawn Strande

   1. One of the goals that came from yesterday's charter is that these goals need to be communicated to all other groups and areas so everyone is in sync.

   2. It was brought up during yesterday's EC that the community building and the DEI group should have a conversation.

   3. Comms and personas should also talk to each other.

   4. Personas WG will not be a permanent committee at any point, the goal is to define personas and then will retire the group

   5. Community building has an operational perspective involved, same thing with Comms which is an ongoing work.

   6. Ag, Jay and Alana to have a conversation and will go through the charter and may be invited to the EC in the next 2 weeks

   7. If we think this process works, we want to ensure that it is documented.

   8. Personas is a good thing from a marketing perspective and how it has come up to target specific individuals, and the feedback received from stakeholders. This may or may not solve the actual issue.

   9. The idea is that if we define the personans, we maybe able to have targeted mechanisms for each of these groups

   10. Kim, what about having the idea that lavanya just mentioned whereby the prompt at some of these various meetings could be “any ideas for a good FAQ for the website based on conversations you’ve recently had with misc”…this would engage the meeting people and also possibly assist with applicable, missing FAQs on that web page
       
       

2. Discuss review agenda and status @Shawn Strande

3. Researcher Advisory Committee meeting Debrief @Shawn Strande
   
   

4. NeurIPS supplemental funding request @Shawn Strande

   1. Lavanya to reach out to the conference folks and see if a space is available for ACCESS
      
      

5. Review Action Items @Shawn Strande

   1. Lavanya to work with Shannon and understand how the action tracker and the to do lists on the wiki are linked

   2. It will cause confusion to have two separate places to track all the actions items for the ACO
      
      

6. Updates

   1. @Shawn Strande

   2. @Cindy Wong

   3. @Lavanya Podila

      1. Immediate issue working with the procurement teams at NCSA and campus to ensure vendor receives payment on time for the ACCESS Booth at SC.

   4. @Dina Meek and @Kimberly Mann Bruch

      1. Added “not getting info from Comms Team members” to Risk Register under the Execution of Comms Plan risk

      2. Shout out to Kim for chasing down and publishing two underserved community pieces recently: Howard University and Spelman College!
         
         

   5. @Jay Alameda

      1. Adding events to consider in the engagement tracker out as far as possible, noting important early deadline

• item

• item