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 16:49:29 +0200 Message-ID: <83sgmhxp1i.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> 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="85690"; 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 15:50:06 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 1iXnmX-000M87-GH for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 15:50:05 +0100 Original-Received: from localhost ([::1]:41548 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXnmV-0000rJ-Rc for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 09:50:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43714) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXnlu-0000rA-KX for emacs-devel@gnu.org; Thu, 21 Nov 2019 09:49:27 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60648) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iXnlu-0001Ph-0w; Thu, 21 Nov 2019 09:49:26 -0500 Original-Received: from [176.228.60.248] (port=4954 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iXnlm-0007sZ-7a; Thu, 21 Nov 2019 09:49:18 -0500 In-reply-to: (message from =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= on Wed, 20 Nov 2019 20:12:28 +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:242566 Archived-At: > From: João Távora > Date: Wed, 20 Nov 2019 20:12:28 +0000 > Cc: Lars Ingebrigtsen , Óscar Fuentes , > emacs-devel , Richard Stallman , Dmitry Gutov > > > > Well, yeah, but from the contributor's side the process is very > > > similar. Apart from not being able actually merge the PR > > > to master, he changes the PR's branch in the very same > > > ways as I (the developer) described in my previous email. > > > > That branch _is_ the problem. You don't want that to be a branch in > > our upstream repository. > > Why don't you? 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. > As an Emacs developer, I create branches under scratch/ > very frequently. You are trusted with write access to our repository, and you obtained that trust after some initial period whereby we took a good look at your coding and documenting practices, and made sure you are aware of our conventions, standards, do's and dont's. By contrast, J.R. Hacker from out there was never subject to such scrutiny, and could make serious mistakes, or even do something evil on purpose. So we will need to set up a mirror repository somewhere. the current best idea is to host that on savannah.nongnu, I think.