From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Thu, 21 Nov 2019 20:26:15 +0200 Message-ID: <83blt5xf08.fsf@gnu.org> References: <20191117113054.49837.qmail@mail.muc.de> <87pnhq7mxg.fsf@gnus.org> <87bltaz9g4.fsf@telefonica.net> <834kz25qp9.fsf@gnu.org> <87y2wexsv1.fsf@telefonica.net> <83sgmm4a08.fsf@gnu.org> <87h832xqxr.fsf@telefonica.net> <20191117192558.GC11551@ACM> <87a78uxot6.fsf@telefonica.net> <87a78uuvde.fsf@gnus.org> <8853390e-f4a5-c295-4f94-cf417ec8db5f@yandex.ru> <83wobv2684.fsf@gnu.org> <878soakddl.fsf@gnus.org> <83wobuzf8y.fsf@gnu.org> <83lfsazbmu.fsf@gnu.org> <83ftiiz57k.fsf@gnu.org> <83sgmhxp1i.fsf@gnu.org> <83mucpxo28.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="233093"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ofv@wanadoo.es, larsi@gnus.org, dgutov@yandex.ru, rms@gnu.org, emacs-devel@gnu.org To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 21 19:28:44 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 1iXrC7-000yTd-JV for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 19:28:43 +0100 Original-Received: from localhost ([::1]:44802 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXrC6-0003Co-9p for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 13:28:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53979) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXr9k-0001x7-MC for emacs-devel@gnu.org; Thu, 21 Nov 2019 13:26:17 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36572) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iXr9h-00072Y-Pn; Thu, 21 Nov 2019 13:26:13 -0500 Original-Received: from [176.228.60.248] (port=2342 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iXr9Y-0006f8-Ss; Thu, 21 Nov 2019 13:26:06 -0500 In-reply-to: (message from =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= on Thu, 21 Nov 2019 15:30:01 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:242587 Archived-At: > From: João Távora > Date: Thu, 21 Nov 2019 15:30:01 +0000 > Cc: Lars Ingebrigtsen , Óscar Fuentes , > emacs-devel , Richard Stallman , Dmitry Gutov > > > which will make it be hosted on > > the same machine where our upstream repository lives. And then who's > > to say that such branches pushed into our GitLab are not part of > > Emacs, like all the scratch branches you and others push now? > > Is that question really important? Yes. Because by hosting code that violates some copyright we could make GNU liable. Or if someone, by mistake or malice, pushes code that is against the GNU policies, we could make it easy for enemies of GNU to attack and discredit GNU. Etc. etc. > And why does it not apply to patches as potentially absurd or as > harmful as those branches that are sitting in email bodies of the > debbugs bug tracker and the archives of lists.gnu.org? Because an email message is from someone who offers us code, wheres code on our server is already on our server, in our repository, even if it's a fork. Thus, people who don't understand these technicalities could easily be convinced that we "endorsed" that code. > But what does that risk amount to, i.e. what are > the consequences of someone making that mistake? In our present chaotic world, the consequences might be dire. And I really don't understand the need for trying to do it on Savannah, when savannah.nongnu is a good compromise that solves this problem. Why should anyone care on what server is this tracker hosted?