Commit 1d5ae389 authored by Yannick TANGUY's avatar Yannick TANGUY

Update after PSC meeting (2018-02-22) :

new rules to accept Merge Request
parent 99723cb9
......@@ -122,7 +122,7 @@ decision-making, or in case of disputes over voting.
A vote of the PSC is required in the following cases:
1. Merge Request
1. Some Merge Request (see below)
2. Addition or removal of PSC members (including the selection of a new
3. Release process
......@@ -134,22 +134,28 @@ In addition, a vote can be summoned for:
#### Merge Request
A Merge Request describes a change in Orfeo ToolBox code, API,
infrastructure or processes that need to be submitted to the PSC vote:
All changes in Orfeo ToolBox (code, API, infrastructure or processes) must be
handle with a Merge Request :
- Anything that could cause backward compatibility issues,
- Adding substantial amounts of new code,
- Changing inter-subsystem APIs, or objects,
- Any change in the code or in the documentation.
It should describe :
Merge Request can be linked to an issue and should describe :
1. What changes will be made and why they will make a better Orfeo
2. When will those changes be available (target release or date)
3. Who will be developing the proposed changes
Those elements can be provided in an email to the developer list or on a
git hosted platform (GitLab, GitHub, etc.).
Those elements must be provided to a git hosted platform (GitLab, GitHub, etc.).
Merge request can be discussed on the developer list or directly on GitLab.
Votes are necessary to accept Merge Request :
- Core developers members can vote
- At least two +1 are necessary
- PSC members have veto
#### Add or remove PSC members
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment