Page Comparison

...

1. Working Group Updates (15 mins)

   1. Update from the Evaluation Working Group (Shawn Strande) (10 mins)

      1. Shawn sent update in email

      2. Will work with Shannon on how to track progress
         

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

   1. 8 August 2023 EC Summary

      1. none
         

3. Program Milestone CheckJohn Towns (10 mins)

   1. Action item for the awardees to update their program milestones

      1. Shelly Shelley - we need to update them based on modified goals that Support is going through

      2. 2 events calendared - only 1 is happening (Ag is attending Tapia - working on a piece for news)

      3. Another person from San Diego is attending Grace Hopper - what kind of things should she carry to and bring from the conference

         1. need to work on a plan for next year

         2. raise awareness for programs - possibly recruit new employees

         3. come back with report on how we can participate next year

   2. Reminder: Do not edit "Dashboard" tab, please edit "ACCESS program milestones" tab as needed
      

4. Identifying, prioritizing, and addressing ACCESS tasks: Stephen Deems (10 mins)

   1. What’s our process for addressing items like the following that cross awardees? If we know of certain things that need addressed, how do we communicate (and to whom) to prioritize and track that? Some recent topics:

      1. ACCESS Account creation: how do we request and discuss changes?

         1. Academic Status (currently optional field)

            1. ACCESS awardees and RPs are asking for this to be required

         2. Persons whose institutions aren’t in our database yet

            1. Process ill-defined and/or not implemented properly?

            2. Causes account creation process to stall (maybe?)

         3. Web/branding guidelines have not reached these pages

         4. Changing organizations — currently very difficult

            1. Is this a security concern that prevents ID holders from being able to do this?

            2. Could/should we preserve history of org. changes?

   2. runs in parallel with formalizing our working groups

   3. how do we track things? Things mentioned here that don’t have a home that need a home

      1. EC should be able to decide to keep or delegate who should own it

   4. Shelly Shelley - when you do things to talk to individuals, the communication gets lost and it doesn’t necessarily bubble to everyone

      1. Should there be another team that has representatives from the teams who could just report to the EC and have the authority to make the decisions. They will be paying attention to the milestones and make sure progress is being made

   5. EC Backlog - View in Confluence: Executive Council Backlog Overview

   6. How can we manage tracking actions when not everyone is using the same tools?

5. Support Evaluation Update @Shelley Knuth (10 mins)

   1. Support will be hosting feedback sessions at SC intended to understand more about services we are providing to the community and potential needs

   2. Will use CCEP dollars to host two on-site and pay for people’s travel

   3. Allows for options for people who wouldn’t get to SC otherwise, or for those who are already part of the ecosystem

      1. Campus Champions? Pegasus people?

         1. templated talks so they can also speak on things for us?

      2. Consider Gateways?

   4. Is it valuable to have a separate feedback session (more targeted sessions) for ACCESS wide needs? One specific to a service (like allocations)?

   5. Want to ensure we are all communicating about this/personas issue.

   6. Need to Coordinate with Engagements and DEI to make sure we are not duplicating

   7. Partner with NSF as well to spread information

6. Informational Items (10 mins)

   1. RAMPS David Hart Stephen Deems

      1. Website clarification updates

         1. Text has been incorporated to “add user” interface to indicate that the process isn’t instantaneous (displayed before and after an addition is made)

         2. 

            Allocation “Title” changed to “Project Title”

            1. Some researchers were entering their job title (e.g. Assistant Professor)

         3. Exchange interface updates

            1. Resource justification field was asked for by RPs

      2. 

         Modifications to AMIE packets to reflect “Grant Type” (e.g. Educational, Campus Champion, AI/ML) will be made shortly

         1. Notifications will be sent to RPs in advance

      3. API development for new user interfaces/website (~80-90% completed)

         1. For projects with extreme needs (>1,000 users) the calls are being returned in under a second

         2. Expecting to start integration this week/testing next week

         3. Corresponding re-vamped documentation sprint upcoming

      4. Innovative Pilots Planning

         1. initial meetings are underway with proposal partners (funcX)

            1. Interested in installing their stuff on ACCESS resources

               1. Could be a use case to allocate their work “calls” (think AWS lambda functions)

               2. Seems similar to a gateway but ACCESS could handle management of user accounts and resource balances

         2. More meetings coming with FABRIC (Jim G.) and Pegasus (Mats R.)

   2. MATCH Shelley Knuth

      1. We would like to get an up to date list of the software that each of the RPs are running. Can Operations assist with getting this list? Otherwise we would need to do a workaround.

   3. CONECT Tim Boerner

      1. June and December are bad to do travel - could we consider going to March September rotation? - put on next week

   4. MMS Tom Furlani

   5. OpenCI John Towns

      1. Kim Bruch attending Grace-Hopper. Would like input in potential ACCESS outcomes sought. (Shawn Strande)
         

...