2015-07-30 Developers Forum

How to Join

 Click here to expand...


By Browser

By telephone

  • US telephone number: +1 201.479.2627



  • Quickly review previous meeting minutes (5 min)
  • Update on Dev Stages
  • Technology Radar
  • QA Team Accomplishments
  • Review next meeting agenda


View at notes.openmrs.org


OpenMRS Developers Forum 2015-07-30
Audio recording: https://goo.gl/7YdXPE
  • Ryan Yates /dev/null
  • Michael Downey /dev/null
  • Burke Mamlin /dev/5
  • Darius Jazayeri /dev/5
  • Tomasz Mueller
  • Yourself /dev/∞+
  • Natalia Płonka
  • Shaun Grannis /dev/null (??)
  • Tharunya Pati /dev/null
  • Daniel Kayiwa
  • Kaweesi Joseph
  • Ali Habib /dev/null
  • Tim
  • Paul
  • maany /dev/null
  • Maurya
Last Week Review
  • Demo on OpenSRP
  • No TODOs
Update on Dev Stages v.1.0 beta
  • /dev/null is starting point -- be here and interested
  • /dev/1 is the basic starting developer, IDE, read the docs, etc.
  • Currently a manual review process for promoting people "up the ranks" - this will change
  • Next Steps
  • Finish automating the moodle/quiz
  • TODO: @sunbiz finishing up badge-granting automation
  • move moodle onto an openmrs server
  • TODO: @burke need to schedule regular /dev/5 meetups to review
  • Questions/Comments
  • How are Dev Stages helping (communication, motivation, clarifying)?
  • How are Dev Stages hurting (confusion, ambiguity, don't fit non-devs)?
  • What updates/changes to Dev Stages would help most?
  • Paul: How do we want to handle multiple labels? can't someone be both a GSOC student and a /dev/2?
  • The label in talk is "title" under profile settings
  • Users must pick one
Technology Radar
  • Relevant to OpenMRS
  • Could be a major change to how we develop/deploy
  • What about creating an official Debian package?
  • Some implementations (e.g., PIH) have used debian packages for deployment/upgrade
  • OpenMRS Community has typically not been in the "last mile" – i.e., filling in all the content necessary to implement a system.
  • Let consumers of web services help define the tests we should be running
  • Does the QA team want to evaluate how we might start doing this and make suggestions?
  • Should we create a JIRA issue in the trunk project to ask someone to work on this?
  • For example: should we move our developers guide into a git repo?
  • GitHub would be more familiar to devs than the FLOSSmanuals platform, likely to get more changes/PR's
  • Combinations like GitHub + https://readthedocs.org/ are a great way to balance maintainability with readability/searchability
  • Avoid creating "DevOps" team separate from the development team
  • "silos" are bad (same with QA) ... ops & QA & others should serve and support all devs who work to improve deployment & testing
  • Darius: as far as DevOps goes, I don't think this point is very relevant to the way OpenMRS works.
  • Related: CoreOS?
  • Questions/Comments/Concerns
  • Consider packaging in something like a .deb file? (also .rpm?) Where would that leave our non-Linux friends?
  • VM images/Docker?
QA Team Accomplishments - Tomasz Mueller
  • When QA team started, there were ~5 UI tests done by developers
  • QA team create 78 test cases covering functionality (with a couple on deployment)
  • Used Zephyr plugin for JIRA
  • Switched to creating data for test as part of test
  • Still have problem with data being voided instead of purged
  • Team currently has Seven members
  • Special thanks to Ada Yeung, Yułia, and Pavlo!
  • Working with Admin UI Sprint to consider new test cases
Preview of Next Week



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