From da31f415f816ce786bca944e687ac5e5cf004830 Mon Sep 17 00:00:00 2001
From: John Coffey <john@coffeylabs.org>
Date: Sun, 11 Oct 2026 01:02:33 -0700
Subject: [PATCH] CONTRIBUTING: how to send a change without repository access

New accounts on git.coffeylabs.org can file issues but can't push or fork.
Until a volunteer is given access, a change arrives as a patch on an issue.
---
 CONTRIBUTING.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 840ca6a..a2083a7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -3,6 +3,23 @@
 How to build and test the tool, and where its design is written down. For what
 the tool does and how to use it, see the [README](README.md).
 
+## Sending a change
+
+New accounts on git.coffeylabs.org can file issues but can't push or fork.
+Until you have repository access, open an
+[issue](https://git.coffeylabs.org/coffey-labs/stalwart-migrator/issues) for the change, or say hello
+on [community.coffeylabs.org](https://community.coffeylabs.org), and attach the
+change to the issue as a patch:
+
+```sh
+git format-patch origin/main --stdout > my-change.patch
+```
+
+Repository access goes to volunteers we have worked with; a few good issues or
+patches is the usual way in. After that you push a branch here and open a pull
+request. The GitHub copy is a read-only mirror, so pull requests opened
+there are not merged.
+
 ## Build and test
 
 ```sh
-- 
2.54.0