Page Comparison

...

1. Approval of summaries from prior EC meetings John Towns (5 mins)

   1. 17 January 2023 EC Summary (approved)

2. Informational Items (10 mins)

   1. RAMPS Stephen Deems

      1. sub-group rolled out to align the headers and footers of the website. This should be doable in the short-term.

      2. The Researcher Advisory Committee is starting to spin up.

         1. We’ll check with Laura as to whether a representative would be available for the EAB.

   2. MATCH Shelley Knuth

      1. Do we want an internal ACCESS co-located event at PEARC? I know a guy who can add it.

      2. EC decision to Block Thursday (PM) as tentative for the co-located event

      3. Discussion regarding funding for the event, no decisions made

      4. Continuing on with activities as reported last week.

   3. CONECT Tim Boerner

      1. We continue to recruit students at all levels for our student training & engagement program (STEP). Please help spread the word and encourage students you know who may be interested in pursuing a career in CI to apply! https://operations.access-ci.org/step

      2. Refactored ACCESS Allocated resource roadmaps being released early in February

         1. Splitting it into 3 separate roadmaps for compute, storage, and cloud

         2. Streamlining the integration tasks and creating a more useful integration timeline graphic

         3. Improving the format and organization of all the task documents. 

   4. MMS Tom Furlani

      1. Onboarded 2 new developers

   5. OpenCI John Towns

      1. EAB meeting is now set for March 2, 10am-12pm PDT. Will be reaching out to everyone to get input on agenda

      2. Progress on feedback received: we have implemented some tracking mechanisms to ensure the ACO makes its deliverable on time or it is recognized when that is not possible and why.

      3. access.org domain, or NOT: The company we have been working with continues to be very difficult at every step of the way. Should we abandon this?
         EC decision to abandon the work to secure access.org domain.
         

3. Working Group Updates (10 mins)

   1. Ticketing Working Group @wsnappch@iu.edu

      1. Team did an evaluation on technologies, arrived at an alternate approach to utilize JIRA service management

      2. Preliminary approach will be complete in the next couple weeks

      3. We're going to be doing a lot of testing to ensure evaluation matches stakeholder expectations

      4. Team is also developing communications to reach out to the RP's and let them know how its going to affect them

      5. Target to complete transition March end, hopefully complete by April

      6. Follow up question on how different the new feature is operationally? Roughly the same, only user interface is in the JIRA service management format

      7. Discussion regarding who’s monitoring the queues - Alana from the MATCH team is monitoring the queues, but as a general rule, whoever is marked as the owner, should be watching the ticket.

      8. WG will also work with RP’s to develop certain specific features, for instance, tickets get closed in 2 weeks if there’s no response
         

4. ACCESS-Wide Inclusive Language Statement/Guidelines Tim Boerner (10 mins)

   1. Operations would like to do something quickly in this space, so we’re looking to see what other tracks are thinking/planning

   2. EC in agreement that each of the awardees are responsible for maintaining the content, that is in alignment with the guidelines. If this proves insufficient, then we can create a working group.

5. ACCESS community communications Shawn Strande (10 mins)

   1. Please see attached slide

   2. EC supports the concept of having some sort of channel whereby information can be shared with the broad ACCESS community on a timely basis.

   3. Some PIs noted they are already doing their own communication through channels they have established, e.g., MATCH and CSSN.

   4. It was noted that RP's have an interest in have a communication channel, in order for them to be able to push information to the users. EC in agreement that channel should be moderated.

   5. I asked if new allocated users are getting added to the ACO’s Constant Contact database. Dave Hart and Stephen Deems said not now, but will shortly. It has previously been a manual process, but that halted as they work through privacy policy.

   6. Shawn to bring this topic to the ACO for discussion and would present a proposal at a future EC meeting.

   
   

6. Misc Topics

   1. Discussion and action item - All ACCESS paper to presented at PEARC? John Towns

...