2016-05-31 Meeting notes

Owned by Josh Zamor
Last updated: Jun 14, 2016 by Rich Magnuson (Deactivated)

Date

4-4:50pm PDT

7-7:50pm EDT

1 June 2016 7-7:50am Beijing / CST

http://fuze.me/30957362

Join by phone:
Dial phone number and enter the Meeting ID (30957362) when prompted
- Toll: +1 201-479-4595

Attendees

Goals

Notes

Pengfei demonstrated use of a document DB (MongoDB) in conjunction with Postgres to store extra data. 

  • Worked well, but unclear on whether this is preferred to JSON data type approach

 

Rich outlined the re-architecture project effort, including the engagement with Soldevelo to accelerate the effort.  A brief description of the process is here, and all work is tracked in JIRA.  Josh outlined the purpose of the new v3 repositories.

 

Tech committee’s decision making process.  How can tech decisions be made in a timely manner?

Darius:  OpenMRS model has a chief architect role, along with “lieutenants” in component areas – these roles make the final decisions.  This doesn’t seem like a good model for OpenLMIS.  If consensus it not achieved, perhaps a vote?  A vote among the tech committee might be better than amongst contributors at this point.

Jeff:  we seem reach consensus most of the time.

Darius:  What is an example of a recent decision?

Josh:  The question on the OpenLMIS repository.  Has been out there for some time, but no input other than from Darius and Rich.

Darius:  consider restating and putting a time limit on it?

All:  need to revisit this topic, especially with Elias/JSI present for input.

 

(not mentioned:  Fisheye, Crucible and Zephyr are now installed on OpenLMIS’ JIRA.  Fisheye is used for more insight on the code repositories, Crucible we may trial for code review (it came free with Fisheye), and Zephyr is for basic test case management.  Check ‘em out and let us know what you think)

Action items

OpenLMIS: the global initiative for powerful LMIS software