From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Clarify bug report requirements wrt mailing list subscription
Date: Thu, 21 Oct 2021 13:39:35 +0200 [thread overview]
Message-ID: <YXFRd6janEP6hwS3@maokai> (raw)
In-Reply-To: <CAEOO5TfbVcymik_X5MJQPhTZiZDQVjH+bmY7fy=8axVgyVnbwg@mail.gmail.com>
On Wed, Oct 20, 2021 at 08:33:42PM -0300, Carlos Pita wrote:
> I find the instructions about bug reporting in [1] lacking a heads-up
> that subscription to the mailing list is a (soft?) prerequisite. It's
> true that it links to [2] which states:
>
> You can subscribe to the list from this web page. If you are not a
> member of the mailing list, your mail will be passed to the list
> after a moderator has approved
Subscription is not a prerequisite to sending your message to the
mailing list. If you do not subscribe, your message will wait for
moderation. There is no guarantee that your message will pass
moderation quickly, it could be many days because we have only
volunteer moderators.
Once your address has passed moderation, if you aren't already a
subscriber, you will be added to a list of authorized senders so you
don't have to wait in moderation again.
Either way it's true that the mailing list has some reasonable
protections against spam. I'm sorry if that's caused you some
frustration, but we're all just volunteers with limited time.
I find the Org list policy to be very liberal. I am on other mailing
lists where subscription is mandatory to send any message, and
unauthorized senders are ignored completely.
> but also it's true [3] states:
>
> The Org mailing list is a members only mailing list to prevent
> spam. Membership is freely available and only requires that you
> subscribe to the list and confirm your email address.
>
> Moreover, that it seemingly is a soft requirement implies that I'm not
> getting any feedback for some time about the status of my report.
Indeed. Spam protections can cause problems.
However, what are your expectations regarding a response for a bug
report? Specifically are you referring to the time until your report
shows up on the list archive, or the issue itself is addressed?
I agree we should try to effectively communicate what you should
expect when posting a bug report the first time, and how quickly your
report can reach the list. (ie: instantly if you subscribe, or expect
delays in moderation)
As to how fast the bug can be confirmed or addressed, there are no
guarantees.
> What do you think of:
>
> - Adding some brief mention to subscription in [1].
I've updated the Worg page, it should be pushed out soon.
> - Resolve the apparent contradiction about subscription being a
> prerequisite or not between [2] and [3].
I've updated [3] as well, pending next update.
> [1] https://orgmode.org/worg/org-issues.html
>
> [2] https://orgmode.org/org.html#Feedback
>
> [3] https://orgmode.org/worg/org-mailing-list.html
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
prev parent reply other threads:[~2021-10-21 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 23:33 Clarify bug report requirements wrt mailing list subscription Carlos Pita
2021-10-21 11:39 ` Russell Adams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YXFRd6janEP6hwS3@maokai \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).