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
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
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.
navigation should always open in the same tab
Add “Coordination” to left side main nav pointing to the Coordination office page (link tohttps://access-ci.org/about/ )
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.
Track 4 is ok with “Metrics” as their navigation name; will confirm in EC 7/19
Group approved @...'s proposed sitemap update which will be shared with EC 7/19
Group agreed “Track” and track acronyms should not appear on access.org; may be introduced at the various track levels
Group agreed on dropdown menus for universal navigation; will provide those suggested subnavs in the “input collection page”
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
Decided on wording to use in the first half of the EC Charter
RP Forum Chair will be a voting member of the EC
RPs are invited to all Quarterly meetings - in person and virtual - there may be certain sections they cannot participate in, but overall it is a positive step to include them
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
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
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.
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
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
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
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
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.