| 1 |
CVS Development Policies |
| 2 |
|
| 3 |
This file, DEVEL-CVS, contains the policies by which the CVS |
| 4 |
development group operates. Also see the HACKING file. |
| 5 |
|
| 6 |
---------------------------------------------------------------------- |
| 7 |
Policies regarding the CVS source repository: |
| 8 |
|
| 9 |
By checking items into the repository, developers agree to permit |
| 10 |
distribution of such items under the terms of the GNU General Public |
| 11 |
License. |
| 12 |
|
| 13 |
---------------------------------------------------------------------- |
| 14 |
Procedure for dealing with people who want to be developers: |
| 15 |
|
| 16 |
People who want checkin access are first requested to send |
| 17 |
patches and have them reviewed by a developer. If they submit some |
| 18 |
good ones (preferably over a period of time, to demonstrate sustained |
| 19 |
interest), then one of the developers can ask the other CVS |
| 20 |
developers, usually via the [email protected] mailing list, whether it |
| 21 |
is OK to make this person a developer (after first sending the |
| 22 |
prospective developer a copy of this file and then having the |
| 23 |
prospective developer say they want to be a developer). If there are |
| 24 |
no objections, the person will be made a developer. |
| 25 |
|
| 26 |
---------------------------------------------------------------------- |
| 27 |
Policy regarding checkout-only access: |
| 28 |
|
| 29 |
Checkout-only access to the CVS repository is available to all, on an |
| 30 |
anonymous basis (no need for registration or other complications). |
| 31 |
The exact technical mechanisms by which it is available are not |
| 32 |
covered by this policy. |