Initial Planning Meeting
ACCESS Community Building and Engagement Team
13 September 2022
Agenda
Introductions
Meeting frequency and time - Bi-weekly
Notes proposal: detailed notes in google docs (shared with just us), summary notes in ACCESS confluence (open to world)
Something to think about: will we need to create a charter to govern our group? (see EC charter at Charter of the ACCESS Executive Council
Who are our communities?
Allocations
Support
Operations
Metrics
Service Providers(?)
What kind of relationship do we seek with our communities?
How can we expand participation to new and underserved communities?
How can we deepen participation in our existing communities?
...
Summary notes:
Working group level of formality, bi-weekly meeting frequency
Coordination and information sharing, rather than policy setting
Operations will be naming someone to this group to replace PI Tim Boerner (who was standing in temporarily)
Community Discussion:
Allocations
User community
Wide variety of experience levels
expand into communities not previously using resources
Broadening PI eligibility to include students
scalable broadening participation: partnering with external projects
Make more appealing to students, especially undergraduates
work closely with Support Track
Support
User community (now called researcher community)
focus: undergrads, grads, faculty, staff, ci professionals
knowledge base: free, open, available, also pages in confluence
affinity groups with CSSN: self-run
match plus: small funding to match students with projects, 6 months maximum
match premium: PI brings funding, support matches students
very limited staff
Operations
Resource providers > broadening community of resource providers
Metrics
Originally, community was NSF, providing information about NSF-funded facilities
Now:
Resource providers & efficiency of their resources
Tertiary: end users and supporting end users