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

Date

05/23/2013

How to Join

Click here for information about joining the meeting in person or remotely.

 

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)
  • Getting to Module Repository 2.0
  • After-action review & next week's agenda (5 min)

In Attendance

  • You

Minutes

View at notes.openmrs.org

Developers Forum 2013-05-23
Recording - 
Agenda
  • Getting to Module Repo 2.0
Attendees
  • Wyclif Luyima
  • Roger Friedman
  • Michael Downey
  • Burke Mamlin
  • Jeremy Keiper
  • Nyoman Ribeka
  • Zhaslan Doschanov
  • Daniel Kayiwa
  • Ryan Yates
  • Sri Maurya Kummamuru
  • Saptarshi Purkayastha
  • Paul Biondich
  • Lauren Stanisic
  • Filip Spiridonov
  • Leonjeru
Minutes
  • Last week:
  • TODO compile "community-supported" (define?) modules and list of resopnsible parties -- Burke & Darius
  • Module repository future
  • History
  • Still using bwolfe's original modrepo that was a first attempt at offering modules for downloads, basic statistics, RSS feed, integration with OpenMRS to download through web UI
  • Concerns
  • Missing things ...
  • No compatibility matrix between modules and OpenMRS versions
  • Can't determine popularity, support, recency of modules easily (or at all)
  • Can't see dependencies/requirements of modules easily from current version (unless they're written out in the description)
  • Any screenshots are currently hidden behind a link, no video demos, etc.
  • Search is only by name
  • No tagging
  • Lacks filtering
  • Requirements
  • Name
  • Description
  • Author/owner
  • * Support level
  • * Links to source, documentation
  • * Version Compatibility
  • Module ID
  • OpenMRS ID compatibility is a plus
  • Being able to see our modules (anyone should be able to submit modules)
  • Seeing download statistics
  • Search by name
  • RSS feed (of what content?)
  • Works with OpenMRS (install from application) ***important
  • * Tagging
  • * Rating & Reviews (version-based)
  • * Version compatibility with OpenMRS
  • * Screenshots
  • * Logo
  • Support information (info on how to get support for a given module)
  • * Deploy to repo as part of release process (e.g. maven)
  • Get to old versions
  • Module "collections" or "sets" recommended by people? (i.e. download modules from this specific list to achieve X or do Y)
  • Alternatives
  • Saptarshi is currently customizing Zamboni for use at DHIS2.
  • Elliott Williams is also available and willing to assist with Python work
  • Need a post-mortem on why the 2012 attempt failed
  • Approach:
  • Assemble a team: Ryan Yates, Saptarshi, Elliott, Jer?, Steve Githens?
  • Evaluate Machary's fork (2012) vs. the new developments (via Saptarshi)
  • Re-fork as necessary, customize, sandbox deployment, test
  • Build OpenMRS hooks and any other missing requirements
  • Upgrade/improve the existing OpenMRS module repository application
  • Pro's: Path of least resistance
  • Downside: Resource usage, not a scripted/agile environment, UI looks/feels 20th-century
  • Create new "Proprietary" (OpenMRS-made) modrepo
  • Grails?
  • Do nothing
  • Comments from Darius (offline):
  • the current state of the module repository hurts us in a lot of ways
  • It would surely be nice to use some other existing software product for this, but I have no confidence in our ability to push this through
  • Surely there are some features (e.g. version compatibility charts, commenting and/or rating) that would be helpful and would be easy to just go ahead and implement.
  • So my strong vote would be to determine one or two valuable features, and just implement them in the current module repository codebase, and do this soon.
  • What doesn't work
  • No easy way to tell which modules are compatible with which versions of OpenMRS
  • Not easy to tell which modules are popular/robust vs. unsupported
  • What does work 
  •  (the notes are above not here)
  • TODO:
  • Team: Saptarshi, Ryan, ElliotSteve Githens?, Jer?, Downey, all other comers
  • Fork AMOZamboni into OpenMRS organization

TODOs

Loading

Outstanding TODOs (0 issues)

Summary Assignee Created Due

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

Transcripts

  • Backchannel IRC transcript
  • Audio recording of the call: Listen online or download - available after the meeting
  • No labels