Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 OCS Release Management Board 19/04/2013. 2 Introduction General Vision Proposed approach Tour de table Agenda.

Similar presentations


Presentation on theme: "1 OCS Release Management Board 19/04/2013. 2 Introduction General Vision Proposed approach Tour de table Agenda."— Presentation transcript:

1 1 OCS Release Management Board 19/04/2013

2 2 Introduction General Vision Proposed approach Tour de table Agenda

3 3 Online Collection Software EC Vision OCS is and will remind an open source software developed under EUPL license; All contributions to OCS are welcomed; nevertheless a strict development process is needed in order to ensure quality, security and compliance; OCS is and will remain a tool for gathering Statements of Support, nothing less, nothing more; EC: responsible for compliance with legal framework and with security requirements;

4 4 What is going to change? EC is inviting the OCS stakeholders to work closer Two boards, chaired by EC will meet periodically: Change Management Board, responsible for the general orientation of the software Release Management Board, "technical" group responsible for the development and delivery of the software In order to ensure transparency, all the requirements will be managed through the joinup platform

5 5 Roles of the Release Management Board Coordinate development efforts with requirements prioritized by CMB Estimate the efforts for the implementation of the requirements published in joinup Assign Development/Test tasks to available open source contributors Provide feedback to the Change Management Board on the status of the release Review and improve the OCS development process

6 6 In practice RMB will be composed by up to 15 members from the open source community RMB will meet "virtually" on a regular basis to review the status of the development tasks Before each meeting, the secretary of the board will send the agenda of the meeting Minutes of the meetings will be published in joinup

7 7 Development process Contribution to the software will be provided through patches "diff of the code". Development should comply with a "check list" An environment with the latest patchs deployed will be available to the Open Source Community for testing purposes Any "spontaneous" development will be reviewed by the RMB and proposed to the CMB EC will keep ownership of the Code Review and of Stress and Vulnerability Test

8 8 OCS Requirements in joinup Go to "Issues" page in joinup: http://joinup.ec.europa.eu/software/ocs/issue/all Filter "1.4.0-DD Edition" version Main 1.4.0 requirements: Make captcha easier Enable interface customization Links to Social Media Graphical display for the support received Customized error messages Call-back URL


Download ppt "1 OCS Release Management Board 19/04/2013. 2 Introduction General Vision Proposed approach Tour de table Agenda."

Similar presentations


Ads by Google