From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: Migrating to sourcehut - what's missing? Date: Tue, 21 Dec 2021 10:58:28 -0800 Message-ID: <87v8zh6azv.fsf@ericabrahamsen.net> References: <871r26w27h.fsf@thornhill.no> <87lf0dq08j.fsf@thornhill.no> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24803"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:C4bxCU3pzjKs9hm+t7oLlXa8SW4= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 21 19:59:24 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 1mzkM6-0006CV-OQ for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Dec 2021 19:59:22 +0100 Original-Received: from localhost ([::1]:58288 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mzkM5-0003uG-6m for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Dec 2021 13:59:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:54992) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mzkLZ-0003Fq-1Q for emacs-devel@gnu.org; Tue, 21 Dec 2021 13:58:49 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:46286) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mzkLX-0007Dg-En for emacs-devel@gnu.org; Tue, 21 Dec 2021 13:58:48 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mzkLL-0005AB-6a for emacs-devel@gnu.org; Tue, 21 Dec 2021 19:58:35 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:282619 Archived-At: Theodor Thornhill writes: >>> Is there still interest in moving over to Sourcehut for emacs >>> development? >> >> My understanding is that the answer is yes. AFAIK, no final decision >> has yet been taken, but it seems like the consensus is more or less that >> sourcehut is the most likely candidate to have what we need within some >> reasonable time-frame. >> > > Good to hear. I think it would be stupid to decide this without trying > it properly first anyway. > >>> I'm planning to look into this myself a little during the holidays, but >>> not sure how much time I realistically can spend on this, so therefore >>> this mail. Possibly it may be useful if someone other than me wishes to >>> tackle this over the holidays? In general they are pretty responsive >>> over at #sr.ht, so they might be willing to help out a little. >> >> I would personally start with setting up a sourcehut instance with a >> mirror of the Emacs source code. This would allow you to start >> experimenting with it to see how it works and what is missing. In this >> work, I would specifically compare the sourcehot workflow to what we >> have now. If you could make the instance publicly accessible, other >> interested parties could help with this work more easily. >> > > Workflow-wise I believe it already is established that sourcehut > supports most if not all aspects of the emacs development workflow, > modulo the patch-rendering issue when patches are sent as attachments. > One of the biggest improvements would be to set up builds on patch > submission, running tests etc. All of this works properly in Sourcehut. > >> Preferably any gotchas when installing should be noted down somewhere >> (e.g. sent to emacs-devel). >> >> Next, I would start looking into those things that are still missing. >> For starters, they would need to be listed and it should be ensured that >> there are good feature requests on the sourcehut issue tracker. If the >> sourcehut developers are willing to implement those things then great, >> otherwise it would be obviously be very useful if someone would >> volunteer to start working on those things. >> > > Actually, I think that running Sourcehut as a local instance wouldn't > really be necessary for the evaluation, because it is the same code that > is running on sr.ht. Apart from the fiddly bits with self hosting, the > workflow should be the same. I'd encourage people on this list getting > their own user there and trying it out, as I think many already have. > Specifically, emacs-devel would want to use the `meta`, `lists`, `git`, > `todo` and `builds` subprojects, that is all apart from the `hg` one. I wonder if it would make sense to have one of the maintainers sign up there and start a "pretend" official Emacs repo. They could start a mailing list alongside it that we could play with, and who knows, maybe that would eventually become the "real" official sr.ht repo. Eric