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 17:10:39 +0200 Message-ID: <83mucpxo28.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> 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="179614"; 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 16:10:46 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 1iXo6Y-000kR9-0I for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 16:10:46 +0100 Original-Received: from localhost ([::1]:41700 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXo6W-0003Yu-Pm for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 10:10:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47478) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXo6Q-0003WC-4k for emacs-devel@gnu.org; Thu, 21 Nov 2019 10:10:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:32821) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iXo6O-0000jw-Uo; Thu, 21 Nov 2019 10:10:36 -0500 Original-Received: from [176.228.60.248] (port=2269 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iXo6H-0004sc-JM; Thu, 21 Nov 2019 10:10:30 -0500 In-reply-to: (message from =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= on Thu, 21 Nov 2019 15:00:49 +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:242571 Archived-At: > From: João Távora > Date: Thu, 21 Nov 2019 15:00:49 +0000 > Cc: Lars Ingebrigtsen , Óscar Fuentes , > emacs-devel , Richard Stallman , Dmitry Gutov > > > Because then anyone could push code to our main repository, even > > without having write access, and we don't want to host code we didn't > > eyeball in advance: it might include stuff we don't want to have > > anywhere close to Emacs, or to GNU in general. > > Right, certainly. But in the GitLab/GitHub model, there is that > main repository, which is your duty to protect, and also > isolated from it, one for each "JR Random Hacker", a _fork_ > (maybe Gitlab calls it a "clone") that JR can randomly hack > away in. That fork lives in the Emacs GitLab instance. It > does take some disk space there, but that's pretty much > it as potentially unwanted impact goes. I think we are miscommunicating. Let me ask you: where do you envision the "Emacs GitLab" will be installed? on what server? The most appropriate one is Savannah, 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? > JR's code is never merged to the main repository without your > or some developer's explicit approval. GitLab has a > sophisticated permissions system that states exactly what an > owner, a maintainer, a developer and a potential contributor > can do to the main repository. That's not the real problem. The real problem is not to make random code appear as being part of Emacs, and part of GNU. they are all on the GNU Git server, right? > * everybody can create issues (i.e. bugs) in the main > repository > * everybody can fork the main repository > * everybody can make pull requests to the main repository. > * every developer that currently has write access can > change and eventually merge the pull requests from > everybody else. You are thinking about technicalities, which are not the main problem here.