Page Comparison

{composition-setup}{composition-setup}

Date

17/February/2011

How to Join Call

{toggle-cloak:id=how-to-join}

{cloak:id=how-to-join}

{cloak}

In Attendance

...

• Michael Downey
• Jeremy Keiper
• Ben Wolfe
• Dawn Seymour
• Wyclif Luyima
• Darius Jazayeri
• Daniel Kayiwa
• Sriskandarajah Suhothayan
• Former user (Deleted)
• Suranga Kasthurirathne
• Glen McCallum
• Mark Goodrich

Agenda

• Quickly review previous meeting minutes (5 mins)
• (first item) Release Manager Process (30 mins)
  • ?Being an OpenMRS Release Manager
  • ?Release Process
• 1.8 Beta 2 update (10 mins) 
• Patientmatching module followup? (10 mins)
• Darius to Demo new features in logic module (30 mins)(10 mins)
  • http://connect.openmrs.org/
• Darius to give 2.0 update (20 mins)
  • docs:PDF
• After-action review & next week's agenda (5 min)

...

real-time collaborative notes

1.8 update:
Wyclif:
Set to have the beta 2 to release friday. Will not include the 'intitialization wizard database copier ticket'.
Darius: working on multi-column index ticket. Will not be in 1.8 but instead in a module that can be done at any point.
Roger: please explain the module decision
Darius: Having it in a module allows impl to run it at any time.
Roger: I proposed having it as a liquibase in main line with precondition that if they have less than X observations.
Roger and Darius will take discussion offline
Burke: Do we need an RC?
Ben: Yes, but only if there aren't any changes in the beta

1.9 planning:
Reviewing tickets on roadmap.openmrs.org:
Multiple tickets are partly done.
concept mapping will be finally discussed today
Burke dislikes the 'documentation of interaction points with ancillary systems' ticket.
Paul: This ticket is largely for documentation. Some code exists, some doesn't. This is mostly for things like 'I have a lab integration system, how would I integrate?'. Would be nice ot have a web page for that
Darius: this might involve some code being written.
Diptanu: I can help contribute to that document. We use openmrs and other systems
Burke: I want at least something on a wiki page instead of a bunch of points on a call that are lost.
Shaun: is this a list of 'you should do this this and this' or is it a best practices?
Burke: Its more of a pointer to people that have done things
Burke: there is not '1 hammer' to solve everyone's needs

Stanford Hack-a-thon
A handful of student hackers will be working on openmrs tickets for 24 hours straight this weekend.
We need people to help them on irc/forum, especially overnight on Saturday Feb 12th

Concept Mapping Updates
concept mapping improvements for 1.9
Andy: We also need a derived table for exploding children/grandchildren/etc for speed improvements
Burke: We can do that later potentially
Andy: But if it is not usable with the speed improvements, its useless
Roger: concept map type might not need to be a user defined table
Burke: openmrs does not want to be an ontology management system. modules can add their own types.
Darius: using a table adds a lot of complexity
Burke: fair enough, but we shouldn't assume that the values are in X enum and will never have more
Roger: what about the open archetypes standard
Carl: We're working on that and the occ integration to share concepts
Roger: Andy has mapped his concepts in a snomed way. Is this data strucutre sufficient to handle OSA model. If not, is it possible to make somethign to handle both
Burke: it'd be nice to let other systems do what they do best, openmrs can just provide the basics
Roger: can some of this be in core vs a module?
Andy: The relationship type of tables can probably be a module
Andy: There could be entries in the refernece_term table that are not mapped to a concept yet.
Roger: translations are not possible in the term table
Andy: we weren't looking to create a dynamic translator here
Andy: do we want a source column in the term_map table?
Glen: what if the terms in the term_map are for two different source?
Darius: just join to term to get the source
Andy: how to know which rows in termp_map to delete when doing an update?
Glen: do a pattern matching on ... ____
Darius: terms have a unique id. Do term_maps have a code?
Andy/Glen: Yes, they probably do
Andy: could add a 'external_code' column to term_map' (TODO)
Darius: How to work if we add locale to reference_term (TODO)
Darius: How does this work if term_map has a code? (TODO)
Ben: can we rename concept_map to something more in line with concept references
Burke: concept_map ⇒ concept_reference_map
Jer/Roger: need some documentation on how this works with concrete examples
Roger: Darius' weight example is a good one to use

The "patientmatching" module tickets
Shaun: James will not be able to do all of the tickets, especially UI.
Darius: send an email to dev list with the tickets and the potential work involved

Release Manager Responsibilities
Paul: Bump this to next week? Needs to be first on the list next week
Darius: 5 min overview:
1) RM is the one to push users to finish tickets
2) RM follows up on tickets telling Darius someone to work on them
3) Picking tickets that go in the release
4) Making wiki page for release
5) Doing the release (packaging, etc)
Burke: how much time is involved (full time, part time, no time)
Paul: wants more of a wording on the page like 'just do this, its not hard, we'll help you"

Diptanu: is information available online? or on the ticket?
Ben: The wiki only has minor documentation

...

• Start time: 10:15

Review of todo's

• Most need to be deferred
• Stanford Hackathon didn't go too well this time due to lack of real-time/in-person support.
• Ben: In person support was very helpful (first year), Last year went OK, this year no support was available and they worked on something else

Release manager - 20 min

• Defer until anyone interested in the conversation is here?
• How to make people feel more comfortable
• Ben: May be fear of unknown time committment etc. Should we get Wyclif on video saying "it gets better"?
• Paul: Needs to be an "advertisement" for release manager every time a new release cycle starts up. Formal meeting of the interested parties to kick-off the process.
• Assumption: We want community volunteers to be involved in release process.
• Paul: Look at mozilla web site for a good example of reading about release process / release managers.
  • http://weblogs.mozillazine.org/asa/archives/007309.html
  • ?
• TODO: Ben will write an email from Paul as a call for potential release managers.
• TODO: Clean up the release manager role page on wiki to dispel misconceptions. (Expectations, different roles in the release process, what it is and is not, triaging, staying on top of issues, etc.) Provide a high-level overview of how releases come to be – not just a technical howto.
• TODO (future): Have a real-time meeting with volunteer release managers

1.8 Update - 20 min

• Wyclif: Well, the 1.8 beta 2 is out. We asked the implementations to try it out and report bugs. Spoke to AMPATH, PIH, James Arbaugh/HAS. In terms of tickets 1.8 development is fine and he personally has started on 1.9 coding.
• Jeremy: AMPATH has a test server ready to go, they need a snapshot before installing 1.8. He's found a few small things:
  • FormEntry module wasn't correct version
  • Schema issues for AMPATH to use
• TODO: Wyclif should talk to Hamish or Evan Waters at PIH for info about testing 1.8 there.
• Mark: PIH has done some testing on 1.8 beta 1 for their Haiti implementation. He wrote up a list of their issues (mostly related to PIH-specific modules rather than the beta). Doesn't think there were many 1.8 issues. Basic testing was done in US on Mark's test system using real (de-identified) data.
• TODO: Mark to provide feedback on his 1.8 findings to Wyclif et al.

OT: Uganda OpenMRS users - 5 min

• Daniel: Known installations in Uganda are using 1.2 and 1.5, for example.
• It would seem that the value proposition for upgrading (benefits vs. time/effort) are not enough for them to upgrade. They realize there's no "support" available.
• Ben: It could take a day or more to upgrade data from 1.2 to 1.7+.

Patient Matching project update (Shaun) - 5 min

• Need community's help for working on outstanding issues

Logic module feature demo (Darius) -

• Many cool new improvements.
• See http://openmrs.atlassian.net/wiki/display/docs/Logic+Module
• Logic now supports Groovy and Java
• Arden will be supported soon
• TODO: Darius to upload slides to wiki notes page and notify dev list

Side announcements

• Mark will be moving the MDRTB module
• Crucible is being moved over to OSUOSL. This will bring major speed improvements due to local (ok, well, a read-only nfs mount) indexing of svn and ganeti >> vmware

Outcomes

||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||

...