From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Choice of bug tracker Date: Fri, 1 Sep 2023 00:24:12 +0300 Message-ID: <98fb089d-9bc2-eee1-7f74-7effce9fc44a@gutov.dev> References: <87il9kksqz.fsf@dfreeman.email> <87a5uw9ivs.fsf@posteo.net> <87ttt42gna.fsf@dfreeman.email> <87wmy080kn.fsf@posteo.net> <83v8djcydl.fsf@gnu.org> <87350ndquw.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87wmxj27fn.fsf@dfreeman.email> <831qfrptiq.fsf@gnu.org> <57429221-d9be-5791-e975-b3539905e2f6@gutov.dev> <83a5udlj47.fsf@gnu.org> <87a5udk1co.fsf@posteo.net> <835y51kslv.fsf@gnu.org> <7a82c524-1aa1-e755-e377-673ebb107a44@gutov.dev> <83r0nok8s4.fsf@gnu.org> <83ledwk4xi.fsf@gnu.org> <76ecf629-a41a-f6e4-f661-2ef926326d6c@gutov.dev> <83zg2cias7.fsf@gnu.org> <83pm37ie54.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4082"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: eliz@gnu.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 31 23:25:19 2023 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 1qbpAD-0000oe-76 for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 23:25:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbp9I-0007hi-Ja; Thu, 31 Aug 2023 17:24:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbp9G-0007fx-VN for emacs-devel@gnu.org; Thu, 31 Aug 2023 17:24:19 -0400 Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbp9E-0006Sn-3g; Thu, 31 Aug 2023 17:24:18 -0400 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 87CC65C010A; Thu, 31 Aug 2023 17:24:14 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 31 Aug 2023 17:24:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1693517054; x=1693603454; bh=PF6d2U8z6lp4yU02YIvbUBM8dK4/7uUyxXr n5pjqKaM=; b=k7B7LmNM+VYVabFoN7FTJrQMj+fjwNvuoa4lc8xdqo8MuOdHpa7 Ktc8OfTwjw4Ey1EVxwZIA1BQo8u2HhIBHRHNue9FrF1tMN2KxNhlmNXjIzZjoiBV VJbO1nu/5IXXldx6dKhbso+Ziro/Hk/yyNnlCBWXuF6rnpnYw68/J9hB5gtyServ eU0Xtw6/sO5BYXGy8EJkI9hCuBQuScPoPasU814IBgc8/2ZWHaxW+2cHg4yLZs4L Iwyi96ARsIdimWKoQybYSW9cul7tM8806ARF8A4AMBXRATLL/LgY9GUy/MUAP1Cb mjhnGQmO4cYtXPyP07zySP5NSARMtffFH/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693517054; x=1693603454; bh=PF6d2U8z6lp4yU02YIvbUBM8dK4/7uUyxXr n5pjqKaM=; b=QL/nvIHwHDLko20xgFBdxW6edaXCD09FwSWMulAOBn+qG/HPWNS Yb2OzPVE21gcX6aR+M7x3GLo0dt12w6rn5oF6+uhxiD7D5PHwesEq7qNh5y+pMgm emm8YaPFhLI3PasLHDU2WSFXSQT6abvrRpnHyGW8r9hBTaEoGpUdvuxpAZf/c24p ALPJHtc0YCndhp16rq+kBn5cNags0iOqsVEQOEmYtUvw6vKwwEm8M6OnL82Oy5j4 L8Cwjdp12Klbdjrwf5llhKVTe0DbENX78BZo0hUf11TM1uEZ9AqOuuyrjDnm8w57 4kGT7deDD+Xq7wqqkRGb2HkNLRy+yA7ZL1g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudegtddgudeivdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvvehfhfgjtgfgse htjeertddtfeejnecuhfhrohhmpeffmhhithhrhicuifhuthhovhcuoegumhhithhrhies ghhuthhovhdruggvvheqnecuggftrfgrthhtvghrnhepiefgteevheevveffheeltdeuke eiieekueefgedugfefgefhudelgfefveelvdevnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepughmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 31 Aug 2023 17:24:13 -0400 (EDT) Content-Language: en-US In-Reply-To: Received-SPF: pass client-ip=66.111.4.28; envelope-from=dmitry@gutov.dev; helo=out4-smtp.messagingengine.com X-Spam_score_int: -62 X-Spam_score: -6.3 X-Spam_bar: ------ X-Spam_report: (-6.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-3.478, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309701 Archived-At: On 31/08/2023 05:07, Richard Stallman wrote: > The Gitlab software ls a different issue. I gather that it is all > free software, so there is no bar to our installing it on a server and > running it. If Gitlab.com changes its policy, we could continue running > the previous version of the software, or else patch their release. When we talk about trying Gitlab, we mean this approach. We already have an experimental instance running on GNU's servers, after all. The aforementioned EMBA. > Regarding using an email responder to file submissions in a server: > > > The main limitation, however, is that this design requires people to > > create accounts in the system. Even just to file new reports. > > If a server requires that, that is a major negative. Aside from being > a nuisance for each person to start to use, it also infringes each > user's privacy. > > Worse, if the site requires that, it may also require running nonfree > Javascript to create an account. That would be morally unacceptable: > we can't direct users to run nonfree programs. > > If the site does not do that now, will it start some years from now? > Will it start using Cloudflare, which requires nonfree Javascript for > users coming in through the Tor network? If the developers don't > share our values, we have to treat that as a permanent danger. Again, we're talking about a self-hosted solution. The (apparently solved) issue of reCaptcha was mentioned upthread (there is now a setting which switches to a different, simpler method that doesn't use Google's solution). > I have a possible workaround for all of that. Could we use one single > account GNU-EMAIL to file all email submissions, and record who really > sent each submission (obtained from the From field) in another data > field in the submission? I don't know about the feasibility of saving the "From" value into another data field in the same database, but whatever piece of code would be running the "one single account" could potentially maintain a database of associations between bug reports and email accounts (reporters). But that's an open-ended feature, e.g. at some point people will want to be able to unsubscribe from email follow-ups in those threads, and we would be required to add that feature too (maybe even by law). We're talking about a mailing list software, basically. > If the site developers care about us a little, they could add a > feature to use the From-field submitter, for display and search, > instead of the account name, when that latter is GNU-EMAIL. > > (With a little more work they could make this feature more elegant and > general, so other projects could do likewise. Each would make its own > account for email submissions. We could release the email responder > program as a GNU package so they couid use it.) Looking at past reports, Gitlab developers do discuss our issues and fix some of them, but not all, and not right away. Which seems logical overall. Speaking of privacy, though, not exposing everybody's unobfuscated email addresses to the web is considered a privacy advantage in many contexts. That helps avoid spam, and it helps tracking an individual across the Web a little more difficult (because for every platform the searches would at least have to work out the specific way every given site obfuscates the emails, if they're available at all). OTOH, having to create an account doesn't seem to create any additional privacy risks, if we're only asking for email, password, and the account verification using said email.