Child pages
  • 2016-06-09 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)
  • Translating OpenMRS, Platform 2.0 release retrospective
  • Review next meeting agenda

Minutes

Attendees
  • Sebastian
  • Darius
  • James
  • Daniel
  • Willa
  • Burke
Agenda
  • Translating OpenMRS
  • Platform 2.0 release retrospective: how we can make release managers better?
Notes
Should we be pulling in translations as they are created and modules are being built? Or should we pull them in during the release process?
=> pull these in quickly (as they happen, or daily), because this is conceptually just like background synchronizing from Transifex to our git codebases
  • (translation changes "should" be just like any other code change, e.g. have a PR, but this is probably unworkable)
Platform 2.0 Release Process Review (Mayank)
  • Presentation
  • Reviewed current platform release process
  • Reviewed stats for Platform 2.0 contributions thru Alpha & Beta
  • Retrospective
  • Avoid long release time
  • Enthusiasm decreased over time with long release process
  • More public release planning
  • Leverage influx of GSoC students in early part of year
  • More automation/standardization of release process
  • Candidates for automation
  • Finding contributors
  • Find differences in database
  • Identifying tickets that are part of the release
  • Uploading artifacts to Nexus
  • Improve tracking & follow-ups
  • Improve release process documentation
  • It covers the "bringing things together"
  • Re-order the information to match actual worfklow
  • Document errors that may arise at various steps
  • Some short videos to cover the basic steps
  • More Sprints on release
  • Focus community development on release priorities
  • Next steps
  • Share slides
  • Schedule an "improvathon" (half-day) to act on Mayank's suggestions

 

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)