From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: non-gnu elpa issue tracking Date: Sat, 12 Dec 2020 00:34:01 -0500 Message-ID: References: <20201209125516.lenqswi7fhiscbr2@E15-2016.optimum.net> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37705"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, boruch_baum@gmx.com, bugs@gnu.support, stefankangas@gmail.com To: thibaut.verron@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 12 06:36:12 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knxZj-0009g1-Ng for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 06:36:11 +0100 Original-Received: from localhost ([::1]:56630 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knxZi-0003Kc-NX for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 00:36:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36364) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knxXj-00029k-7r for emacs-devel@gnu.org; Sat, 12 Dec 2020 00:34:08 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41757) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knxXi-0007za-Jb; Sat, 12 Dec 2020 00:34:06 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1knxXd-0001VD-7o; Sat, 12 Dec 2020 00:34:01 -0500 In-Reply-To: (message from Thibaut Verron on Fri, 11 Dec 2020 12:10:13 +0100) 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:260707 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > As far as I remember from a previous discussion, it is possible to use > github with javascript disabled, but creating an account requires > running non-free javascript for the captcha. And it is not possible to > open or comment on issues without an account. Assuming someone who knows for certain confirms that information, I have to conclude that reporting bugs via GitHub comments is not an ethical way to accept bug reports. We cannot direct users to report bugs in the package that way. We should edit the README file to remove that. But there are other kinds of arrangements we can ask to make with the package developers, such as * The developers check bug-gnu-emacs for reports about their package. * Establish an email address which will forward to them, and give that as the way to report bugs in that package. * A volunteer relayer who already has a GitHib account checks bug-gnu-emacs for reports about that package, and enters them in GitHib as comments. The developers will have to reach the OP by email -- the relayer would not want to keep relaying every conversation for its whole length. If the developers propose something else, and it meets the moral requirements and isn't too much work, and we can do it, we should be flexible. I expect most packages won't get a bug report every month. -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)