Page Comparison

Agenda/Notes

1. Fate of Conference Competitive Analysis (CBE & Comms) Topic 2- Jay, Dina, Kim

   1. Prioritizing different conferences - traditional + other suggested ones

      1. need to start planning for SC24 - it is in November if we go

      2. we have put a down payment on it - but there will be another payment due soon that if it isn’t paid we lose early registration discount

      3. Refocusing Community Engagement - what will ongoing strategy be?

   2. Which conferences should be our audience?

   3. Wanted to have list done by end of February

   4. Where does this task set going forward?

   5. What budget should we plan on? - EC determines where we will be spending funds

      1. Communicate each as a discussion point to the EC - make separate decisions?

      2. Should there be a holistic look - and approve the set for 2024 which would make things easier for budget?

      3. Any conference take a lot of planning for us to attend

   6. There are different needs between what Comms will engage with at a conference vs Community Building and what they do at a conference

   7. Perhaps put this on our Chicago conference agenda to discuss? or should the EC make the decision?

      1. present as an investment planning schedule

      2. get initial info that we have - send to EC now and let them know we will discuss in the Chicago meeting

2. Review Action Items

   1. https://access-ci.atlassian.net/wiki/spaces/ACP/pages/317521925/ACO+Action+Tracker#:check_mark:-ACO-Meetings-To-Do-Items

3. Review Metrics Spreadsheet

   1. https://docs.google.com/spreadsheets/d/1j8X1aFKwXQJ90mMi4grYuWnzDisi8qb3jirc61hKCYY/edit#gid=314453872

   2. Should any other Metrics information be pulled from anywhere else?

      1. /wiki/spaces/ACP/pages/201195544

      2. https://drive.google.com/drive/folders/1BBnVCxPOehm4z992_HQ7ka-eYLgYD7I- - for PEP

      3. https://docs.google.com/spreadsheets/d/1tdcQjm5Xl5FuccCmKxjg28ZHjHKeZF9sXs-trFm47X0/edit#gid=2060503881

4. Following up on MFA for Confluence/JIRA - MFA Follow Up Tracking

   1. Shortened text for email to EC needs approved:

   2. We have had a request from ACCESS Cybersecurity to add Multi-Factor Authentication/Two Factor Authentication to Confluence and JIRA. 

      This is being proposed so we can do our best to eliminate unauthorized access resulting from disclosure or compromise of reusable passwords (which remains the most common source of intruder access).  So far, we have not had a problem with this in JIRA/Confluence, but it would be nice to be prepared in advance of any attempted intrusions.  

      Effects on User Experience:

      • For public access sites/pages/documents, there should not be any difference in user experience, as no accounts nor authentication are required.

      • For sites/pages/documents that currently require a user to be authenticated for access, this would be an additional step to complete authentication.

      Some Initial Plans for Implementation:

      • We will need to create a test site to try things on before we roll out a configuration change that affects everyone

      • We'll want to document what people can expect to see when the change is put in place

      • We will need instructions on what they may have to do to update their login preferences to add TFA

5. Updates

   1. Shawn Strande

   2. Cindy Wong

   3. Dina Meek

      1. Comms Plan approved; charter?

      2. Web Presence - Dina developing a plan for feedback; charter to be updated based on this

   4. Kimberly Mann Bruch

   5. Jay Alameda

   6. Lavanya Podila Shannon Bradley

      1. Risk Register Review - Change Tracking Summary Report

         1. Based on discussion with NSF yesterday - wondering about how we communicate regarding changes in risks.

         2. To improve visibility re: Risks and other team updates / changes - I have changed the view of the summary risk report

         3. OpenCI ACO Weekly Leadership Meetings

         4. I suggest we add a segement segment to this meeting where we review the risks that have been updated since our last meeting

         5. We can then reach out to teams when we feel there are opportunities to discuss how certain risks impact other teams or the project as a whole.