Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Design for Supplying Partner scenario - tech committee

Description

In the tech committee meeting a real scenario for the OpenLMIS community was discussed regarding how the version 3 architecture would address the scenario to avoid/minimize code-forks.

This is a candidate for and to pair on.

Acceptance:

  • scenario's description is accurate and detailed enough (needs approval)

  • design document(s) and narrative propose what components of the architecture would be used, where (approx), and to what effect.

  • design and narrative will be presented and discussed at next committee call (Nov 8)

QAlity Plus - Test Management

Checklists

Activity

Josh Zamor 
November 22, 2016 at 7:49 PM

Thanks, meeting notes have been added and I added a link back to them from the scenario document in the comments.

Brandon Bowersox-Johnson 
November 22, 2016 at 7:17 PM

Here is the scenario: https://openlmis.atlassian.net/wiki/display/OP/Requisition+Splitting+-+Extension+Scenario+Analysis

I agree that we can mark this ticket as done. I filed two follow-up tickets for the UI extension scenario and also for adding in a diagram (to identify git repos, CI/CD jobs, Maven/Docker Hub pieces) as the tech committee asked today: and OLMIS-1407.

Also, when you write up meeting notes from the tech committee, you may want to edit the scenario wiki page to link to those meeting notes.

Josh Zamor 
November 22, 2016 at 7:12 PM

Work completed:

From this arose a desire to:

  • show how extensions would be packaged, deployed, versioned, etc (git repos, dockerhub repos, jenkins jobs, etc)

  • have the UI discussion which needs to start with finding the right "line in the sand" for extending v. fork/replace.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Sprint

Fix versions

Due date

Priority

Parent

Time Assistant

Created October 26, 2016 at 7:38 PM
Updated March 1, 2017 at 8:36 PM
Resolved November 22, 2016 at 7:18 PM