path: root/CONTRIBUTING.rst
diff options
authorSean Whitton <>2020-05-01 11:21:56 -0700
committerSean Whitton <>2020-05-01 11:21:56 -0700
commit6131b675e852077b65a588c636206ce0bf29ba27 (patch)
tree353b3c138bdee3ccc30c60515b98fe855ffa2c88 /CONTRIBUTING.rst
parent89c13d03c7fa3ea148b92707990aee2e2301fb2e (diff)
add mailing list info to
Signed-off-by: Sean Whitton <>
Diffstat (limited to 'CONTRIBUTING.rst')
1 files changed, 54 insertions, 0 deletions
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index 707e2f6..0db4ab0 100644
@@ -1,3 +1,57 @@
+Submitting patches
+Thank you for your interest in contributing to this project!
+Please **do not** submit a pull request on GitHub. The repository
+there is an automated mirror, and I don't develop using GitHub's
+Project mailing lists
+There are two low-volume project mailing lists, shared with some other
+small free software projects:
+- sgo-software-announce --
+ <>
+ For release announcements.
+- sgo-software-discuss --
+ <>
+ For bug reports, posting patches, user questions and discussion.
+Please prepend ``[mailscripts]`` to the subject line of your e-mail,
+and for patches, pass ``--subject-prefix="PATCH mailscripts"`` to
+Posting to sgo-software-discuss
+If you're not subscribed to the list, your posting will be held for
+moderation; please be patient.
+Whether or not you're subscribed, has
+aggressive antispam. If your messages aren't getting through, we can
+easily add a bypass on chiark; please contact <>.
+If you don't want to deal with the mailing list and just want to send
+patches, you should feel free to pass ````
+to git-send-email(1).
+Alternatively, publish a git branch somewhere publically accessible (a
+GitHub fork is fine) and write to me asking me to merge it. I may
+convert your branch back into patches when sending you feedback :)
+Reporting bugs
+Please read "How to Report Bugs Effectively" to ensure your bug report
+constitutes a useful contribution to the project:
Signing off your commits