Agenda
- SDSU Site Visit update
- PEARC tutorial progress
- Meeting to discuss last week w/ action items for Eric & Jeremy, dry runs the week of 6-26.
- Jeremy will be building the tutorial image today
- Date setting for planning Tapia panel - after PEARC, late July.
- Updated XCRI metrics – see tables below
- Rich will put up a wiki page & we will update
- Toolkit testing - where? ongoing
- SP coordination updates
- Barb to plan PEARC dinner
Attending
- Resa
- Eric
- Francesco
- Barb
- Rich
Regrets
- Jeremy Fischer
- Craig Stewart
Metrics:
WBS Name | CRI |
Metric Level (KPI, L2, L3, Other) | L3 |
Metric Name | Toolkit updates |
Frequency | Annual |
Target | 4 |
Definition/Description | Number of updates to packages within toolkits or updates to toolkit scripts/glue code. Includes bugfixes/features/security improvements. |
Collection Methodology (Where does the data come from and where is it logged) | Packagers of individual rpms at Cornell maintain spreadsheet of version updates, Rich Knepper records this in the XCRI section of the wiki. Eric Coulter commits updates to scripts/glue code to git repositories, and records those updates in the wiki. |
WBS Name | CRI |
Metric Level (KPI, L2, L3, Other) | L3 |
Metric Name | New Toolkits released |
Frequency | Annual |
Target | 2 |
Definition/Description | Number of new toolkits released for use by community members, including use case, capability delivery plan, testing, and release. |
Collection Methodology (Where does the data come from and where is it logged) | Toolkit tracking pages in XSEDE wiki will have detailed description of each toolkit, and new toolkits will be counted each quarter. |
WBS Name | CRI |
Metric Level (KPI, L2, L3, Other) | L3 |
Metric Name | User satisfaction with CRI |
Frequency | Annual |
Target | 4 of 5 |
Definition/Description | Users of XCRI services (site visits, meetings, and tickets) are asked to report their satisfaction with XCRI services. |
Collection Methodology (Where does the data come from and where is it logged) | Direct request from CRI site visit participants, requestors from RT, and meeting partners. |