2020-10-07 Call 14 Working Group

21:00

Presentations

All

Participants introduced themselves

21:15

The main project roadmap

Alessandro Domanico

We went through the OpenHospital roadmap, since version 1.8.4 (monolithic, hosted on SourceForge) to the 1.10.0 (multi-component, hosted on GitHub) and its reduced technical debt, thanks to the hard community work, and by finalizing the two Epics goals “Vezo” and “Adwa”.

21:45

v1.11.0

All

What is missing to release 1.11.0?

We briefly discussed the current Sprint n.5 is about to be closed with its OP-06 almost done David B Malkovsky and Emerson Castaneda are working on it.

After that we will open Sprint n.6, and the duration will be sized on the previous 3 sprint velocity, for a maximum of 2 months. This Sprint will include:

• The 18 issues already marked as v1.11.0
  Highlights:

  • Java8 (OP-224) Tomasz Tokarczyk

  • Report Java6 discontinuity (OP-228) Alessandro Domanico

• Spring5 (OP-101) and Date & Time Typing (OP-282) Paolo Viotti

• More?

  • File-based DB for portable version

  • Automatic announcer (script)

  • Renovated “gui” (look&feel)

22:30

React Frontend “ui”

Henrique de Almeida Riccardo Costa

Henrique and Riccardo 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

For its developments the API have been updated to the latet OP-6 branch and are available online at https://www.open-hospital.org/oh-api/swagger-ui.html

For developing purposes it is suggested to disable web-security in the browser (see example for Chrome). In the future the back-end Spring Security should be adjusted https://openhospital.atlassian.net/browse/OP-306

22:50

www.open-hospital.org

Paolo Viotti Alessandro Domanico

The actual website is not updated since many months, probably to a lack of time and/or WordPress awared people. Also, at the moment it is missing an accountable person for it. A proposal could be to move the website under a repository and to have a minimum (or eventually complex) website on GitHub pages which code would be hosted as any other project's code (example here and here) and to manage changes with issues and PR; this would transfer the website ownership back to the project's opensource community itself.

The group has raised doubts about segregations of competencies and roles between project coding and project marketing.