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