Get Help from Others
Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack
|Primary Mentor||Jan Flowers|
|Backup Mentor||Pascal Brandt|
|GSoC Student||Shekharreddy Mittapelly|
|Interested People||Darius Jazayeri, Burke Mamlin|
Hack the Atlas in the right direction†.
The exact scope of work is yet to be defined, but here are a few initial ideas:
Rewrite the atlas server backend as a node.js app presenting a simple Restful API.
Add functionality to support arbitrary metric from clients.
Link to Doc
openmrs-contrib-atlas (PHP Laravel Framework)
Pascal Brandt Darius Jazayeri I'm surprised that 'Rewrite the server code in a modern framework that is not PHP' is optional as this point. I believe that in the Dev/Design meeting with Bahmni, it was decided that rewriting this in Node.js would be a good GSoC project on it's own.
Shreyans Sheth, the idea is that whoever is going to pick up this project can help define how exactly it is shaped. We don't want to rewrite the code for its own sake, without also providing some business value. So a project proposal should suggest a set of new features and possibly technical changes to support them.
This project is entitled "Atlas Module Enhancements," but the work describes enhancements to the Atlas server, not the module.
I too do not think we should invest any more in the PHP Laravel Framework. It's a niche technology not commonly known by the folks trying to enhance or support the Atlas service. Our goal for the Atlas was to convert to a Nodejs application deployed via Docker. Any work done in PHP would either need to be completely re-written or abandoned when we migrate to Nodejs.
I would suggest: