Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS »
Discussion: OpenMRS Talk »
Real-Time: IRC Chat

Resources

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)
  • Open Concepts Lab Subscription Module Showcase
  • Versioning Strategy
  • Review next meeting agenda

Minutes

OpenMRS Developers Forum 2015-08-06
Attendees
  • Burke Mamlin
  • Michael Downey
  • Darius Jazayeri
  • Ryan Yates
  • Wyclif Luyima
  • Tim ___
  • Karl Wurst
  • Tomasz Mueller
  • Willa
  • Sharon Varghese
  • Carolyn __
  • Rafal Korytkowski
  • Daniel Kayiwa
Agenda/Notes
  • Review last week TODOs
  • Dev stages
  • Technology radar
  • QA team accomplishments
  • QA team still is awesome
  • Open Concepts Lab Subscription Module Showcase
  • Versioning Strategy
  • Do we need (or will we need) a 1.12 or 1.13 release of the platform? If so, what's the strategy for getting it done if master contains platform 2.0?
  • If needed (only if needed), we would branch 1.12.x from 1.11.x and backport any changes needed from master to 1.12.x
  • How can we make our versioning _more_ confusing? It may get worse when the platform becomes 2.0 (and we're working on 2.4 atop 2.0?!?)
  • Suggestions
  • Stop calling anything just "OpenMRS"
  • "OpenMRS Core", or simply "Core", is the openmrs-core in github (basic API)
  • Just "Core"
  • "OpenMRS Platform", or simply "Platform", is the shared platform (currently API + web services), may evolve to include web framework components as well
  • Just "Platform"
  • Give the reference application a different/specific name – e.g., "OpenMRS Distribution 2.4" or "OpenMRS Reference Application 2.4"
  • Just "Reference Application"
  • MD: Don't use "OpenMRS" in the name because that's what confuses people (in reverse, "OpenMRS" vs. "OpenMRS Platform")
  • Consider automobile naming scheme:
  • "Ford Fusion", "Ford Focus", etc.
  • Ford is the make, "Fusion" or "Focus" is the model
  • Ford
  • Fusion
  • Focus
  • etc.
  • We need unique names name for:
  • Our community
  • Our platform software product
  • Our featured "distribution" product
  • Communication becomes: the OpenMRS "Reference Application 2.4 runs on Platform 2.0"
  • 2013 suggestion from Win Ribeka: "OpenMRS Samsara"
  • "There are only two hard things in Computer Science: cache invalidation and naming things." -- Phil Karlton
  • Next week preview

TODOs

Loading

Outstanding TODOs (0 issues)

Summary Assignee Created Due

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

Transcripts

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

 

 

  • No labels