Child pages
  • 2014-10-30 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)
  • OpenMRS 2.1 retrospective
  • Review next meeting agenda

Minutes

View at notes.openmrs.org

 

Attendees
  • Burke Mamlin
  • Ryan Yates
  • Karl Wurst
  • Darius Jazayeri
  • Daniel Kayiwa
  • Mike Seaton
  • Paul Biondich
  • Sara Armson
  • Ada
  • Win
  • Sap Purkayatha
Agenda/Notes
OpenMRS 2.1 Retrospective
  • What we thought would happen
  • We would get 2.1 released in September 2014
  • We planned it would contain allergies, form entry hooks, retrospective data entry, ad-hoc analysis tool, reporting, improved demo data, and a few other things
  • What actually happened
  • We are really happy that we released it (pretty much) on time.  Earlier in 2014, the OpenMRS Developer Community put some stakes in the ground, saying that we wanted to release OpenMRS twice a year, in March and September.
  • We ended up eliminating most features from 2.1 (except allergies, form entry hooks, improved demo data) in order to get it out in time.
  • Had not organized sprints or dedicated core developer time toward meeting the release time
  • We might have a Darius Dependency for OpenMRS releases
  • Items that needed analysis were less likely to happen
  • Items that were desirable for implementations (e.g., retrospective order entry) but not by implementations with time or resources to do the work were unlikely to get done 
  • We were digging ourselves out of getting 1.10 (basic Order Entry API) and 1.11 out.
  •  
  • What we can do better
  • The Road Map is what people have done or are stepping up to do and not a list of things that we plan to go recruit developers to do for the community.
  • This probably needs to be combined with some development strategy
  • Design-to-ready-for-work-ticket is a bottle neck
  • We need to build up a BA team and/or product owner team
  • Implementations with resources have BAs, but those BAs are focused on their implementation's needs
  • Need to identify a release manager for releases 4+ months ahead of time
  • Need to define what that thing is from which OpenMRS (reference application), PIH, and Bahmni (and hopefully soon, KenyaEMR) are built.
  • OpenMRS Platform + UI Framework + App Framework + bunch of modules that make an OpenMRS distribution possible.
  • Can we make the reference application this thing – i.e., making it really easy to "peel off" the parts that make the reference application the OpenMRS distribution... or make the reference application the base system with the option to opt-in for the OpenMRS Distribution magic
What does "OpenMRS Core Team" mean?  How does somenone join or leave the core team?
  • People that are either paid to spend a significant portion of their time on OpenMRS-specific work or, through their ability to volunteer, are predictably and reliably spending a significant portion of their time on OpenMRS-specific 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)

 

 

  • No labels