2015-02-12 Developers Forum

How to Join

 Click here to expand...


By Browser

By telephone

  • US telephone number: +1 201.479.2627



  • Quickly review previous meeting minutes (5 min)
  • Upgrading Spring (deciding what we need to do and how we will see it done)
  • GSoC 2015 Planning
  • Review next meeting agenda


View at notes.openmrs.org


OpenMRS Developers Form 2015-02-12
  • Michael Downey
  • Bhavana _
  • Maurya _
  • Aniketha _
  • Bharat Akkinepalli
  • Sandeep Raparthi
  • Daniel Kayiwa
  • Ryan Yates
  • Burke Mamlin
  • Ada Yeung
  • Paul Biondich
  • Sharon Varghese
  • Rafal Korytkowski
  • tharunya _
  • Govind
Agenda & Notes
  • Review last week's TODOs
  • TODO: Put out a call for volunteer OpenMRS 2.2 release manager (Burke)
  • TODO: Burke to define the explicit Upstream coordinator role and look for someone(s) to fill it
  • TODO:  See if we could make a script to Create a database/table/document to  track libraries (someone?). Joseph Kaweesi was working on a module to  show dependencies.
  • TODO: Burke to suggest this GSoC project (Legacy UI moved to a module)
  • TODO: Interested potential mentors sign up for GSoC
  • Introductions of new people participating
  • Upgrading Spring
  • Why upgrade Spring?
  • Current version is 4.1.4
  • We are using 3.2.7 (released 28 January 2014)
  • The 3.2.7 release officially turns the Spring Framework 3.2.x line into  maintenance mode.
  • A 3.2.8 released Feb 2014; however, it only contained bug fixes and was intended to be the last regular 3.2.x release
  • Upgrading Spring will not happen overnight and Spring 3.x is no longer being actively developed (getting bug fixes only).
  • What are the issues?
  • Many old controllers.
  • Jackson library would need to be upgraded from 1.x to 2.x as well.
  • Per Darius: "Upgrading Spring will be a large task."
  • Possible Solution:
  • Branching OpenMRS and upgrading the controllers for a start.
  • Who does this? When?
  • If we have a group (or individual with lots of spare time) coming to OpenMRS with good technical skills asking how they could help, we point them to TRUNK-4607.
  • If we could get it to a large amount of simple tasks, then we could distribute those tasks.
  • Perhaps our only option for now is to task a /dev/4 or /dev/5 with "owning" the issue enough to come up with a strategy.
  • We could start the process by creating a controller that works with Spring 3 and Spring 4 and working to migrate to it (while still on Spring 3) to lessen burden of switching to Spring 4.
  • TODO: give someone the authority to run with this – i.e., Burke will reply to existing dev thread and see if someone (Lluis, Kirs, others) who wants to dig into it. 
  • Is there a time limit?  Is there a point at which we will have no choice but to upgrade?  Or can we code OpenMRS against Spring 3 for the next 20 years and just live with any security risks or other limitations?
  • For example, if we moved toward a web framework that promoted use of Angular & similar techologies against REST services, then Spring controllers may not be used so much.
  • Is Spring 3 a blocker for Java 8?
  • The answer appears to be YES
  • GSoC 2015 Planning
  • Mentoring a student is a great way to (a) introduce someone new to open source and OpenMRS, and (b) help get some work done over the summer!
  • 20 February 19:00 UTC is the drop dead date for ideas to be posted! Make sure yours are updated before then. Include:
  • Projected skill level(s) needed
  • Primary mentor (you)
  • Backup mentor(s)
  • Short project description
  • Initial goals
  • "Bonus" achievements
  • Mentors may post more than one project idea each.
  • Students will provide a timeline on how to achieve the goals of the project in the time provided, and should (really should!) contact mentors ahead of time to discuss their ideas.
  • GSoC/OpenMRS Info Sessions at Universities wanted!
  • Materials are available to help!
  • /dev/0 to /dev/1
  • look at pull requests
  • scan multiple repos
  • Use a custom field for GitHub ID in addition to currently-used email address of Discourse account
  • Usage:
  • This can be used for looking at submitted PR's
  • Devs will need to add their GitHub ID to their OpenMRS Talk profile page
  • TODO: Spec out a Moodle server based on our usage plans
  • 1 GB ram per 10-20 concurrent users
  • LAMP stack
  • TODO: Figure out how to get data out of Moodle
  • Similar Discourse plugin to github?
  • Scan some API or database to look for OpenMRS ID vs exam status/score
  • /dev/1 Badge Criteria:
  • OpenMRS ID
  • Validated by having a Discourse account
  • Development Environment, RTFM, Pass 5-10 question Introductory Quiz
  • Validated by passing the Moodle Quiz, and a to-be-written Discourse plugin to validate
  • Introduced
  • Earned the "Friendly User" Badge
  • Claim ticket & Pull Request Accepted
  • Validated through earning a "Code Contributor" badge via the Discourse github plugin improvements describe above
  • After Action Review
  • What did you expect to happen?
  • What actually happened?
  • What can we do better?
  • Preview next week
  • OpenMRS 2.2 showcase
  • WIP: Angular AMRS forms ± mobile web app



  • Audio recording of the call: Listen online or download (available after the meeting)