[SCM] postgis.net branch website updated. clarity-final-88-ga87b7e2

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "postgis.net".

The branch, website has been updated
       via  a87b7e2533c73b4fe434f478dd3e2e8bfc59ee0f (commit)
      from  44bc53097dc635c9a2cc98487a83c00018b6f89d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a87b7e2533c73b4fe434f478dd3e2e8bfc59ee0f
Author: Regina Obe <lr at pcorp.us>
Date:   Wed Mar 13 18:14:58 2024 -0400

    Details on how to submit patches

diff --git a/content/development/developer_docs.md b/content/development/developer_docs.md
index 8ea9bed..293f711 100644
--- a/content/development/developer_docs.md
+++ b/content/development/developer_docs.md
@@ -1,6 +1,6 @@
 ---
 title: Developer Documentation
-date: 2023-07-14
+date: 2024-03-13
 weight: 110
 geekdocHidden: false
 layout: toplevel
@@ -9,6 +9,7 @@ layout: toplevel
 * [Style Guide](https://git.osgeo.org/gitea/postgis/postgis/src/branch/master/STYLE)
 * [Testing with Docker](https://trac.osgeo.org/postgis/wiki/DevWikiDockerTesting)
 * [Backtracing Crashes](https://trac.osgeo.org/postgis/wiki/DevWikiGettingABackTrace)
+* [Submitting documentation for a new feature](https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature)
 
 ## Doxygen Documentation
 This is doxygen documentation for all supported branches.
diff --git a/content/development/getting_involved.md b/content/development/getting_involved.md
index 8e363bf..d0d9ef3 100644
--- a/content/development/getting_involved.md
+++ b/content/development/getting_involved.md
@@ -1,6 +1,6 @@
 ---
 title: Getting Involved
-date: 2022-02-01
+date: 2024-03-13
 weight: 40
 description: "Some tips for how to get started with contributing code and documentation to the project."
 geekdocHidden: false
@@ -22,3 +22,17 @@ Before you can contribute anything, you need to be able to build the software an
 
 * Consider installing PostGIS and its dependencies ([GDAL](https://gdal.org), [GEOS](https://libgeos.org), [Proj](https://proj.org)) from source. This will allow you to debug deeply into whatever you are working on.
 * Install the documentation dependencies tools (docbook-xsl, xsltproc).
+
+## Submitting Patches
+
+If you've read all the above, and are ready to submit a patch, do the following:
+
+1.  Create a [new ticket](https://trac.osgeo.org/postgis/newticket) on our ticket tracker 
+    or find an existing ticket you would like to submit a fix for. Although we will accept new features via pull requests without a ticket, we prefer a ticket in place.
+2.  In the ticket detail the new feature purpose, and attach a patch or alternatively a link to 
+    a pull request on one of the postgis [git mirrors or primary repo](../source_code/#source-code-repository).
+
+If your feature involves a new function/ feature, we expect documentation to accompany this.
+Details on how to prepare documentation are on [Submitting documentation for a new feature](https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature)
+
+

-----------------------------------------------------------------------

Summary of changes:
 content/development/developer_docs.md   |  3 ++-
 content/development/getting_involved.md | 16 +++++++++++++++-
 2 files changed, 17 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
postgis.net