From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Fri, 27 Aug 2021 23:44:35 +0200 Message-ID: References: <87h7fcnmq0.fsf@posteo.net> <83tujbqg4j.fsf@gnu.org> <46353190-1190-495f-b15e-22980159b3ab@yandex.ru> <49df8478-3a2a-6607-9f8c-72ce806f3ea1@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28491"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, Daniel Fleischer , emacs-devel@gnu.org To: Dmitry Gutov , Stefan Monnier , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 27 23:45:59 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 1mJjfh-00076m-NZ for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 23:45:58 +0200 Original-Received: from localhost ([::1]:42532 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJjff-0002x6-Fc for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 17:45:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJjea-0002BX-G5 for emacs-devel@gnu.org; Fri, 27 Aug 2021 17:44:49 -0400 Original-Received: from out2.migadu.com ([188.165.223.204]:59963) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJjeU-0003Bg-0F; Fri, 27 Aug 2021 17:44:48 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1630100676; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4KYPnlrxcAvIygJwo4XiI0YIx7PYJe+7Lr+DZQ5QULY=; b=edK85ze6kGXabBk4zJuZimUH6rqB0orbxtK8qcUnBOPIlwwF8GYHfw48V2vxuM/2pZD3lB aS8pg5tp9N2qVa83TLYCo/Q6G3yrKr0t6KTbB7W0mcKf9cjJyEcaKgaCdUPKIqwRSndJtu /vEN9oY5kF1wTDqyhD46r0+158RVSbN4k7391ekUwhWhqRmW6kBTcKh7ybpPtd34aReNHP lddc1K1F6bpKiWgM46Lv8aCzkKfdOIEVrIKGuq11fyE0ehG2sWZeiKWw+qSlBgTbib6Jjd QYt612wyaUwyjslOLWCIB/JU31b+79LEhRyeeSoYXYPisXHsoOXPUT3t37pQQA== In-Reply-To: <49df8478-3a2a-6607-9f8c-72ce806f3ea1@yandex.ru> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: theo@thornhill.no Received-SPF: pass client-ip=188.165.223.204; envelope-from=theo@thornhill.no; helo=out2.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, 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:273189 Archived-At: Dmitry Gutov writes: > 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. > https://lists.sr.ht/~technomancy/fennel/patches/24386 This shows both a build that succeeded and an inline comment. More complicated stuff is likely still missing, but this seems to address part of what you were referring to, doesn't it? There's also examples where faling builds sends out notifications etc. I can try to find some of those, but that will be shooting in the dark until I find one... >> 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. > Yeah, I agree this is missing, at least if we're not willing to accept that this might not be the number one thing to need before migrating. >>> 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? You might be correct about this. No, he is a vim user, and seems a little negative towards emacs, as far as I can tell. Theodor