From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Memnon Anon Newsgroups: gmane.emacs.devel Subject: Re: Emacs project mission (was Re: "If you're still seeing problems, please reopen." [ Date: Fri, 29 Nov 2019 09:17:02 +0000 Message-ID: References: <20191117113054.49837.qmail@mail.muc.de> <87pnhq7mxg.fsf@gnus.org> <87bltaz9g4.fsf@telefonica.net> <834kz25qp9.fsf@gnu.org> <87y2wexsv1.fsf@telefonica.net> <20191118175639.08d02820@jabberwock.cb.piermont.com> <874kz0pa9y.fsf@gnus.org> <87sgmjyn60.fsf@gmx.de> <87imnezyt5.fsf@gmx.de> <481a1f16-d661-0f96-2f45-3d5ec9c1132e@yandex.ru> <749d3c85-ecd0-5d4e-b9fc-6405c2ca2334@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="201974"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 01 13:30:38 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ibON4-000qPE-AL for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 13:30:38 +0100 Original-Received: from localhost ([::1]:50910 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibON2-00035O-Sb for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 07:30:36 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44529) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibOMd-000333-8L for emacs-devel@gnu.org; Sun, 01 Dec 2019 07:30:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibOMc-0003fC-7k for emacs-devel@gnu.org; Sun, 01 Dec 2019 07:30:11 -0500 Original-Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:50994 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ibOMc-0003Nk-0b for emacs-devel@gnu.org; Sun, 01 Dec 2019 07:30:10 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1ibOMT-000piy-T5 for emacs-devel@gnu.org; Sun, 01 Dec 2019 13:30:01 +0100 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:qw2AbJwNVpDFghezBbKphfO+UTo= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242953 Archived-At: Richard Stallman writes: > > Whereas in most other projects both the repository and the bug tracker > > the public and visible, and easy to observe that development work is > > going on, recent reports are being handled, meaning they are welcome, > > and whatever grievances the user has have the possibility to be fixed. > > This is an argument that users often would _like_ to look at the bug > tracker. They don't _need_ it, but having it would motivate them. FWIW, I was always under the impression that, before you even consider writing a bug report, it is good manners to check, whether the issue is already reported, or perhaps solved in the dev branch. Searching "proper bug reporting", the first thing I get is: How to write a good bug report: step-by-step instructions 1. Isolate bug. The first step in in writing a bug report is to identify exactly what the problem is. ... 2. Check if you are using the latest version. Bug reports should be based on the the latest development build . ... 3. Check if the bug is known. . ... Memnon