Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • 2014-03-20 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

 

By Browser

By telephone

  • US telephone number: +1 201.479.2627

 

Agenda

 

  • Quickly review previous meeting minutes (5 min)
    • OpenMRS Hackathons (reviewing past hackathons, plans for new ones)
  • After-action review & next week's agenda (5 min)

In Attendance

  • You

Minutes

View at notes.openmrs.org

In Attendance
  • Kesha Shah
  • Jeremy Keiper
  • I Nyoman Winardi Ribeka Pratihana
  • Wyclif Luyima
  • Burke Mamlin
  • Ryan Yates
  • Elliott Williams
  • Daniel Kayiwa
  • kushal
  • VaibhavAgarwal
  • Chris Power
  • Darius Jazayeri
  • aniketha
  • Alexis Duque
  • Milinda Premadasa
  • suraj
  • Sashrika
  • Lukas Breitwieser
  • ayuk etta
Agenda
  • Quickly review previous meeting minutes (5 min)
  • OpenMRS Hackathons (reviewing past hackathons, plans for new ones)
  • After-action review & next week's agenda (5 min)
Notes
  • Quickly review previous meeting minutes (5 min)
  • TODO: Burke will get PIH presentation from Mike added to the wiki page
  • No further comments
  • OpenMRS Hackathons (reviewing past hackathons, plans for new ones)
  • Recommended by Chris Power; expanded to talk about tools, etc
How do we get development done?  OpenMRS as a community ... current impression.
Values/Mission/Goals
  • Try to be driven by implementation needs
  • Wanna have fun
  • High quality code
  • Fast turnaround (never more than 3 years between releases)
  • "Engage the world"
  • Road Map?!?
  • TODO: Burke & Darius to clean this up
Roles
  • We have core developers and "people on the outside"
  • "implementation developers"
  • Working on modules
  • Adapting core code (e.g., via implementation-specific modules)
  • Looking for opportunities to leverage community modules
  • Not always clear how to collaborate without losing efficiency
  • Not always clear on how to use resources
  • Sometimes wear a "community" hat and support community modules
  • RFE, reporting, idgen, HFE, etc.
  • Often with insanely tight timeliness
  • "community developers"
  • "community groups of developers"
  • We've seen these form in Germany, Australia, etc.
  • "philanthropic organizations"
  • e.g. ThoughtWorks, random universities / schools
  • Need a quick way to donate a chunk of high quality developer time
  • Full committers, Partial Committers, Module/Repo Owners
  • Full committers can work on anything
  • Partial committers can change anything, but are expected to focus on their particular area/repo and not push to things they are not involved with
  • Module/Repo Owners tend to be the go-to person for a particular module/repo and are typically the lead for the associated JIRA project
Tools/Approaches
  • Sprints
  • Not always helpful to implementations (timing, ability to participate, ...)
  • Community Development Swim Lane
  • Helping n00bs
  • Tends to do the "non-sprint" stuff
  • Design
  • Design forums
  • Occassional "idea" wiki pages
  • Rare hackathons
  • Small group spend a focused amount of time (e.g., 1-3 days) on a focused topic
  • OMRS13 hackathon was great
  • What are ways we can do better with them?
  • TODO: Start having more hackathons
  • Explore different types
  • Contest approach
  • Education approach
  • Pile-On approach (getting a pile of pre-defined work done quickly)
  • "Virtual" online
  • ...
  • Need projects/targets available for folks
  • Try to have one per quarter
  • Rare spikes
  • Usually a single developer spends 1-2 days on answering a particular question, often with throw-away code
  • Projects
  • Mentored projects (GSoC)
  • Non-mentored projects
  • Testing / Deployment
  • What I mean is ...
  • Unit tests
  • Integration tests; should be just as important to new development as unit tests
  • How can a new dev jump into testing?
  • Training / Mentoring
  • Meetup/Hangout (like-minded people, chance to get an answer face-to-face)
  • OpenMRS University
  • Regional Meetups
  • Formal training
  • Paired Programming
  • Documentation
  • GSoC
  • SDK
  • After-action review & next week's agenda (5 min)

TODOs

Outstanding TODOs  (${entries.size()} issues)

Summary Assignee Created Due
Loading...
Refresh

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