ACCESS Communications Standing Committee

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/52035597/2022-08-18+Meeting+notes

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.

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/59736065/2022-08-25+Meeting+notes

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

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/79527960/2022-09-14+Meeting+notes

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.

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/85721089/2022-09-29+Meeting+notes

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

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/89915393/2022-10-06+Meeting+notes

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

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/94175244/2022-10-12+Meeting+notes

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

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/92307500/2022-10-13+Meeting+notes

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

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/58228757/2022-8-18+Meeting+notes

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.

https://access-ci.atlassian.net/wiki/spaces/ACP/pages/3244041/ACCESS+Communications+Topics

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