@r0bby, I pointed this out on today’s call. Getting sustained funding for IT support is hard. Like a dial tone, people just assume it should work. Other than waiting until we can find a benevolent philanthropist to donate money or for you to hit the lottery and decide you want your winnings to fund OpenMRS IT support, our best chance is to find ongoing funding streams for the community (whether through grants, certification programs, etc.) and bundle in IT support costs. Since OpenMRS has always been a collection of implementing orgs agreeing to work together (not a single company selling a product), most funding around OpenMRS is tied to specific projects or within implementations that aren’t prioritizing community infrastructure.
We know that infrastructure is a top priority. It’s what has allowed the community to succeed to this point and we really do desperately need dedicated resources for it (e.g., a dedicated junior sys admin could learn a lot from someone like Cintia, help us with migration to Jetstream, get things fixed & patched, etc. Part of the reason community members meet weekly to help on the leadership call is to brainstorm and take on tasks that could lead to non-tethered funding for the community. We could use any practical ideas on how to raise funds for dedicated infra support.