125839Speter                        CVS Development Policies
225839Speter
325839SpeterThis file, DEVEL-CVS, contains the policies by which the CVS
425839Speterdevelopment group operates.  Also see the HACKING file.
525839Speter
625839Speter----------------------------------------------------------------------
725839SpeterPolicies regarding the CVS source repository:
825839Speter
925839SpeterBy checking items into the repository, developers agree to permit
1025839Speterdistribution of such items under the terms of the GNU Public License.
1125839Speter
1225839Speter----------------------------------------------------------------------
1325839SpeterProcedure for dealing with people who want to be developers:
1425839Speter
1526801SpeterPeople who want checkin access are first requested to send
1625839Speterpatches and have them reviewed by a developer.  If they submit some
1725839Spetergood ones (preferably over a period of time, to demonstrate sustained
1825839Speterinterest), then one of the developers can ask the devel-cvs mailing
1925839Speterlist whether it is OK to make this person a developer (after first
2025839Spetersending the prospective developer a copy of this file and then having
2125839Speterthe prospective developer say they want to be a developer).  If there
2232785Speterare no objections, the person will be made a developer.
2326801Speter
2426801Speter----------------------------------------------------------------------
2526801SpeterPolicy regarding checkout-only access:
2626801Speter
2726801SpeterCheckout-only access to the CVS repository is available to all, on an
2826801Speteranonymous basis (no need for registration or other complications).
2926801SpeterThe exact technical mechanisms by which it is available are not
3026801Spetercovered by this policy.
31