Deprecated in favor of RFC 2849

[openldap] / doc / devel / guidelines

diff --git a/doc/devel/guidelines b/doc/devel/guidelines
index 82433d2166f6ea4a4adf09042fc8fce9cf4391fe..3f81652b0e0f8110b33845f9f1548ad360a943c2 100644 (file)
--- a/doc/devel/guidelines
+++ b/doc/devel/guidelines
@@ -1,7 +1,15 @@
+$OpenLDAP$
+
+This document is being replaced with:
+       http://www.openldap.org/devel/programming.html
+and
+       http://www.openldap.org/devel/contributing.html
+
+However, some of the info here is still useful.
+
 Coding guide lines and and hints for OpenLDAP developers.
 =========================================================
 
-
 Please add to this file when new points come up.
 
 
@@ -65,12 +73,14 @@ even for non-installed headers.  See lber.h and ldap.h for examples.
 CVS updating
 ------------
 
-<URL:http://www.openldap.org/repo.html> describes how to check out
+<URL:http://www.openldap.org/software/repo.html> describes how to check out
 -stable.  To get the -devel (HEAD) branch, omit `-r OPENLDAP_STABLE'.
 You can use 'cvs status -v README' to get a list available CVS tags.
 
-Core members should subscribe to the private -core mailing list and
-coordinate activities there.
+Core members should subscribe to the -core mailing list.  This
+list is for private discussions between core team members.  The
+openldap-devel@openldap.org mailing list is the primary developer
+forum for both  technical disscusions and coordinating efforts.
 
 Please test patches before committing.  This should include compiling
 and linking the system AND running the test suite.