How does this project fit with the strategy?
Burke and others describe the strategy in https://talk.openmrs.org/t/an-amazing-future-for-openmrs/22328
Our decision making process is an RFC (Request For Comments). All major decisions are made through github pull requests where anyone can comment. See https://github.com/openmrs/openmrs-rfc-frontend.
Why are we doing this?
We are modernizing OpenMRS' frontend with a few goals:
Impact of this problem
All distributions will have the option to use a new OpenMRS frontend and share code with other distributions.
How do we judge success?
|Do we create something? Is it used? By how many groups? Does it work well? How long before we have to rewrite it again?|
What are possible solutions?
|SPA, client rendering, ES modules, import maps, single-spa applications and parcels|
What do we already know?
What do we need to answer?
Ready to make it
What are we doing?
Why will a customer want this?
Visualize the solution
Scale and scope
Copyright © 2016 Atlassian
This work is licensed under a Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License.