2020-01-29 Call 9 Working Group

What you see and what you do?

All

Each participant shortly introduced *self and explained what he/she has done since last call and how he/she feels about the project.

All participant agreed that work with the project has been easied by well documented issues. Therefore we invited all participant and dev to help us in documenting event better the future ones.

Last Sprint

@Alessandro Domanico

We had a look to the sprint graph and explained how to read it and what we understand out of it. Briefly we have too plan much less workload for the team, in order to achieve goals in a steady way. Much less workload has been identified as 1-2days/week with sprints of 3-weeks lenght.

Roadmap

@Alessandro Domanico

We briefly discussed the roadmap from OH1.9 → OH2.0 meant as, briefly, a release joining together “core” + “api” + “gui” + “ui” + “doc” in a single package (note: the “ui” will not cover 100% of the “gui” for the first several months):

• The REST API service OP-6: Implement the new REST APIDone

• To finalize the Exception Handling pattern OP-127: Improve Exceptions HandlingDone

• To link “ui” with “api” for at least Patient’s Search and Registration

• To mount all pieces together with a future release OP-159: New Open Hospital EXPERIMENTAL packageDone

Until these collage is not possibile, we’ll continue with minor releases, like 1.9.x (or 1.x in case of DB changes)

Next Sprint

All

We defined the new sprint (already started) for the coming month: it will last for 3-weeks so it will finish 1 week before the next planned call (end of February)

Reactions and suggestions

All

We agreed that some work needs to be done before the version OH2.0, especially on the “ui” side, for which it would be better to have a specific call with whom involved on that side @Riccardo Costa @Henrique de Almeida @Niccolò Pasquetto

We also talked about different paths the application could take in the next future, like making the “gui” to call the new “api” instead of using core’s managers; this would unpair all the components and it could be achieved by code generation through script @Antonio Verni said.