I see us ending up with a layered approach to supporting Kuali Rice on the campus. I like to compare this to how we're currently support CAS from the JA-SIG community. For CAS, we provide "first line" support via a campus mailing list and campus wiki ( https://confluence.ucdavis.edu/confluence/x/eFY ). However, we also refer people to the JA-SIG project resources.
Our first line of documentation and support gives us a few advantages:
- We can provide details on our local CAS implementation to the local community (timelines, features, etc).
- We don't require the entire UC Davis community to follow the CAS roadmap, we can do that centrally and communicate when/how that roadmap will be implemented on our campus.
- We can fill in any gaps that might exist in the CAS documentation.
- We can build that local community here so technical staff and assist one another through their local connections/relationships.
I think a very similar model will work well in the Kuali Rice space as well. Just brainstorming this morning, I thought the model may visually look like this:
Again, we provide that front line support to our local community while still making them aware of and referring them to the larger Rice community resources. The ITAG and larger UC wide effort will fit in this picture as well as that effort moves along.