Update develop from main

CODE_OF_CONDUCT.md

@@ -58,7 +58,7 @@ We strive to:
   Our work will be used by other people, and in turn we will depend on the work
   of others. When we make something for the benefit of CoastalME, we are willing to
   explain to others how it works, so that they can build on the work to make it
-  even better. Any decision we make will affect users and colleagues, and we
+  even better. Also, please make use of existing code (such as CoastalME's 2d integer and floating point classes) wherever possible. Don't try to re-invent the wheel! Any decision we make will affect users and colleagues, and we
   take those consequences seriously when making decisions.
 
 - Be inquisitive.
@@ -132,4 +132,4 @@ To privately email the code of conduct committee leadership use coc@osgeo.org.
 Credits
 -------
 
-CoastalME re-uses the `OSGeo Code of Conduct <https://www.osgeo.org/resources/osgeo-code-of-conduct/>`__
+CoastalME re-uses the `OSGeo Code of Conduct <https://www.osgeo.org/resources/osgeo-code-of-conduct/>`__

development/rfc/rfc2_commiters.md

@@ -96,6 +96,7 @@ project.
    managers are assumed to have permission to create a branch.
 -  All source code in SVC should be in Unix text format as opposed to
    DOS text mode.
+-  Please make use of existing code (such as CoastalME's 2d integer and floating point classes) wherever possible. Don't try to re-invent the wheel!
 -  When committing new features or significant changes to existing
    source code, the committer should take reasonable measures to ensure
    that the source code continues to build and work on the most commonly