From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [Bug] Unexpected bug suspension
Date: Thu, 21 May 2020 16:30:15 +0000 [thread overview]
Message-ID: <20200521163015.0b012455@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAHYJk3QY2JWaqqOc_T2H8=QHqgDCGsG-3iF982845GcHPtV5gw@mail.gmail.com>
Mikael Magnusson wrote on Thu, 21 May 2020 11:23 +0200:
> 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.
True, but I think Rudi did have a valid point as well.
One can't get people to solve bugs by recording those bugs in
a different kind of database. In general, one can't solve a social
problem by technical means. However, having a bug tracker would solve
a _technical_ problem: it would provide an easy way to enumerate and
grep the list of all known, unresolved issues, and to access the latest
status of each.
Cheers,
Daniel
prev parent reply other threads:[~2020-05-21 16:31 UTC|newest]
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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200521163015.0b012455@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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
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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).