2020-05-06 Call 12 Working Group

21:00

Presentation

@Alessandro Domanico

Brief greetings and presentations

21:15

Sprint

@Alessandro Domanico @All

The ongoing Sprint was not yet closed because the main issue in it (OP-6) is not yet completed due to the long discussion and sharing about the pattern to adopt, that anyway now is somehow defined you can find it here Rest API Controller (pattern) and at the moment implemented here OP-6 new proposed pattern by mwithi · Pull Request #23 · informatici/openhospital-api.

So we agreed to leave this Sprint open in order to finish at least OP-6 and its subtasks.

@Emerson Castaneda proposed to split major tasks into smaller ones in order to enable more people to work on them and also increase engagement.

The same Sprint, called “1.10 + API beta” includes also realeas 1.10 that is yet to come and under review. It will be finished soon and also the Standard Maven Layout will applied to the “core” and “gui” components before the release. This will affect some works on some issues but will not impact at all on the “api” component.

21:30

API Tests

@Emerson Castaneda @Vito Romano

We agreed that testing are affected by the Spring configuration and that need to be split into smaller tasks. @Emerson Castaneda has worked on a Spring configuration that works but it is based on Spring Boot v2 and so on Java8+ and he will share it for review.

We pointed out that compliance with Java6 is blocking the developments and we need to abandon it as soon as possible. We recall that one step in this direction is already started with discussion on OP-108: Create openhospital-cliTo Do whose aim is to isolate components that need compliance, but also we agreed that for the new coming version’s sake some parts can/should be discountinued.

22:00

New Distribution

@Uni2grow Cameroun @Paolo Viotti

We discussed the OP-159: New Open Hospital EXPERIMENTAL packageDone reminding that both “gui” and “ui” will be needed in the first period so we have to find a compromise between “application deployment” and “ease of use” by the end-user.

@Paolo Viotti pointed out that both Spring Boot server and MySQL server we are distributing are old and may be not safe for the portable version, that anyway is meant for the product evaluation and its use is discouraged in a production environment.

@Uni2grow Cameroun remarked that “gui” is too old and users would benefit a lot by the new “ui” when it will be ready

22:30

New “ui”

@Henrique de Almeida

New mockups have been published in the related discussion page UX - First steps (outdated) and it will be subject of a dedicated call.

Some other related discussion pages are still open and no decisions have been taken yet, so most of them will be taken in the next call.

Very important is to start coding, thus this is not very easy without documented issues.

22:45

OH Website

@Riccardo Costa @Paolo Viotti

We discussed the need ot updating the OH Website in order to facilitate developers in finding key informations about the project.

We agreed that the actual WordPress is not fitting the needs but the main problem is that nobody is actually working on it, also due to the fact that it’s kind of “webie” actors that a the moment are missing in this working group.

@Paolo Viotti proposed a Jekyll version of the website that can be hosted on GitHub as well and updated via push and automatic deployment. We agreed that this kind of solution would better fit our way of work and maybe narrow down the whole process, but we need a kind of decision.

@Alessandro Domanico pointed out that in any case, whereas WP or Jekyll, we need an accountable person for this activity.