diff --git a/source/conf.py b/source/conf.py
index b2dc4ba54..cf35b94bf 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -14,9 +14,9 @@ copyright = '2020, OpenDroneMap'
 author = 'OpenDroneMap'
 
 # The short X.Y version
-version = '0.9.9'
+version = '0.9.10'
 # The full version, including alpha/beta/rc tags
-release = '0.9.9'
+release = '0.9.10'
 
 
 # -- General configuration ---------------------------------------------------
diff --git a/source/contributing.rst b/source/contributing.rst
index 8866f90e4..8a6709c90 100644
--- a/source/contributing.rst
+++ b/source/contributing.rst
@@ -1,6 +1,6 @@
 .. contributing
 
-How to contribute
+How To Contribute
 =================
 
 OpenDroneMap relies on community contributions. You can contribute in many ways, even if you are not a programmer.
diff --git a/source/flying.rst b/source/flying.rst
index fdf818f71..5d5e5925a 100644
--- a/source/flying.rst
+++ b/source/flying.rst
@@ -1,4 +1,4 @@
-Flying tips
+Flying Tips
 ===========
 
 The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has guidelines on `flying for UAV mapping <https://uav-guidelines.openaerialmap.org/>`_:
diff --git a/source/index.rst b/source/index.rst
index 437410d9a..25a1787d5 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -37,6 +37,7 @@ Welcome to OpenDroneMap's documentation
     resources
     flying
     multispectral
+    requesting-features
     contributing
 
 `Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_
diff --git a/source/requesting-features.rst b/source/requesting-features.rst
new file mode 100644
index 000000000..f8369621f
--- /dev/null
+++ b/source/requesting-features.rst
@@ -0,0 +1,33 @@
+How To Request Features
+=======================
+
+All software needs user feedback and feature requests, to grow and maintain 
+alignment with the needs of its users. 
+
+OpenDroneMap is FOSS software.  Free and open source (FOSS) projects are interesting 
+from the inside and outside: from the outside, successful ones feel like they should be able 
+to do anything, and it’s hard to know what a reasonable request is. From the inside of a 
+project, they can feel very resource constrained: largely by time, money, and opportunity 
+overload.
+
+A feature request can be submitted as issues on the applicable Github repository (e.g., 
+`WebODM <https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM <https://github.com/OpenDroneMap/ODM/issues>`_ 
+or similar) or more simply as a discussion topic on `the community forum <https://community.opendronemap.org/>`_.  
+Try to start by searching these sources to see if someone else has already brought it up.  Sometimes a feature is already in 
+the works, or has at least been discussed.
+
+And importantly, the trick is to listen: if someone within the project says: "This is a big lift, 
+we need MONEY or TIME or SOMEONE TO HELP CODE IT" (or possibly a combination of the three) 
+then there are two answers that work really well in response:
+
+    *Ok. I didn’t know it was a big feature request! I hope someone comes along with the necessary resources. As a community member, I would be happy to be an early user and tester!*
+
+or
+
+    *Let’s figure out if we can put together the resources to get this done! Here’s what I can contribute toward it: …*
+
+We are glad you are excited to see new features added to the project.  Some new features need support, 
+and some are easier to implement.  We'll do our best to help you understand where your request falls, and 
+we appreciate any support you can provide.
+
+`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-features.rst>`_
\ No newline at end of file