Skip to main content

Presentation: Joinup re-use & collaborative development - 2013-10-22

Anonymous (not verified)
Published on: 22/10/2013 Last update: 05/06/2014 Document Archived

The publication process for the source code and the installation manuals was presented. The collaborative tools used in the context of Joinup, Confluence, JIRA and SVN were also briefly presented.

The current processes for development and deployment are complex and have a number of weaknesses. Everis is working to simplify and automate the deployment process because the current processes are unfit for collaborative development. There are two scenarios to work together at technical level:

  1. Global application

This scenario implies that Joinup, OpenRay and OpenRoad would all use the same software and functionalities. The advantages of this scenario are that it would allow immediate collaboration and that it would provide create a platform that could be used globally. However, this scenario is not very flexible.

  1. Parameterised application

This scenario implies the creation of modules with separate functionalities that can be turned on and off. This solution is flexible and would make it easy to share the development work. However, it would add another layer of complexity to Joinup and it would take some time to implement.

Regardless of which scenario is selected, the simplification of the deployment process for new releases of Joinup is still necessary.

Key message: The development and deployment processes must be automated and simplified to make collaborative development possible.

by Pablo Rojo Guerra (Everis)

Nature of documentation: Other

Categorisation

Type of document
Document
Login or create an account to comment.