What features do you think should be extracted out from OpenLMIS Core repository?

Hi there,

I’m trying to put together a backlog of technical tasks regarding improving internal quality of OpenLMIS. Here is a question: which features/functionalities in current 2.0 codebase do you think conceptually should not belong to “OpenLMIS Core” chunk and should be extracted out to its own codebase?

[Indicators of “not belong to core” might be (1) specific to one country’s need, and (2) different frequency of change.]

For example, the “report” module might be a candidate to be extracted to its own codebase?

Is there some conditional logic specific to a particular country implementation?

Can we come up to a list of these stuff?

···

Jeff Xiong
ThoughtWorks
+86 186 826 53819

Plus some thoughts:

  • Should sms and email modules be extracted out to their own codebases?
  • In order to extract sms/email, we might need extract a core domain as dependency first. Then the dependency structure might become something like: openlmis-web => openlmis-email => openlmis-core?
  • There are REST APIs in openlmis-web module, and there is rest-api module. Should they be consolidated?
···

On 16 October 2015 at 10:15, Jie Xiong jxiong@thoughtworks.com wrote:

Hi there,

I’m trying to put together a backlog of technical tasks regarding improving internal quality of OpenLMIS. Here is a question: which features/functionalities in current 2.0 codebase do you think conceptually should not belong to “OpenLMIS Core” chunk and should be extracted out to its own codebase?

[Indicators of “not belong to core” might be (1) specific to one country’s need, and (2) different frequency of change.]

For example, the “report” module might be a candidate to be extracted to its own codebase?

Is there some conditional logic specific to a particular country implementation?

Jeff Xiong
ThoughtWorks
+86 186 826 53819

Can we come up to a list of these stuff?

Jeff Xiong
ThoughtWorks
+86 186 826 53819