From b55b8a56a8b124e80ae0d0f59a50089b7f36b1db Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Fri, 1 May 2020 12:08:24 -0700 Subject: add mailing list & bug reporting info Signed-off-by: Sean Whitton --- CONTRIBUTING.rst | 48 ++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 42 insertions(+), 6 deletions(-) (limited to 'CONTRIBUTING.rst') diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 428fce0..8e5d94e 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -7,14 +7,50 @@ Please **do not** submit a pull request on GitHub. The repository there is an automated mirror, and I don't develop using GitHub's platform. -Instead, either +Project mailing lists +===================== -- publish a branch somewhere (a GitHub fork is fine), and e-mail - asking me to merge your branch, possibly - using git-request-pull(1) +There are two low-volume project mailing lists, shared with some other +small free software projects: -- prepare patches with git-format-patch(1), and send them to - , possibly using git-send-email(1) +- sgo-software-announce -- + + + For release announcements. + +- sgo-software-discuss -- + + + For bug reports, posting patches, user questions and discussion. + +Please prepend ``[git-remote-gcrypt]`` to the subject line of your e-mail, +and for patches, pass ``--subject-prefix="PATCH git-remote-gcrypt"`` to +git-send-email(1). + +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, chiark.greenend.org.uk 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=spwhitton@spwhitton.name`` +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 ======================== -- cgit v1.2.3