2022-06-14 Call 16 Working group

Date

Jun 14, 2022

Participants

@Alessandro Domanico
@Andrei Dodu
@Arnaud FOFOU
@Claudio Rosazza
@David B Malkovsky
@Emerson Castaneda
@miz
@Nicole Lazzeri
@Paolo Viotti
@Steve Tsala (Unlicensed)

Goals

To share Open Hospital roadmap for 2022

Discussion topics

Time	Item	Presenter	Notes

Time	Item	Presenter	Notes
19:00 CEST	Presentations	@Alessandro Domanico	Brief presentation of all attendees
19:10	Latest News	@Alessandro Domanico	Latests news are: Application little restyling (graphics, logo, gui), thanks to @David B Malkovsky Website little restyling (pages, links, language, etc) thanks to @miz Open Hospital roadmap (the current stack, with API and UI under development) What is missing is a good documentation about new projects and installations, for which we’ll plan a space in the website and we kindly ask to document new projects, as a very important impact evidence of our work. Among these there are projects in Madagascar, updates from Ethiopia, project in RCA and several installations in Cameroon.
19:20	3 New Topics	@Alessandro Domanico	Presented 3 new “Epic” issues: GDPR and SEC: topic DONE, and issues available Patient Portal: discussion IN PROGRESS UI Dashboard: discussion IN PROGRESS For the discussion IN PROGRESS we warmly invite the community to contribute with suggestions for a final decision.
19:40	UI development	@Alessandro Domanico @Steve Tsala (Unlicensed)	We talked about the need of reducing the confusion on the current UI development by doing the required (little) changes on “core” and “api” into official “informatici” repositories (like the “ui” is) rather than keeping them on the fork of “intesys”; this would also enable the community to check the PRs and to test the results. The topic will be discussed internally with the @Uni2grow Cameroun and User Interface teams.
19:50	Open Debate	@all	We discussed how to contribute to the project (the fork-pr schema), the testing schema and actual test coverage, the next version 1.12.0 issues, and the community tools (Slack and ML). @miz pointed out the we have also a very important “topic” of the project that is the users support, that requires a lot of time and also is a tangible evidence of the application usage and its impact. We will try to better organize this part in order to enable also the community to contribute offering support.
20:25	Closing	@Alessandro Domanico	We aim to have another meeting within 2-3 months or whenever is required by a specific topic that may rise on the community channels.

Action items

@Emerson Castaneda to share the actual tests coverage. We can use the already existing page Tests naming convention for this topic.

@David B Malkovsky to share the ideas and suggestions for a general tests suite principles. We can use the already existing page Tests naming convention for this topic.

@Steve Tsala (Unlicensed) to discuss the shifting of “core” and “api” development from Intesys fork to official Informatici repository in order to reduce the confusion on the current UI development

@Alessandro Domanico to disable Jira integrations for new issues on all Slack channels except #jira one, in order to reduce the workspace verbosity. Jun 15, 2022

@Alessandro Domanico@Nicole Lazzeri@Uni2grow Cameroun@Claudio Rosazza to share description about projects stories

@miz to think about a section in the website where to share projects stories

@Alessandro Domanico@miz to think how to enable community for support

Decisions

@everyone To contribute to following discussion pages: