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: Gitlab Migration Date: Sat, 28 Aug 2021 00:35:44 +0300 Message-ID: <49df8478-3a2a-6607-9f8c-72ce806f3ea1@yandex.ru> References: <87h7fcnmq0.fsf@posteo.net> <83tujbqg4j.fsf@gnu.org> <46353190-1190-495f-b15e-22980159b3ab@yandex.ru> 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="32077"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 Cc: philipk@posteo.net, Daniel Fleischer , emacs-devel@gnu.org To: Theodor Thornhill , Stefan Monnier , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 27 23:37:52 2021 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 1mJjXs-0008Ab-3e for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 23:37:52 +0200 Original-Received: from localhost ([::1]:37262 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJjXq-0007U9-Kb for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 17:37:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35562) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJjVu-0005SE-Jw for emacs-devel@gnu.org; Fri, 27 Aug 2021 17:35:51 -0400 Original-Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]:44937) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mJjVs-0005xp-PZ; Fri, 27 Aug 2021 17:35:50 -0400 Original-Received: by mail-wr1-x42a.google.com with SMTP id g18so4882213wrc.11; Fri, 27 Aug 2021 14:35:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2RkdaPF3gaIOe+HSDiPT5qUCRT23uFXUMxToB7HxnOY=; b=tX45SvQsP2VbdoFLy/LolHEmMB8eZbhN9MsMrChUnOYyfwmhCaek1BQz7Ak93cLLwo MwrGZkKxlsOu69lNVl+u2Te+xUJcfCqwz/+9BEoEboN6PU5R8b0jwaa9MxCs73d4BVdy ddWbvAbeAuN4NOhjxxkGKtlVi0Ar0znHip19MuKTdanNqfdmdbVAUxLLqw2oWk42Po1K OFfR9+EUvIlz7dhP85PtN5TkTSGPOc//zsIZIc+QjkOGr/nCKFfTezjPputU533N/v78 g3AcOFfk1mFIQk5rRtlYXSQzZP6E6gId7NL/HGzc+jG9FYFILLh/MQa5QLweuuywmYTt OuFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2RkdaPF3gaIOe+HSDiPT5qUCRT23uFXUMxToB7HxnOY=; b=mtGvtD8WtjCruVPl9cjgstdh/s1MLahZnikssrSz6lV+hNbDMTwJOsVIZNUL5+YjJ8 MqzAGdMI7i9UaLVIEVXGsh4yYWby3bfxQLt9yxIniTqLWQrhY6WD7Wo591KLom7sbtTR Op+beUMevkRWUVGKtMrWEy9E9CLzjs2W1BdumUJy41ENY0G6UmF1r+LhAehtiZfCxZmU I0MJJKWlnHamNy6InHH9qAorZHy1C4yN/ifbqLwdWhcNPVEWamdm+usAcIhx+LHzW7HY /C0LNvgRJJuxmoXWOsROxyxLLWZ1hDA9+5DJI1xvNimU94M8dE5LtUtWM2AEm3tcAu0K fI+g== X-Gm-Message-State: AOAM532nbL9AGPWUeleQh+0O2GQsn4IrQoSUEe9nPE6vy6K9DDmLsENW OP11HSpxmqYPZRL5T4bixJP1b8XcZRE= X-Google-Smtp-Source: ABdhPJxzYZV1lVvDPtCFQMtUY2FK7u8CQZDQWfwRurrcPQhHc+xn9AgkLtCTXw5RgFw8SzjU2Pb+SA== X-Received: by 2002:adf:8006:: with SMTP id 6mr12844679wrk.38.1630100146808; Fri, 27 Aug 2021 14:35:46 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id k18sm12258406wmi.25.2021.08.27.14.35.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Aug 2021 14:35:46 -0700 (PDT) In-Reply-To: Content-Language: en-US Received-SPF: pass client-ip=2a00:1450:4864:20::42a; envelope-from=raaahh@gmail.com; helo=mail-wr1-x42a.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.437, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273188 Archived-At: On 28.08.2021 00:17, Theodor Thornhill wrote: >> From what I have seen of it, it's email-first, and far from "full and >> convenient support for ... web". >> >> For example, those quality-of-life features that Gitlab has in the >> browser which I previously figured would be difficult to translate to >> email (the code review workflow, with inline comments and updates from >> the branch; automatically updated CI indicators and links to builds; >> editing of messages) are predictably absent. > > This isn't really true though. It seems substantially true. > There definitely are links to builds and There's no such examples on the home page (and it does have a link to a page supposed to resemble a code review). If you have a better link, please share. > inline comments. Inline comments like quoting parts of an attached patch inline in an email, which we've been doing for decades in emacs-devel? That's not even close to a dedicated code review UI. > Though I agree on parts of this. One missing thing as > I see it is the updated patch. You need to find the latest patches, and > it won't update as in GitHub when you add another "oops" commit. The review UI would need to be tied to a particular branch, instead of some file attachments. And happen not in a email client, but either in a browser, or perhaps some re-implementation of the same UI inside Emacs. >> Of course, it should still be a significant step forward compared to the >> current situation. > > Yeah. One might also think that some contributions could trickle down > to sourcehut itself when emacs workflow settles, so the "github way" of > contributing could get a little love? I doubt that: since the system is email-first, it would likely be hard to promote/upstream features that don't translate well to email. Even if someone writes an Emacs UI for them. Does Drew use Emacs?