From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/88871 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Adam_Sj=C3=B8gren?= Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus backend for GitHub/GitLab? Date: Wed, 20 Nov 2019 13:38:44 +0100 Organization: koldfront - analysis & revolution, Copenhagen, Denmark Message-ID: <874kyyhgdn.fsf@tullinup.koldfront.dk> References: <8736ejsehi.fsf@tullinup.koldfront.dk> <87v9reixy3.fsf@gnus.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="148968"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+M37075@lists.math.uh.edu Wed Nov 20 13:39:39 2019 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iXPGl-000cbp-Q2 for ding-account@gmane.org; Wed, 20 Nov 2019 13:39:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92.3) (envelope-from ) id 1iXPGC-00005e-0X; Wed, 20 Nov 2019 06:39:04 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iXPG7-0008Ud-SN for ding@lists.math.uh.edu; Wed, 20 Nov 2019 06:38:59 -0600 Original-Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iXPG6-0000vn-GD for ding@lists.math.uh.edu; Wed, 20 Nov 2019 06:38:59 -0600 Original-Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226] helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iXPG0-0007ZD-BR for ding@gnus.org; Wed, 20 Nov 2019 13:38:54 +0100 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iXPFy-000buD-PO for ding@gnus.org; Wed, 20 Nov 2019 13:38:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ OpenPGP: id=476630590A231909B0A0961A49D0746121BDE416; url=https://asjo.koldfront.dk/gpg.asc Mail-Follow-Up-To: never X-Face: )qY&CseJ?.:=8F#^~GcSA?F=9eu'{KAFfL1C3/A&:nE?PW\i65"ba0NS)97,Q(^@xk}n4Ou rPuR#V8I(J_@~H($[ym:`K_+]*kjvW>xH5jbgLBVFGXY:(#4P>zVBklLbdL&XxL\M)%T}3S/IS9lMJ ^St'=VZBR Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:88871 Archived-At: Lars writes: > Adam Sjøgren writes: > >> It hit me that accessing comments on GitHub/GitLab seems like an obvious >> candidate for a Gnus backend. >> >> * GitHub/GitLab-instance: a Gnus server >> * Each project you're interested in: a subscribed group >> * Each issue: a top-level article >> * Each comment: replies to issues/other comments >> * Label, State ...: headers that can be edited > > That would indeed be nice, but the main problem with the APIs that > Gitlab provides is that... they're very chatty and aren't geared > towards "show me what's changed since " (which is what Gnus thrives > on). I think this is what Michael Albinus addressed - in an email that seems to be stuck in the mailing list flow somewhere - where he wrote: GET /projects//issues?scope=all&updated_after=2019-11-19T13:22:55.640Z is your project id. Best regards, Michael. That might be useful? Anyway, I intend to use this against quite small projects (i.e. not Emacs sized, but more in the thousands of issues). > This means that you have to issue a whole bunch of API requests just to > get the basic info, which means that things get very s-l-o-w. Are you thinking of having to fetch all comments for all issues again and again, or? I *am* worried about ending up with yet-another-nnslashdot backend, which is so dog slow that it is unusable... > But I've just skimmed the Gitlab API documentation; perhaps it has > what's needed to make things go fast. Alternatively I could build a "gitlab_to_nntpd", but I think the integration (especially with changing labels and status by editing articles, rather than superseding), would be easier/better if it is a backend that Gnus knows that editing directly works for? Another thing I was thinking was that maybe nngitlab could build upon the code in Magit Forge that already exists to talk to the APIs... but given my level of familiarity with elisp, I might just start attempting the simplest possible. Best regards, Adam -- "I wish *I* was a tiger!" Adam Sjøgren "A common lament." asjo@koldfront.dk