From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:] Date: Thu, 21 Nov 2019 15:00:49 +0000 Message-ID: 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: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="136408"; mail-complaints-to="usenet@blaine.gmane.org" Cc: =?UTF-8?Q?=C3=93scar_Fuentes?= , Lars Ingebrigtsen , Dmitry Gutov , Richard Stallman , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 21 16:01:23 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 1iXnxS-000ZFX-4K for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 16:01:22 +0100 Original-Received: from localhost ([::1]:41618 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXnxQ-0005wv-TE for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 10:01:20 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45668) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXnxI-0005wZ-E5 for emacs-devel@gnu.org; Thu, 21 Nov 2019 10:01:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iXnxG-0000hA-A6 for emacs-devel@gnu.org; Thu, 21 Nov 2019 10:01:12 -0500 Original-Received: from mail-il1-x12b.google.com ([2607:f8b0:4864:20::12b]:43447) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iXnxA-0000WA-Dx; Thu, 21 Nov 2019 10:01:04 -0500 Original-Received: by mail-il1-x12b.google.com with SMTP id r9so3531800ilq.10; Thu, 21 Nov 2019 07:01:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=v8Uc2r47EzAQohVXXz9k6s5Vg8WtNcL746QS/jOYiCo=; b=W/o5wB+73RoDcYXKUYScxKLjM0RHK89ycqLk7sF09D0hprZ0IzR18tTd46qAqMo01C khPTVrT1vhIas3GqqTw1+CeTf8yt87cg1Ui4uY+ulPhadfSgCmKieD+j/ND28xpqxhUz /rfZQIXvDNuaemXIWbHaJSM+ZQ3m9w07Y7v+A/KsmTFrQjn83sUByRNC50FUz5V41Su6 YTV9aEEO4Q2ELmR33RhNIFXxul/fAB7drW2V8j3St3cS78OTAXf75tJvs0j4RMkEigP8 gpT/U/GLbp759uojFRp71AbeNfRHt7DNE7tVQlgVdCUeRQRe+J4x01gbr4/C2nPCRvp0 Gl7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=v8Uc2r47EzAQohVXXz9k6s5Vg8WtNcL746QS/jOYiCo=; b=CW+pwu4BS1pHJSMoqFLST1yOIFAaZge7Co+wzB3Ivxfn53/IUwbG8gC5Rd13uX35oi 8NBcLi9puph2VJXko9TMJet/+WJy2ZAR0aVRIP3Tr2iOosliNVY0CKRVa1EVu9BlS8FJ sDcoJHVycFOriPFfLUBdf0P+1Pgedn/k/bB1yB0hX1HT7ibvEVIwyCRYzsHwAv1ItsPA f5M7o1bRp9DKLuyZLszD75re/ORPiMOU4xdzqb/yPPX9G9FiIhGwsqCzUqQ9NB3hcHib icGe+LIFe6PW0SYwF+fn2Rl1Y7eI0XQeJgGOtn9yIDXj/weI6tGGKZDtsyhk8GyFdQhD o44w== X-Gm-Message-State: APjAAAXMWk4AorpDe8BqBpcTXDUQ7Sj1mur7SM8Z+fO/wKBDV3wC/z2a jTZLwiiVQi+eSwd+Bwj62jqD7ZWCwUiiqCuJ8diKvyAB X-Google-Smtp-Source: APXvYqw82ypEBWS9TKTrV+EvzoMcDgGyJpcS6qatxYfpFCnWPHeJA9jH1FOrlu/8d4EyYB58w/OKjKCTJE5qRg7YcJU= X-Received: by 2002:a92:1513:: with SMTP id v19mr10281773ilk.125.1574348460684; Thu, 21 Nov 2019 07:01:00 -0800 (PST) In-Reply-To: <83sgmhxp1i.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::12b 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:242568 Archived-At: On Thu, Nov 21, 2019 at 2:49 PM Eli Zaretskii wrote: > > > From: Jo=C3=A3o T=C3=A1vora > > Date: Wed, 20 Nov 2019 20:12:28 +0000 > > Cc: Lars Ingebrigtsen , =C3=93scar 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. 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. 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. The way it would most closely reflect our current model is: * 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. We could enhance this later, of course, to reflect another organization within developers, for example. Jo=C3=A3o