On 07/08/2010 09:30 AM, Sebastian Benthall wrote: > One thing I can think of right off the bat that is comments on the > Python stuff in particular. I think it would be good to adopt a > standard for that and try to stick to it. > I'm not sure I understood this; it is a vague response to a long email. Are you saying that we should have some coding guidelines for patches to the Python code that stipulate comment formatting?
Each language has some documented coding guidelines (with varying degrees of officialness) we could crib off of if we want to discuss formatting in a specific way: http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html http://www.python.org/dev/peps/pep-0008/ http://javascript.crockford.com/style1.html Or we could look to the style guidelines of a closely related project: http://docs.codehaus.org/display/GEOT/5.1.1+Coding+Conventions http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style http://trac.openlayers.org/wiki/CodingStandards Along these lines, I'd also be interested in having some browsable API documentation once dev.geonode.org is available to us for such things. A certain level of documentation coverage could be another factor in patch acceptability. -- David Winslow OpenGeo - http://opengeo.org/
