unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: debbugs.gnu.org: is it user-centric or developer-centric?
Date: Wed, 19 Nov 2014 18:37:13 +0000	[thread overview]
Message-ID: <87bno33uli.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <m38uj7p0h8.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 19 Nov 2014 18:24:35 +0100")

	Could someone please clarify on the proper usage of
	debbugs.gnu.org?  Specifically, per my prior experience with the
	Debian BTS, the issues which the developers do not consider
	worth fixing, but which are otherwise valid, are tagged
	‘wontfix’, but /not/ closed.

	The rationale behind that is that the issues both remain visible
	to the /users/ of the package, /and/ are known to be “dealt
	with” (in a way) to the developers.

	Recently, two of my bug reports filed against Emacs (#17959 and
	#19109, specifically) were closed without the issues being
	actually fixed.  This makes them eligible for archiving, which
	will hide them from the (default) BTS view.

	Granted, Debian BTS was established to serve /both/ the
	developers /and/ the users of the package (or at least it’s my
	reading of the Debian Social Contract.)  I thus wonder if my
	experience is applicable to the Debbugs instance run by the GNU
	project; or if that instance is instead targeted primarily at
	developers, and thus merely sharing the knowledge of the
	existing issues (including those arising from some “singular
	usage pattern”, so to say) among the users is out of its scope?

	TIA.

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

 >>> So I'm closing this.

 >> I have no objections to classifying this as ‘wontfix’, but I’d
 >> rather keep this opened for the issue to remain visible to the
 >> community.  (FWIW, http://debbugs.gnu.org/ hides closed issues by
 >> default.)

	I stand corrected: merely closing the bug doesn’t hide it from
	the public view.  However, it makes the bug eligible for
	archiving, and the archived bugs /do/ get hidden by default.

 > That's the point of closing bugs reports -- so that other maintainers
 > don't have to bother with them.

	Wouldn’t ‘wontfix’ be enough for that?

 > Closing again.

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A



       reply	other threads:[~2014-11-19 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mwcmb8nx.fsf@violet.siamics.net>
     [not found] ` <m31tpaiwgo.fsf@stories.gnus.org>
     [not found]   ` <87r3wz7h0e.fsf@violet.siamics.net>
     [not found]     ` <m38uj7p0h8.fsf@stories.gnus.org>
2014-11-19 18:37       ` Ivan Shmakov [this message]
2014-11-19 18:53         ` debbugs.gnu.org: is it user-centric or developer-centric? Glenn Morris
2014-11-19 19:27           ` Ivan Shmakov
     [not found]     ` <877fxricgb.fsf_-_@violet.siamics.net>
     [not found]       ` <87fvbfy8xv.fsf@violet.siamics.net>
     [not found]         ` <87mw4ndny0.fsf_-_@violet.siamics.net>
2015-12-25 19:00           ` bug#19822: url-retrieve: allow to fail when no document is associated with the URI Lars Ingebrigtsen
2015-12-25 23:47             ` Drew Adams
     [not found]           ` <87r3iawdyl.fsf__1890.34737782112$1451070147$gmane$org@gnus.org>
2015-12-28 22:07             ` Ted Zlatanov
2015-12-28 22:30               ` Lars Ingebrigtsen

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87bno33uli.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=emacs-devel@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.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).