...
- soon we will publish a third component (repository) on GitHub "openhospital-api" which will initially contain an example of REST services built around the "org.isf.patient" module and documented with OpenAPI (ex Swagger) which will be the track we will all follow for then cover all the other modules
- there is absolute freedom in self-assigning tasks, creating new ones if necessary, dividing them into smaller sub-tasks and discussing them directly on Jira (in English) to ask for opinions or share choices and activities with the whole community, do not be shy!
- to contribute to the code one always proceeds according to the fork & pull-request scheme on GitHub and is documented through the Wiki (which also has tasks on Jira that can be taken over by someone, see
,Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-7
andJira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-8
)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-9 - at Paolo Viotti suggestion we will try to "label" Jira's tasks with specific labels so that they can be reorganized or searched by type and degree of difficulty
- We meet in about a month to discuss the progress of the work (around the end of April).
...