From: Trey Ethan Harris <treyharris@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: issue tracker?
Date: Tue, 19 May 2020 16:14:11 -0400 [thread overview]
Message-ID: <CALKJ+Esqcdr7MZsJtRAb=ysS_Ci-Dj+fSk5is6nH0jN99st6gw@mail.gmail.com> (raw)
In-Reply-To: <20200519194833.GS30250@volibear>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
On Tue, May 19, 2020 at 15:49 Russell Adams <RLAdams@adamsinfoserv.com>
wrote:
> Is there a problem with submitting issues via the mailing list? Has
> something
> gone unaddressed? Do you have any statistics to show that there is
> decreased
> participation because you have to use email? Is something really
> inefficient at
> the moment? Did you have patches ignored?
I think you have the null hypothesis backwards here. Do you have any
statistics to show that issues _are not_ dropping through the cracks?
Sending a “ping?” message on a ML is generally considered poor netiquette,
and even if it were expected here, would make many requesters
uncomfortable. That’s one of the fundamental things any tracker does—keeps
statistics on and forces every issue to _some_ resolution, even if it’s
“will not fix” or “on hold”. Things don’t just peter out and get forgotten
like on email threads.
(I have not done the exercise of perusing old email threads to see if I can
find issues being dropped on the floor. But I’ve already found several
apparent existence proofs. Whether they’re common or rare is a question I
can’t answer without doing tedious manual work that is the entire raison
d’être of a tracker.)
I wouldn’t dispute that the Linux kernel ML, for the most part, works. But
the Linux kernel mailing list is a rather different beast than the
potential users of an issue tracker for any other software project I can
imagine—the technical acumen expected of contributors is high, quotidian
back-and-forth user-assistance exchanges with non-contributors are not
tolerated, people are usually expected to offer fixes as working code and
not simply prose bug reports or feature requests (except for critical or
security issues), and patches and pull requests on the mailing list are
dealt with using a distributed version-control system that was
purpose-built for the task (though happens to have worked well enough to
because the most widely-used DVCS period).
[-- Attachment #2: Type: text/html, Size: 2423 bytes --]
next prev parent reply other threads:[~2020-05-19 20:17 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 21:24 issue tracker? Anthony Carrico
2020-05-18 22:21 ` Nick Dokos
2020-05-18 23:13 ` James R Miller
2020-05-19 7:33 ` tomas
2020-05-19 14:02 ` James R Miller
2020-05-19 14:05 ` James R Miller
2020-05-19 14:53 ` tomas
2020-05-19 14:58 ` Bruce D'Arcus
2020-05-19 16:45 ` Timothy
2020-05-19 16:57 ` Russell Adams
2020-05-19 17:03 ` Timothy
2020-05-19 17:29 ` Russell Adams
2020-05-19 18:50 ` James R Miller
2020-05-19 19:42 ` Eric Abrahamsen
2020-05-19 20:17 ` Roland Everaert
2020-05-19 20:47 ` Diego Zamboni
2020-05-19 21:28 ` Eric Abrahamsen
2020-05-19 19:48 ` Russell Adams
2020-05-19 20:14 ` Trey Ethan Harris [this message]
2020-05-19 20:57 ` gyro funch
2020-05-19 23:22 ` James R Miller
2020-05-20 9:22 ` Eric S Fraga
2020-05-20 9:40 ` Detlef Steuer
2020-05-20 11:12 ` Stefan Nobis
2020-05-20 16:41 ` Jud Taylor
2020-05-20 18:55 ` gennady.uraltsev
2020-05-20 22:05 ` Bob Newell
2020-05-21 8:10 ` Nicolas Goaziou
2020-05-21 11:21 ` Bruce D'Arcus
2020-05-21 14:46 ` Kévin Le Gouguec
2020-05-21 16:31 ` Eric Abrahamsen
2020-05-22 8:17 ` Roland Everaert
2020-05-22 14:53 ` Anthony Carrico
2020-05-23 12:57 ` Roland Everaert
2020-05-23 13:14 ` Russell Adams
2020-05-25 11:20 ` Roland Everaert
2020-05-26 12:34 ` Robert Pluim
2020-06-01 14:40 ` Bastien
2020-06-01 14:36 ` Bastien
2020-05-26 19:17 ` Matthew Lundin
2020-06-01 14:43 ` Bastien
2020-05-27 17:59 ` Mario Frasca
2020-05-27 18:12 ` Russell Adams
2020-05-27 18:48 ` Eric Abrahamsen
2020-05-31 8:49 ` Russell Adams
2020-06-01 14:45 ` Bastien
2020-06-01 15:46 ` Mario Frasca
2020-06-01 15:53 ` Bastien
2020-06-01 16:28 ` Mario Frasca
2020-06-01 16:54 ` Russell Adams
2020-06-02 11:57 ` Bastien
2020-06-05 22:44 ` Mario Frasca
2020-06-06 7:57 ` Bastien
2020-06-06 16:15 ` Mario Frasca
2020-06-07 9:38 ` Bastien
2020-06-07 13:50 ` Mario Frasca
2020-06-08 9:11 ` Bastien
2020-05-21 2:35 ` Anthony Carrico
2020-05-21 3:12 ` James R Miller
2020-05-21 5:33 ` Russell Adams
2020-05-21 7:31 ` Kévin Le Gouguec
2020-05-21 14:18 ` Anthony Carrico
2020-05-21 14:38 ` tomas
2020-05-21 14:38 ` Anthony Carrico
2020-05-21 15:05 ` Kévin Le Gouguec
2020-05-22 16:56 ` Ken Mankoff
2020-05-26 19:36 ` Matthew Lundin
2020-06-01 14:59 ` Bastien
2020-09-14 5:23 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2020-06-02 11:38 Vladimir Nikishkin
2020-06-02 11:55 ` Bastien
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='CALKJ+Esqcdr7MZsJtRAb=ysS_Ci-Dj+fSk5is6nH0jN99st6gw@mail.gmail.com' \
--to=treyharris@gmail.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).