/
2015-02-12 Developers Forum

2015-02-12 Developers Forum

Feb 12, 2015

How to Join

 

 

Agenda

  • 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

Minutes

View at notes.openmrs.org

 

OpenMRS Developers Form 2015-02-12

Recording: http://goo.gl/2lUSJD (audio) https://connect.iu.edu/p5b263bq3lz/ (Adobe Flash)

Attendees:

  • 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!