[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nix-dev
Subject:    Re: [Nix-dev] Too many open issues
From:       Roland Koebler <rk-list () simple-is-better ! org>
Date:       2016-07-24 10:19:48
Message-ID: 20160724101948.GA24100 () localhost
[Download RAW message or body]

Hi,

as a Nix user: I think that it's a *very* *very* bad idea to auto-close
issues after 14 days. Usually, if I find a bug, I report it. If my
bugreport then gets auto-closed after a few days/weeks, it would feel like 
(a) the maintainers simply don't care about bugs (and prefer to ignore
    bugs rather than fixing them), and
(b) that bugreports are undesirable.

> All the *real* issues will stay active, since people will reopen them.
No.
As a "normal user", I probably wouldn't ever reopen a bug.
("I have submitted a bug; if it was closed, the maintainers probably
solved it or closed it for a good reason.", or
"I have submitted a bug. Why should I tell them 14 days later that the
bug still exists? Do they think bugs magically disappear? WTF?")

As a more experienced user, I *might* re-open it once, but when it's
auto-closed again, I would be very annoyed, wouldn't report any more
bugs (since obviously the maintainers don't care), and probably go
away (since obviously the maintainers don't care about bugs; and I
don't want to use software where the maintainers don't care about
bugs). This is NOT, what NixOS needs (at least in my opinion).

In my opinion, auto-closing would be ok for:
- bugs which cannot be reproduced easily and need more information,
  but the submitter does not submit this information, and
- bugs about packages which are no longer in Nix

All other bugreport-handling-problems should be solved by filtering,
searching or tagging bugreports, but not by (auto-)closing them.


just my 0.02ct
Roland
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[prev in list] [next in list] [prev in thread] [next in thread]