2015-08-06 Developers Forum
How to Join
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
Recording: https://goo.gl/oYJIIi
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
Transcripts
Audio recording of the call: Listen online or download (available after the meeting)