...
Present: Jay Alameda, Cynthia Dillon, Shawn Strande, Cindy Wong, Ron Payne, Lizanne DeStefano, John Towns, Dina Meek, Lavanya Podila
Agenda/Notes
...
ACO Supplement Request
...
Ron
...
High
...
03/21/2023
...
3/31/23
...
Code of Conduct Discrepancy
...
Jay
...
High
...
03/21/2023
...
John’s suggestion - Using inspiration from Tim A's slide on “how to do it”, we can create a simple slide and add to the code of conduct
...
WG and Committees Discussion
...
All
...
High
...
03/21/2023
...
Next step is for ACO to circle back to WG's, bring all WG's together and have a conversation to ensure alignment?
...
Update the program wide meeting agenda
...
Lavanya
...
Medium
...
03/21/2023
...
(2 annual meetings) wherein WG and committee reps to provide a 10 minute update
...
IPR Q4
...
All
...
High
...
03/15/2023
...
04/10/2023
...
Needed by 3/24 for John to make first pass
...
Invite ACO reps to awardee meeting
...
Lavanya
...
High
...
03/15/2023
...
Asked Amber working on it
...
Risk Identification
...
Ron
...
Medium
...
01/11/2023
...
3/3/2023
...
Risk register populated with ACO risk summary info. Each owner needs to complete the details of each risk.
...
UIUC Guidelines regarding content that ACO needs to adhere to (GDPR/Accessibility)
...
Dina
...
Low
...
01/25/2023
...
Dina to confirm with Illinois security team - 3/15
...
Collaborating with ACCESS/Letters of Collaboration
...
Dina
...
Low
...
01/10/2023
...
Dina drafting content for (EC) review
...
All ACCESS paper for PEARC
...
John
...
Low
...
01/24/2023
...
04/21/2023
...
Submission deadline is April 21
Near-Term ACO Deliverables
...
Deliverable
...
Due Date
...
Owner
...
State
...
Start-up
...
Establish an OpenCI Performance Management Plan
...
7/31/2022
...
Ron Payne
...
Started
...
Debrief on EC meeting John Towns
RAMPS update had following item:
ACCESS awardees and/or RPs may be interested in some metrics included in RAMPS annual report:
Diversity (institutional; race; gender); inclusion index; allocations success rate; FoS; credits awarded/exchanged/used; allocations by resource; publications, etc.
If interested, please contact Dave.
Question: Yes, interested: can we request this for the ACO rather than having each of us asking Dave?
Prep for NSF Annual Review John Towns
Dry-Run scheduled for Friday, 14 April, 2023 from 2-3 PM ET/ 1-3 PM CT/ 11 AM-1 PM PT
From ACO-NSF meeting on March 27, Tom mentioned that “Review: driven by pep and KPIs” -
What implications does this have for our review prep?
What should be our base outline/content covered for each of our areas?
?
...
Topic
...
Responsible Persons
...
Priority
...
Added
...
Needed By
...
Notes
...
Acceptable Use policy - Inform during next week's CGC meeting
...
John
...
“Note: This policy is awaiting formal acceptance by the ACCESS Cybersecurity Governance Council.” John to bring this this topic during next week’s CGC meeting
...
...
7/31/2022
...
Jay Alameda
...
Started: Initial draft for revision at https://docs.google.com/document/d/1ClRorlMAIUa30f_Fhr_XhP7Q96SH-gY3inbL2yspBog/edit?usp=sharing
Updates
EAB Updates Shawn Strande
Evaluation Update Lizanne DeStefano (Unlicensed)
Communications UpdateDina Meek
Social Media
Discussion at EC about content posting processes/approvals?
Community Engagement UpdateJay Alameda
Code of Conduct review:
Underway, initial thought was to clean up long code of conduct and add it as a “for further reading” fine print addendum to the EC-approved code of conduct
Comments added to the long code of conduct: https://docs.google.com/document/d/1J6MV3YMGGp57Zruxl4p-J0g0dcl62M3OLfV4Jz1RCac/edit?usp=sharing
Remember that the CB&E team includes a member from each service area plus the ACO, which makes the review a bit awkward.
Immediate issues with long code of conduct
Mentions steering committee without definition
Reporting mechanism inconsistent with EC-approved code of conduct (and provides a non-anonymous ticket submission as the preferred means to report).
It it is too long (and has some redundancy), but the overall tone: positive.
Original attribution: US-RSE plus 4-5 other organizations
Questions about the ombudsperson mentioned in the EC-approved code of conduct:
Should this be someone separate from ACCESS?
Should it be an ACCESS PI or Co-PI?
If it is OK to be populated with ACCESS personnel, should it have representation from all awards?
What training should we provide for the ombudspersons? DEI training? What should the source of this training be?
Community Building And Engagement Plan: Draft in progress (https://docs.google.com/document/d/1ClRorlMAIUa30f_Fhr_XhP7Q96SH-gY3inbL2yspBog/edit#heading=h.21ylrh1soxje ).
MS-CC annual meeting: Lizanne is invited, John is on the external advisory board, should we doing more (sending more people, having an ACCESS presence). Time is running short for quality participation this meeting.
Impact page from RAMPS: Dave Hart is soliciting input, gathering input from ACO at https://docs.google.com/document/d/1M2WsuKWP29Q6WM11QFxbBqlhDcMWrHWs60WKb3R2HtI/edit . The old page was tremendously valuable, we hopefully have an opportunity to make something even better.
Staff tool: Allocation Queries: Dave granted me access to https://xacct-admin.access-ci.org/allocations_queries, which is fantastic! I think I’m not the only one interested in this, can we consider staff access more broadly (across program areas + ACO)?
RP Forum Chair: RP Forum is looking for a chair, nominations have been short in coming. Request for some of us to consider this role, but appear to have a COI that strikes us out:
RP Forum Chair duties:
Term: Remainder of the calendar year;
by then, there should be bylaws that specify a regular election period as well as roles and responsibilities.
Convene and run the biweekly meetings (including drumming up topics and presenters)
Oversee the creation of bylaws
Represent the RP Forum on the ACCESS External Advisory Board.
Oversee annual elections
As a reminder, these were the recommendations from the RP Forum Charter committee: If the RP Forum accepts the provisional charter, we also suggest the following to appoint a RP Forum Chair
The SP Forum elects the Chair. It may opt to define additional roles to be elected in the future (e.g. vice-Chair, etc.).
To avoid potential conflicts of interest, the SP Forum Chair should not be an individual who is an ACCESS Program awardee PI/Co-PI or lead any area of effort of an ACCESS program project.
In order to select an initial Chair, we recommend a simple majority of the voting members of the Forum with membership as defined in the provisional Charter.
Project Office & Tools Update Ron Payne
PEP v1.2 approved by Tom G and added to ACO wiki and Google folder.
ACO Supplement for In-Person Program Meetings has been formally submitted to NSF.
NSF Review wiki page setup and draft presentation slide deck created.
Performance Management Plan to be sent to John for final review by Friday, 7 April
Options for redistributing PY1 underspend funds being collected. Will be brought to this group for discussion, potentially next week.
June in-person logistical planning underway. Will be collecting agenda topics from Program in early-May.
Misc Topics
(John) Preparing the Supplemental Request Submitted on April 5th: What do we need to do as yet?
(John) DEI: Are we handling this appropriately?
Would like to see solid sources to base our work - some things that are possibly relevant (but not as close as I’d like):
Looking for solid actionable recommendations from experts in the field to base our DEI plans.
...