2020-06-12 Call 13 Working Group

21:00

New version v1.10.0 and next version (tag 1.11 on Jira)

Alessandro Domanico

The new version 1.10 has been released on 4th of June 2020, it has many improvements and new features and it accomplished the epic “First Release Vezo (Madagascar)”. We are anyway ready with many tasks already done and others already under development that will be included in the next version 1.11 (see the list here). It will be very soon released a 1.11-pre-release for the epic “First Release Kidane Mehret Project (Adwa)” but most probably the 1.11 release will be done in late September.

Retrospective and next Sprint

Alessandro Domanico
Paolo Viotti Emerson Castaneda

The Sprint has been finally closed (after 71days) and a retrospective is available at this link. Briefly can be summarized with the Start/Stop/Keep doing schema in the end of the report.

Next Sprint will include previous uncomplished tasks and the epic “First Release Kidane Mehret Project (Adwa)” (almost done).

Decisions Logs and Actions logs

Alessandro Domanico

Uni2grow Cameroun

Very important for the small teams that are supporting the project, like Intesys and Uni2grow Cameroun, is to costantly have a look to the main Action Log and Decision Log pages to either check what was decided in the last call and and at the same time to push forward the discussions on the overal roadmap. Then the the issues' filter Next Version helps in check what are the open issues to be solved first and last but not least, of course, the Current Sprint (if any).

The new developbranch and contributions' schema

Alessandro Domanico

Paolo Viotti

With the new release 1.10 we have (finally) adopted the Maven Standard Layout on the core and gui components (ex OP-181) and a new branching schema for the contributions, with a new branch develop (default), that will be documented in the WiKi.

Of course all current developments on master branch should be rebased on the new develop one.

React UI: where we are?

Henrique de Almeida

Henrique showed his own work on the UX on his repository that starts from scratch the developments, showing a BDD (business design development) using Cypress with a better and more clean organized code. He will work on it a little more before the next call about “ui” (last one was on “2020-05-14 Call "ui" n.2”).

The encouragement is to give us a sign-off very soon in order to set free the community on concrete tasks to be developed.

Users' permissions schema

Alessandro Domanico

One of the nicest topic in the Decision Log page is the one concerning the actual users' permission schema and its improvement, already gratly analysed by Paurav Munshi on the related page. This task will impact also the UI, so we are ager to take charge of this tasks.

We should also verify if the actual Versioning schema is functional and enough understandable by the developers, normally focused on the single component with its own version, and end-user, obviously dealing with only one version at time.

End-User updates

Alessandro Domanico

Paolo Viotti

With the the new distribution workflow (note: Travis CI has been replaced with GitHub Actions on core, it should be done into gui also) and this Sprint schema we are going to release very fast version after version, so it might be needed to better document the update process for the End-User between two different version (e.g. 1.9.1 → 1.11.0).

This is already documented in the Admin Manual, but should probably improved a little and also to endorse newer version of MySQL Server (by updating and using the OP-166)

For the portable version we should probably be already ok with OP-128 and OP-136 (in memory DB) so also the portable could be freed-up of more than 100MB

End-User ticketing

Alessandro Domanico

At the moment we have too many end-user “end points” (GitHub, OH-Website, ISF-Website, Jira and community e-mail) so it is very difficult to have a standard way to support either user like also new developers (CONTRIBUTING.md is a bit hidden because only on the main repository). So we are thinking to enable OpenHospital Service Desk here on Jira so we could redirect here all the requests and also directly convert them into Jira issues (if needed).

End-User demo data

Alessandro Domanico

Some users and PM (Project Managers) often request “demo data”. This is possible to achieve by creating from scratch the DB by using the create_all_demo.sql script, but this is an old method and also burdersome to maintain. Hence a new task OP-223 has been created for this goal.

Adoption of Java8 or greater

Alessandro Domanico

Since new release 1.10 we are eager to bump to Java8 (LTS) as minimum requirement almost pain-free at this stage (1.9 would introduce too many changes to the code) unless for those “native library dependent” features that we need to upgrade or discontinue for a while. Ref. https://openhospital.atlassian.net/browse/OP-108