Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • progress status of tasks: Jira Tasks, GitHub tasks, Action page, Decision Page

  • New UI translations in React

  • Sprint towards the version 2.0 in January 2020

  • Sprints on the merge of the tasks developed and awaiting review (TO_BE_REVIEWED or DOC_REVIEW)

Discussion topics

Time

Item

Presenter

Notes

21:00

Custom version releases

Paolo Viotti Nicola Punzi

Nicola, who is working on a version of a project, announces that he will work on individual feature branches which will then be integrated later into a single version.

Paolo points out that it is not convenient to have separate branches for each client but it is always better to have everything in a single development cycle.

21:15

Project Roadmap

Alessandro Domanico

Alessandro makes an introduction to the project roadmap and announces his intention to release version 2.0 in January 2020.

So they are briefly explained what the missing tasks are to get to this important goal and the structure of the project, that is composed by several components now (GitHub repositories):

  • openhospital-core

  • openhospital-gui

  • openhospital-api

  • openhospital-ui

  • openhospital-doc

We also remember what tools are available to take charge of a job and bring it forward: Jira Tasks (planned), GitHub Tasks (tickets), Action Logs Page (after these meetings) and Decision Log Page (for wider discussions).

Some tasks are in the merge and final review phase, while others have been modified in their definition: for example the existing translations will not be reused but the new interface will have its own translation system. Related tickets and discussions:

22:00

“api” and “ui”

Niccolò Pasquetto Riccardo Costa

Niccolò and Riccardo reported on what is missing to get to the publication of the first SPA (Single Page Application) in React, exposing part of their work that must be shared as soon as possible.

In particular, there is an open discussion on exception handling, which must be moved online to bring everyone's contributions together and make a decision. A “decision page” on the topi might be created but since developments are already going, we will try to use the same task’s page OP-127.

The involved tasks are the following:

22:45

Sprint definition

Alessandro Domanico

Alessandro tried to build a Sprint from the Backlog and then propose the following result to the participants.
It is very important, before being approved, that the Sprint contains all tasks with owners and non-orphans, it is not important how many they are as long as they are assigned and completed in the Sprint, after which you can proceed to the next sprint.

Proposed Sprint: Sprint (SCRUM)

23:15

Next Call

Alessandro Domanico

Since next end of the month is in between Xmas and The New Year, next call will be planned in late January, so all of us can concentrate on the Sprint, that anyway will be updated if needed.

Action items

  •  To query former JPA Task programmer for clarifications on RepositoryFactory “implementations” in OH1.x
  •  To propose the Sprint backlog and await for candidacies

...