2021-04-29 Call 15 Working Group

21:00

Presentations

@Alessandro Domanico

Thanksgiving to the community and brief presentation

@Andrei Dodu and @Timur Mikhaylov presented themselves

21:15

Closing current sprint and open a new one

@Alessandro Domanico

The goal of the call was to focus on the next release. As Informatici Senza Frontiere (in short ISF) we need to plan resources and efforts, so we need first of all to reach a milestone, that we identified as the release 1.11, which has been waiting for a quite while now. Of course we will share thoughts about the future, but since we are very close to the goal, we focused on the definition of the “final” sprint, trying to define an indicative release date, based on the issues we want and we DO NOT want to include. And then, as usual, we will try to make things go ahead as planned.

We closed Sprint n.5 and we opened a new Sprint n.6 - “Release v1.11 (Step 2)”. All the participants has been invited to look at the open issues' list.

As suggested by @miz and @David B Malkovsky we decided to:

• remove from the sprint OP-312 (Telemetry)

• include in the sprint a number of bugs directly connected to release 1.11

• include OP-483 and OP-484

Indicative date of the release (Sprint end) has been set for June 2021, and we will plan a mid-term call check.

22:15

React Frontend “ui”

@Henrique de Almeida @Alessandro Falezza

Henrique and Alessandro Falezza presented the ongoing developments of the new “ui” which issues are enclosed in a dedicated kanban
https://openhospital.atlassian.net/secure/RapidBoard.jspa?rapidView=5

There have included localization using i18next javascript liberary and Transifex and developed a number of components for some pages. They pointed out that, although the “ui” prototype can call the current “api”, they are currently testing against mocked APIs.

22:30

Community

@Emerson Castaneda

Emerson pointed out that it would be advisable to define clear a roadmap for the future components “api” and “ui”, not only in terms of issues to be done, but also in terms of amount of effort to put on each component (e.g. 10% on gui, 20% on core, 40% on api, 30% on ui) this also for the sake of the community cohesiveness, because in several months we have seen leaving some devs.

Moreover, last but not least, it is higly missing any channel of communication with the end user, in a way where we can receive their feedback and to understand where to focus

22:45

Community

@Alessandro Domanico

The cohesiveness of the community is something very hard to achieve in a small opensource community like the one of Open Hospital, mostly because it is not possibile to assure any effort in any specific direction (most devs develop what they feel to) and the current meeting was exactly a temptative to focus the community on a number of issues (the Sprint) that as community we identify as the priority to move forward in the shared overall roadmap, keeping in mind that anyway it is physiological that contributors step in and step out in the project lifespan.

After release v1.11 will be more than possible to plan a dedicated meeting for whom interested in “api” and “ui” developments only and to better define the next “bricks”, since we already have a number of issues just waiting for that (Spring5, adoption of java.time.*, the “ui” alpga release, and so on)

The typical end user of Open Hospital software is generally offline and non tech-aware to report bus or open issues, but an official channel is actually in place on the official website (Contact Form) where we receive mostly info requests and installation instructions.

We all agree that this channel must be improved and @Tsognong Fidèle suggested the use of Jira Issue Collector, that it has been added as option in the dedicated page UI - End User feedback technology where @everyone is warmly invited to contribute.

23:00

Patient Monitoring Solution

@Timur Mikhaylov

Timur presented a patient monitoring solution based on image recognition using mobile device that could be integrated in Open Hospital.

The participants recognized the importance and appliance of the proposed solution for Open Hospital.

We opened a dedicated decision page Patient monitoring with home devices to collect information and discuss the best way to do that.