2015-01-15 Developers Forum
How to Join
Agenda
Quickly review previous meeting minutes (5 min)
Process for keeping track of components, libraries, dependencies
#MOZ15 OpenMRS-DHIS2 hackathon pre-planning
Review next meeting agenda
Minutes
OpenMRS Developers Forum 2015-01-15
Recording: http://goo.gl/pkCmtr (audio only) https://connect.iu.edu/p1qqpkd0o3m/ (Adobe Flash)
Attendees
Michael Downey
Parker Erway
Burke Mamlin
Ryan Yates
Daniel Kayiwa
Pierre Dane
Hannes Jembi
Maurya
Sara Armson
Pascal Brandt
Brett Ausmeier
Karl Wurst
Sharon Varghese
Bhavana _
Wyclif Luyima
Darius Jazayeri
Paul Biondich
Uzanysa _
Akash Agrawall
Mike Seaton
Cosmin Ioan
Alexis _
Rafal Korytkowski
Tharunya _
Kmit Satwikreddy
Agenda & Notes
Review TODOs from last week
Run through strategy for each OpenMRS 2.2 distributed module on design forum soon (Jamie Thomas)
Invite Bahmni team to present their OpenERP integration as a form of billing support OOB for OpenMRS RA (Jamie Thomas)
Invite PIH to present "2.0-ified" appointment module for potential RA integration
TODO: Put out a call for volunteer OpenMRS 2.2 release manager (?)
TODO: get Wyclif in touch with David & Audrey to coordinate sprint kickoff time. (?)
Process for keeping track of components, libraries, dependencies (40 minutes)
Darius: Realizing we're behind isn't enough. We need people to make sure upgrades are getting done, tested, etc.
Example: Jackson JSON library. In OpenMRS Platform 1.10 we are using 1.5.0 (from 3/2010). In 1.11 we will be using 1.9.13 (from 7/2013), they have released 2.5.
Reasons to upgrade
What do we gain?
New devs will be used to contemporary libraries, not really old ones
How much work will it take?
Is it backwards compatible?
Issues
Backwards incompatibilities can be introduced
Smaller (less popular) libraries - can be challenging to get documentation on old versions
Potential approaches to identify the work needed
Upstream coordinator? (April 2014) https://groups.google.com/a/openmrs.org/d/topic/dev/VXvPiAO5fhM/discussion
TODO: Burke to define the explicit role and look for someone(s) to fill it
Use topic fest to schedule discussions
Create a database/table/document to track libraries (version used & current stable release)
This could probably be scripted – i.e., given a list of specific libraries, scan POM in core or distributed module source, then grep the latest stable release version
TODO: See if we could make a script
TODO: Suranga to share output of version diff for CORE with dev list
Review library versions as part of release process
Create tickets to upgrade library version