OpenCI ACO Weekly Leadership Meetings

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/312541185

1. Go ahead and reserve booth for SC24 and perform a Cost Analysis to see if it is the benefit we believe it is - with the possibility we would pull out if we decide it is not

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/307462207

1. ACO Retreat - Aug 30, 2023 - Decided to use in meeting agenda Confluence Decision Macro
2. ACO Retreat - Aug 30, 2023 - Decided to track attendance at meetings via Confluence Status Macro
3. ACO Retreat - Aug 30, 2023 - Decided to use Confluence more effectively - implement Parking Lot via Confluence Status Macro

1. Per EC - Reserve use of main ACCESS logo for ACCESS-wide communications; use individual service area/track logos for communications specific to your audiences about your topics

1. We will move the original group meeting from Thursday to Wednesday at 3 (CT) and rename, reformat as “Web Presence Working Group” that will be more inclusive of others working on the web presence, beyond branding.

1. navigation should always open in the same tab

1. Add “Coordination” to left side main nav pointing to the Coordination office page (link to )

1. For enhancements and bugs, we’ll use the ticketing system to collect, triage and status; each track will decide whether to bring it into Jira for their operations. We will set up a queue in the ticketing system.

1. Track 4 is ok with “Metrics” as their navigation name; will confirm in EC 7/19

1. Group approved @...'s proposed sitemap update which will be shared with EC 7/19

1. Group agreed “Track” and track acronyms should not appear on access.org; may be introduced at the various track levels

1. Group agreed on dropdown menus for universal navigation; will provide those suggested subnavs in the “input collection page”

1. Each service area/track representative will provide a lead to a story during this meeting the first week of each month - just a lead; Megan and Hannah can utilize for website and newsletters

1. access.org was chosen by track PIs as domain, and access-ci.org will redirect to access.org.

1. Committee Charter Approvals - Communications Standing Committee Charter approved
2. Committee Charter Approvals - Web Presence Standing Committee Charter approved
3. Committee Charter Approvals - ACCESS User Profile 2024 Working Group Charter approved

1. Future IPRs will contain lists of funded staff

1. EC Approved Program Wide Goals via Email
2. EC Approved reviewing and approving Charters off line via email

1. EC approved moving forward with getting WG/SCs and other Teams to input items to the Program Milestone Check
2. EC approved starting a Staff Recognition Award for ACCESS
3. EC decides - Quarterly Meeting at PSC - Sept 25 and 26

1. We will encourage EC PIs to go back to their teams and review the weekly EC meeting notes with them to help in distributing information to the rest of the project members

1. Unanimous approval of the Personas Doc -

1. Enabling Multi Factor Authentication for Atlassian Confluence and Jira - Approved
2. Move back to weekly meetings for an hour - Lavanya will adjust the calendar

1. Communications Plan - Approved

1. Evaluation Plan approved by EC Vote - 12/19/2023

1. Go ahead and reserve booth for SC24 and perform a Cost Analysis to see if it is the benefit we believe it is - with the possibility we would pull out if we decide it is not

1. Adopted ACCESS DEI Working Group charter
2. Adopted Program wide goals and metrics

1. ACO Retreat - Aug 30, 2023 - Decided to use in meeting agenda Confluence Decision Macro
2. ACO Retreat - Aug 30, 2023 - Decided to track attendance at meetings via Confluence Status Macro
3. ACO Retreat - Aug 30, 2023 - Decided to use Confluence more effectively - implement Parking Lot via Confluence Status Macro

1. Evaluation Working Group Charter: - approved

1. For enhancements and bugs, we’ll use the ticketing system to collect, triage and status; each track will decide whether to bring it into Jira for their operations. We will set up a queue in the ticketing system.

1. Each service area/track representative will provide a lead to a story during this meeting the first week of each month - just a lead; Megan and Hannah can utilize for website and newsletters

1. Group decided NOT to add “Coordination” to the top nav - not that helpful to users and gets very crowded.

1. Each service area/track representative will provide a lead to a story during this meeting the first week of each month - just a lead; Megan and Hannah can utilize for website and newsletters

1. Each service area/track representative will provide a lead to a story during this meeting the first week of each month - just a lead; Megan and Hannah can utilize for website and newsletters

1. Per EC - Reserve use of main ACCESS logo for ACCESS-wide communications; use individual service area/track logos for communications specific to your audiences about your topics
2. We will move the original group meeting from Thursday to Wednesday at 3 (CT) and rename, reformat as “Web Presence Working Group” that will be more inclusive of others working on the web presence, beyond branding.

1. We will go with “ACCESShpc” as our social media handle

1. Per John Towns, we’re not to use NSF in our social handles as they are going through some brand work and have put a moratorium on such usage.

1. Track 4 is ok with “Metrics” as their navigation name; will confirm in EC 7/19
2. Group approved @...'s proposed sitemap update which will be shared with EC 7/19
3. Group agreed “Track” and track acronyms should not appear on access.org; may be introduced at the various track levels
4. Group agreed on dropdown menus for universal navigation; will provide those suggested subnavs in the “input collection page” linked above by 7/22