Revision: 55953
http://sourceforge.net/p/brlcad/code/55953
Author: brlcad
Date: 2013-07-03 20:06:17 +0000 (Wed, 03 Jul 2013)
Log Message:
-----------
talk about commit access more concretely. it's at least a five step process.
Modified Paths:
--------------
brlcad/trunk/HACKING
Modified: brlcad/trunk/HACKING
===================================================================
--- brlcad/trunk/HACKING 2013-07-03 20:02:09 UTC (rev 55952)
+++ brlcad/trunk/HACKING 2013-07-03 20:06:17 UTC (rev 55953)
@@ -901,6 +901,21 @@
result in automatic consideration for commit access. If you have to
ask for it, you probably won't get it.
+That said, the following steps represent a minimum that needs to occur
+in order for commit access to be granted:
+
+1) Read this file completely.
+
+2) Be able to compile BRL-CAD successfully from an SVN trunk checkout.
+
+3) Join the brlcad-devel developer mailing list, introduce yourself.
+
+4) Create a Sourceforge account, submit two or more patches that
+demonstrate competency with our coding style, apply flawlessly, and
+provide significant improvements to the existing code.
+
+5) Be a nice person. We're here to have fun and do cool things. ;)
+
Those with commit access have a responsibility to ensure that other
developers are following the guidelines that have been described in
this developer's guide within reasonable expectations. A basic rule
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
BRL-CAD Source Commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-commits
