From 5be3ade929976a5aff573fda7f8dc1526aa81b8a Mon Sep 17 00:00:00 2001
From: Rich Bowen <rbowen@rcbowen.com>
Date: Fri, 26 Sep 2025 15:52:47 -0400
Subject: [PATCH 1/2] Non-code contributions; A few TODO items.

---
 source/contributors/_index.md        | 36 ++++++++++++++++++++++++----
 source/contributors/mailing-lists.md | 10 ++++++++
 2 files changed, 42 insertions(+), 4 deletions(-)

diff --git a/source/contributors/_index.md b/source/contributors/_index.md
index 4ef81a6c..2dfdf4c7 100755
--- a/source/contributors/_index.md
+++ b/source/contributors/_index.md
@@ -50,11 +50,30 @@ reasonable first step towards contributing. Keep notes of that first
 user experience, as that is valuable information for the project, and
 might be a good place to start your contributions.
 
-### The Code
+### What can I contribute?
 
-Most (not all) Apache projects have their code on
-[GitHub](https://github.com/apache). Search for the project name in the
-**apache** GitHub organization.
+Most people's first thought when contributing to open source projects is
+code. And, indeed, that's where most people get involved. Most (not all) 
+Apache projects have their code on [GitHub](https://github.com/apache).
+Search for the project name in the **apache** GitHub organization.
+
+There are, however, many other areas where you can contribute to a
+project. These include, but are not limited to:
+
+* Documentation
+* Marketing and social media promotion
+* Event planning
+* Technical support on mailing lists and other forums
+* Vendor/Sponsor relations
+* Project management (organizing the next sprint or feature set, keeping
+  track of who is working on what, updating the roadmap)
+* Community management
+
+Projects should identify, recruit for, and celebrate contributions in
+all of these areas, and reward non-code contributors with the same
+rights and privileges that they do for code contributors. 
+
+**Being a committer is *not* just for code contributors!**
 
 ### Communication
 
@@ -67,6 +86,15 @@ participate in current discussions, either by subscribing to the lists,
 or by using the [lists.apache.org][11] site
 directly.
 
+<!--
+
+TODO:
+
+All of this stuff about mailing lists should be in mailing-lists.md
+rather than here.
+
+-->
+
 #### Subscribe
 
 To subscribe (that is, to receive every message sent to the list via
diff --git a/source/contributors/mailing-lists.md b/source/contributors/mailing-lists.md
index 7a4e5f9e..dd84c57b 100644
--- a/source/contributors/mailing-lists.md
+++ b/source/contributors/mailing-lists.md
@@ -93,6 +93,16 @@ conversation is essential to collaboration.
 
 ASF mailing lists default to English, unless specified otherwise.
 
+<!--
+
+TODO:
+
+This stuff about configuring mailing lists should really be under
+/committers rather than here, since you can't make any of these changes
+until you're a committer.
+
+-->
+
 ## Mailing list configuration
 
 Modern software development tools, including GitHub, your various ticket

From 33c7879e66170a1479765fe0c2a90b9a6d534b2b Mon Sep 17 00:00:00 2001
From: Rich Bowen <rbowen@rcbowen.com>
Date: Fri, 3 Oct 2025 10:54:09 -0400
Subject: [PATCH 2/2] committed/committer

---
 source/contributors/_index.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/source/contributors/_index.md b/source/contributors/_index.md
index 2dfdf4c7..2d1dba04 100755
--- a/source/contributors/_index.md
+++ b/source/contributors/_index.md
@@ -73,7 +73,8 @@ Projects should identify, recruit for, and celebrate contributions in
 all of these areas, and reward non-code contributors with the same
 rights and privileges that they do for code contributors. 
 
-**Being a committer is *not* just for code contributors!**
+**Being a committer is *not* just for code contributors!** It's a
+recognition of anyone who is **committed** to the project.
 
 ### Communication