Page Comparison

...

• RAMPS: Stephen Deems (v), Dave Hart

• MATCH: Shelley Knuth (v), Julie Ma

• CONECT: Tim Boerner (v), Leslie Froeschl

• MMS: Tom Furlani (v), Joe White

• OpenCI: John Towns (v), Shawn Strande, Ron Payne, Lavanya Podila, Lisa Kaczmarczyk

• NSF: Tom Gulbransen (NSF)

• Guest Speaker:

  • Julie Ma for Slack Channel Topic

...

1. ACCESS Community Slack channel? Shawn Strande & Julie Ma (10 mins)

   1. https://app.slack.com/client/T03T9KZKP7H/C03THJT91D4

   2. Match team is ready to support the slack channel

   3. Action - Suggestion to draft a statement that tells us the users - what is the purpose of this slack channel; Julie to draft a statement; Ron to post the statement on the slack channel
      

2. Approval of summaries from prior EC meetings John Towns (5 min)

   1. 4 October 2022 EC Summary (approved)
      

3. Informational Items (10 mins)

   1. RAMPS Stephen Deems

      1. NTR

   2. MATCH Shelley Knuth

      1.  

   3. CONECT Tim Boerner

      1. Nothing of note this week.

   4. MMS Tom Furlani

   5. OpenCI John Towns

      1. EAB call for nominations is live on the ACCESS website: https://access-ci.org/now-accepting-nominations/
         

4. Code of Conduct Discussion and Vote John Towns (10 mins)

   1. No further edits at this point

   2. Will follow up later and identify who would be the ombudspersons

   3. Ron to send out a request for list of all employees on ACCESS so that the code of conduct can be shared with all the tracks and the ACO

   4. Decision - Approved by the EC

   5. Next steps - email communications soliciting members to be ombudspersons

    
   

5. ACCESS Core Information Security Policy VoteJohn Towns (10 mins)

   1. Dave Hart - Section 2.5 needs a reference

   2. Tim Boerner's question “what are the factors used to determine if it is appropriate for a policy to be approved by the EC”- John says not sure if we can be really clear and succinct at this point, we can adjust this if we feel the need in the future

   3. Tom Furlani - Who's enforcing and implementing this? Representatives of the cybersecurity governance council would be keeping an eye out, John to bring this up in the next CGC meeting that it is an expectation from the council that the policies are being followed

   4. Tom G - Will the council share reports/scans etc? Would that be available to be shared? These should be available, there is a group that is tracking the scans. John suggests that this could be added into the council's charter. John to bring this up in the next CGC meeting

   5. Decision - Approved by the EC
      

6. Risk Management ProcessRon Payne (10 mins)

   1. John’s question - how are all the tracks managing risks?

   2. Track 3; created a risk project

   3. Track 1; nothing yet

   4. Tom G shares that Shelley agreed with having a common tool that can be used project wide

   5. Track 4; has some mechanisms in place right now

   6. Decision to move forward with the risk management process flows shared by Ron to manage program wide risks and award specific risks; to be developed by Ron and then shared with the EC
      

Reference: EC Backlog

Reminder Next EC Meeting: 25 October 2022 (No meeting on 18 October 2022)

...