We’ve started our first OpenLMIS 3.0 sprint this week. Following the ideas and decisions from
design week in late March, the team dived deeper into the details and came up with a high-level architecture as described
here. As we have much to discover and decide, the main focus of this 2-week sprint is to begin laying the foundation for the overall structure and development environment:
start with the overall structure by creating the *Service Template*
test ideas to extend schema (“extra data”) via JSON, “thin tables” and possibly a document database
potentially spiking on creating Docker images for development and deployment. We have lots of questions on how to handle debugging, logging, etc. If you have expertise in this area, we’d love your help!
Better organize the backlog (see below)
Any code we produce will be in new repos in the
OpenLMIS github organization.
Another sprint goal is to organize the backlog. The design week produced over 150 stories, which were bulk imported into JIRA , and assigned releases of MVP (think beta), 3.0, 3.1 and 3.2. These will need more detail and likely further breakdown, prioritization, etc. To view them, access the OpenLMIS General project and search for issues where
Fix Version == MVP, 3.0, etc.
Thanks - Rich