Child pages
  • 2016-01-14 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

In person

Courtesy, please

If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.

Interactive meeting - Adobe Connect

  • We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at http://connect.iu.edu/omrsdf. For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.

By telephone

  • US telephone number: +1-888-510-4073
  • Access code: 24222#

By Browser

Chat/IRC

  • Chat is available in the Adobe Connect meeting room (see above).
  • A backchannel meta-discussion during the meeting also occurs on IRC.

 

Agenda

  • Quickly review previous meeting minutes (5 min)
  • Platform 2.0 Planning
  • Review next meeting agenda

Minutes

 

OpenMRS Developers Forum 2016-01-14
Attendees
  • Burke
  • Paul Biondich
  • Michael Downey
  • Rafal Korytkowski
  • Dominic Surrao
  • Darius Jazayeri
  • pralay
  • Mayank Sharma
  • Daniel Kayiwa
  • Wyclif Luyima
  • James deGraft-Johnson
  • Jamie Thomas
  • Skype Caller
Agenda & Notes
  • Platform 2.0 planning
  • Alpha has been tagged
  • There is a repo & project for the Platform on JIRA:
  • 80 database changes in Platform 2.0
  • Finding diffs between REST module and 
  • Planning on Sprint starting tomorrow for remaining tickets
  • Need to be addressed separately:
  • We can chat on Talk or IRC to figure out what to do with this
  • Darius will follow up on this
  • OWA module inclusion
  • Needs to be aligned with Platform 2.0 changes
  • Staging and Testing
  • TODO: Burke & Darius will work with Help Desk to get int-platform and uat-platform running
  • Current Estimate for Beta
  • ~1 month (by or before 1 March)
  • 2 weeks for sprint
  • A week for testing
  • A week for coordination/releasing
  • CI Support/Maintenance
  • Ownership
  • Cintia has been a tremendous resource over the past year(s)
  • Some devs (who?) can make changes, but likely expect it's a task for somebody else
  • Automation
  • What tasks need to be done?
  • Defining the work
  • Create a JIRA project (e.g., CI) for outstanding CI tasks
  • TODO:
  • Burke will make a Talk topic ± Google Doc to brainstorm on improving CI for Platform 2.0 and other CI support for the community.
  • What needs to be done?
  • What are the priorities?
  • Where are the bottlenecks or areas of improvement?
  • Who should be doing the work?

TODOs

Outstanding TODOs  (${entries.size()} issues)

Summary Assignee Created Due
Loading...
Refresh

Create a TODO: http://go.openmrs.org/todo

Transcripts

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