From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: issue tracker?
Date: Tue, 19 May 2020 18:57:20 +0200 [thread overview]
Message-ID: <20200519165720.GQ30250@volibear> (raw)
In-Reply-To: <CAF-FPGON2c6Hk+BtdM_+M3sFMeGcy_BWs_80cB+8RWfB7nL2Jg@mail.gmail.com>
I can't help but chime in here. Using email for project management, patches,
testing, etc is not difficult or unusual.
In fact, the Linux kernel uses email for this purpose. They have a variety of
reasons which were recently covered in some articles. Clearly their code base
and number of developers is overwhelmingly larger than Org, so we must be doing
something right.
https://lwn.net/Articles/702177/
https://kernel-recipes.org/en/2016/talks/patches-carved-into-stone-tablets/
My personal opinion is I'd always prefer to use my mail client over some
website. I've personally chosen what I think is the best mail client, where I
can easily sort and read mail from mailing lists. It has a fast interface, easy
to read, and is incredibly consistent (yay Mutt!). I can also rapidly edit (in
Emacs!) my replies. I can send an email in a matter of keystrokes, blindly
typing.
Compare that to most websites where I have to wait forever for all the crap
javascript to load, forfeit my privacy to all the trackers and cookies, and then
manage to figure out how their site works. Once done I'm thrown into a
significantly inferior editor box to try and type or paste information in. From
that point, I can only use their website to manage my submission.
The irony that these websites will often notify me *by email* that something has
occurred.
I clearly don't agree that adding a website somehow makes issue tracking or
patch submission magically easier to manage or submit bug information compared
to email.
If you have feedback, please don't hesitate to just send an email to the list
with your questions or comments. This is easily one of my favorite lists and
very welcoming even to controversial opinions.
On Tue, May 19, 2020 at 10:58:26AM -0400, Bruce D'Arcus wrote:
> Regardless, doing issue tracking, discussion, and patch submission on a ML
> in 2020 is pretty odd and inefficient.
>
> I would have submitted feedback here 6-12 months earlier than I did if org
> had a proper issue tracker.
>
> On Tue, May 19, 2020, 3:35 AM <tomas@tuxteam.de> wrote:
>
> > On Mon, May 18, 2020 at 06:13:38PM -0500, James R Miller wrote:
> > > Doesn’t Gogs have a nice issue tracker functionality?
> >
> > I looked up Gogs. Needs javascript *and* cookies. Wake me up when
> > there's a plain, straight service which works without any of them.
> >
> > Cheers
> > -- t
> >
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2020-05-19 16:58 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 [this message]
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
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=20200519165720.GQ30250@volibear \
--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).