MSP SIG - Meeting 22 - 2024-08-13
- Eric Jansson
- Ann Su
Participants
Agenda
Allowing MSPs to get involved earlier in development and testing cycles for Ed-Fi technology releases
Admin Console Roadmap (will be deferred to Sept)
Data Mapping
Notes
Early access to releases
MSPs would like capacity to test earlier. Example is ODS 7.1: brought in tenant management, would like to see this earlier, as it required work to adjust to. Can earlier builds be accessible?
That code exists today - what's the gap to getting the MSPs to use those? What would help MSPs?
Every time the Alliance teams merge codes, there is a binary built, a new Docker container
can work on how we label these
need to formalize the communications for both directions
seems to be more about communications - how can we connect the loop between tickets/bug reports and new builds?
Note: Jira Cloud will cause community to lose ability to see and comment on tickets - this is unwelcome
Q: Could we use GitHub? A: GitHUB is harder to control who has access
We are talking about a trusted partner program - how would that work? See actions at bottom.
Admin Console Roadmap
Deferred to Sept, btu briefly discussed a few issues
Q: Admin API will continue to act as a buffer for admin functionality. A: yes, confirmed.
The Alliance encourages MSPs interested in Admin API to get involved in Admin work group
Administrative Tooling Work Group
Data Mapping
Remains a big problem, esp. for assessment data
lots of redundant work in MSP ecosystem
lack of clarity about some best practice
Q: Before the Alliance published Mapping EDU, but is there a replacement?
A: MappingEDU was bulky and hard to use - very low usage. Outputs were also not machine-readable.
A: the Alliance is not providing one currently, but at the last Tech Congress we agreed that if field projects give Ed-Fi the artifacts that capture proposed mappings and artifacts that implement those, we will publish them (already doing this for data import template, but don’t think it’s a scalable mechanism). Also the Alliance will work to convene vendors to participate in the validation of these mappings.
Generally the discussion proposed that we look into a common, machine-readable language / technology that captures sanctioned mappings.
Actions
Cover changes under Jira Cloud to see what we can do to not lose visibility and input of community and discuss options for early releases. (Stephen F)
Keep Mapping discussion on Sept agenda