| | 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 Public License. |
| | 11 | |
| | 12 | ---------------------------------------------------------------------- |
| | 13 | Procedure for dealing with people who want to be developers: |
| | 14 | |
| | 15 | People who want checkin access are first requested to send |
| | 16 | patches and have them reviewed by a developer. If they submit some |
| | 17 | good ones (preferably over a period of time, to demonstrate sustained |
| | 18 | interest), then one of the developers can ask the other CVS |
| | 19 | developers, usually via the bug-cvs@nongnu.org mailing list, whether it |
| | 20 | is OK to make this person a developer (after first sending the |
| | 21 | prospective developer a copy of this file and then having the |
| | 22 | prospective developer say they want to be a developer). If there are |
| | 23 | no objections, the person will be made a developer. |
| | 24 | |
| | 25 | ---------------------------------------------------------------------- |
| | 26 | Policy regarding checkout-only access: |
| | 27 | |
| | 28 | Checkout-only access to the CVS repository is available to all, on an |
| | 29 | anonymous basis (no need for registration or other complications). |
| | 30 | The exact technical mechanisms by which it is available are not |
| | 31 | covered by this policy. |
nant's projects / dragonfly.git / blame_incremental