zsh-workers
 help / color / Atom feed
From: Rudi C <rudiwillalwaysloveyou@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [Bug] Unexpected bug suspension
Date: Thu, 21 May 2020 17:09:03 +0430
Message-ID: <CAE9z9A1ZOYyBcKwXjXD4JBKiUSpK1gSqRBz_GEqLvEJmtwdjvw@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3QY2JWaqqOc_T2H8=QHqgDCGsG-3iF982845GcHPtV5gw@mail.gmail.com>


[-- Attachment #1: Type: text/plain, Size: 3451 bytes --]

Still, that's just one example. I don't claim I have done statistical
research on this, but my intuition is that better organization leads to
increased productivity and decreased bikeshedding. Also, I don't know what
regulars here use to manage their email, but I can tell you that using a
mailing list is rather incompatible with modern, mainstream email clients.
I personally use Telegram's Gmail bot as my main way of receiving emails,
and it fails to format emails from mailing lists correctly. I think the
fact that most people have switched to using Github's issue tracker (even
some closed-source projects) should hint that there are good reasons for
using a modern, web&mobile-friendly solution. As you know, Github has now
released official clients for both the terminal and iOS. Of course, I don't
know much about other issue trackers, and if there is a better option, then
that's fine, too. What I don't grok (at all) is what advantages the mailing
list is bringing to the table. Github issues can be received and replied to
via email as well. I might be a young, inexperienced person, but I have no
idea how to do basic things like searching through the past issues in the
mailing list. (Do I use Google with a "site:" directive?) Even when finding
an issue in the archive, all the conversation is scattered across so many
pages, that it just doesn't compare to the sleek experience you get on
Github. I mean, the only way I am keeping up with this issue I have opened
myself is by having a pinned tab of
https://www.zsh.org/mla/workers/2020/index.html on my Chrome, which I check
regularly. And I am the kind of person who has 1000 lines of emacs config,
9 open tabs in iTerm at all times, the first of which is a tmux session
that has three panes. (And I am a student currently who doesn't work, so
all that is for personal use.) I take my notes on a plain-text system that
uses git and personal scripts to search/manage them. I listen to music
through a custom scraper/player CLI I wrote. I follow my readables through
scripts that scrape rss, email, and websites, and package the results into
EPUBs that get sent to my Kindle device. You get the idea. I think when I
feel that the mailing list is a relic of the past that does not bode well
in the mobile age, you should seriously consider that. The current system
cannot be utilized effectively by probably more than 98% of developers.
Googling for "how to use mailing list effectively" returns marketing
bullshit. ...

On Thu, May 21, 2020 at 1:53 PM Mikael Magnusson <mikachu@gmail.com> wrote:

> On 5/21/20, Rudi C <rudiwillalwaysloveyou@gmail.com> wrote:
> > Considering this bug (or a very similar variant) was reported before and
> > the issue just died a silent death, I think it's a good idea to create a
> > Github repo for tracking zsh issues. Github issue tracker is a lot better
> > than mailing lists, as things have a dichotomy of being  open/closed, and
> > can be labeled. It is harder for issues to die a silent death there. It
> is
> > also easier to contribute to that, and easier to unsubscribe (I don't
> think
> > one can unsubscribe from a mailing list post one participated in, as
> people
> > (wisely) use reply-all.).
>
> As a counterpoint to that, I give you
> https://bugzilla.mozilla.org/show_bug.cgi?id=734643 which has been
> open for 8 years. Nobody cares about bugs more just because they are
> "open" in some bug tracker.
>
> --
> Mikael Magnusson
>

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  9:23 Mikael Magnusson
2020-05-21 12:39 ` Rudi C [this message]
2020-05-21 18:10   ` Bart Schaefer
2020-05-21 19:01     ` Bart Schaefer
2020-05-21 20:15       ` Rudi C
2020-05-21 21:00         ` Bart Schaefer
2020-05-21 16:30 ` Daniel Shahaf

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE9z9A1ZOYyBcKwXjXD4JBKiUSpK1gSqRBz_GEqLvEJmtwdjvw@mail.gmail.com \
    --to=rudiwillalwaysloveyou@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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

zsh-workers

Archives are clonable: git clone --mirror http://inbox.vuxu.org/zsh-workers

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.zsh.workers


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git