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---------------------------------------------------------------------- 7Charter for the devel-cvs mailing list: 8 9The CVS Developers' List <devel-cvs@cvshome.org> exists to help people 10with access to the CVS source repository co-ordinate changes, make 11releases, and administer the repository. 12 13Everyone who has been given checkin access to the repository for the 14CVS sources should read devel-cvs. Only those with checkin access may 15send messages to the list. 16 17The devel-cvs list may be used to discuss: 18- administrivia regarding the CVS source repository and release 19 process, and 20- changes and features intended for inclusion in the official CVS 21 release (either source code or documentation), which someone plans 22 to implement, or has implemented. 23 24The devel-cvs list should not be used to discuss: 25- changes or features to packages other than the CVS release 26 (e.g., related packages like tkCVS, RAD/CVS, or other groups' 27 distributions of CVS, like RCVS, etc.), 28- changes which nobody has offered to implement, or 29- the philosophy of CVS (as opposed to a specific change to CVS). 30These topics should either go on info-cvs, or have a new mailing list 31created for them. 32 33The topic restrictions in this charter do not reflect the development 34group's future plans for CVS; rather, they reflect a topic 35classification which the group finds helpful. 36 37---------------------------------------------------------------------- 38Policies regarding the CVS source repository: 39 40By checking items into the repository, developers agree to permit 41distribution of such items under the terms of the GNU Public License. 42 43---------------------------------------------------------------------- 44Procedure for dealing with people who want to be developers: 45 46People who want checkin access are first requested to send 47patches and have them reviewed by a developer. If they submit some 48good ones (preferably over a period of time, to demonstrate sustained 49interest), then one of the developers can ask the devel-cvs mailing 50list whether it is OK to make this person a developer (after first 51sending the prospective developer a copy of this file and then having 52the prospective developer say they want to be a developer). If there 53are no objections, the person will be made a developer. 54 55---------------------------------------------------------------------- 56Policy regarding checkout-only access: 57 58Checkout-only access to the CVS repository is available to all, on an 59anonymous basis (no need for registration or other complications). 60The exact technical mechanisms by which it is available are not 61covered by this policy. 62