Describe policies regarding permissions on Git/Gerrit repositories
Submitted by Wayne Beaton @wbeaton
Link to original bug (#532138)
Description
Let's add our policies regarding how we configure Git repositories to the handbook.
The board discussed this a few years ago:
https://www.eclipse.org/org///foundation/boardminutes/2012_06_19-20_Minutes.php
Summary:
-- RESOLVED, that the Board directs the EMO to ensure that the history of the Foundation’s source repositories cannot be changed in “main branches”, with flexibility in private branches. Any exceptions would have to be requested by a PMC to the EMO. A “main branch” is defined as any branch from which releases are built. Any exceptions would have to be requested by a PMC to the EMO.
Brain dump; I believe that this is the current policy:
- Rewriting history on, or removal of "main branches" is permitted only under extraordinary circumstances;
- Permission to rewrite on "main branches" is granted only for specific manipulation and only for limited periods of time;
- The EMO IP Team may direct a project team to rewrite history to remove problematic intellectual property;
- PMC approval is required for any other rewrite;
- The typical scenario is that we create a specific namespace where anyone on the project team can force push. ** refs/heads/${username}/* ** refs/tags/${username}/*
Denis, does this sound reasonable? Am I missing anything?
See related discussion on Bug 472541 and Bug 531562.