Continuing the discussion from Sync2 Testing Report:
We actually have very little specific insight at the shared OpenMRS level about why people have or haven’t upgraded from Platform 1.x to 2.x, so thank you very much @ningosi for sharing this analysis!
It has been 1.5 years since Platform 2.0 was released, and uptake of Platform 2.x has been slower than I had hoped (perhaps unrealistically). Personally I think it’s time to invest some community effort into addressing all the sorts of hurdles that people have faced in getting to the latest Platform releases.
I propose that we do a community sprint, and spend a couple of weeks of focused volunteer effort addressing all sorts of issues related to “helping people get to Platform 2.x.” Thoughts?
Some of the issues that Nicholas mentions here could easily be addressed in that kind of a sprint.
I just commented on the linked Talk topic. I think we should put a workaround for this in openmrs-core, since it affects anyone using the reporting module (including anyone running the refapp).
Historically we have not tried to proactively upgrade any of the non-refapp modules for Platform 2.x, but I’m proposing that we do upgrade and test a bunch of modules in this sprint that aren’t in the refapp and haven’t been community-supported.
@ningosi did you get to test the snapshot version, and did it work for you?
It seems like an easy task to release a version of patientflags that removes the logic dependency. @mogoodrich thoughts? Or are you no longer really the owner of this module, and it just requires another volunteer to do the release?
Would be worth upgrading this in a sprint.
You’re not using the logic module directly, right? So as long as we drop the logic requirements from other modules, that’s good enough? What are all those modules? Anything besides patientflags mentioned here?
I recall this is quite old, but it could still be upgraded in a sprint.
Should be upgraded in a sprint.