Date
Participants
Goals
Agenda:
Next version v1.10
API work in progress: what's next
servers started in the new 2.0
concurrency between GUI and UI
Retrospective and next Sprint
OH WebSite
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
21:00 | Presentation | 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 https://github.com/informatici/openhospital-api/pull/23. 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 | 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 https://openhospital.atlassian.net/browse/OP-108 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 | We discussed the - OP-159Getting issue details... STATUS 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. |