Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Wed, 20 Nov 2019 13:38:44 +0100	[thread overview]
Message-ID: <874kyyhgdn.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87v9reixy3.fsf@gnus.org>

Lars writes:

> Adam Sjøgren <asjo@koldfront.dk> 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 <foo>" (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/<id>/issues?scope=all&updated_after=2019-11-19T13:22:55.640Z

    <id> 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
 




  reply	other threads:[~2019-11-20 12:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 22:11 Adam Sjøgren
2019-11-20  3:31 ` Eric Abrahamsen
2019-11-20  4:12 ` dick.r.chiang
2019-11-20 11:33 ` Lars Ingebrigtsen
2019-11-20 12:38   ` Adam Sjøgren [this message]
     [not found]     ` <87h82ywu6i.fsf@gmx.de>
2019-11-20 15:01       ` Adam Sjøgren
     [not found]         ` <87h82yvb7r.fsf@gmx.de>
2019-11-20 15:35           ` Adam Sjøgren
2019-11-21 12:31     ` Lars Ingebrigtsen
2020-01-14 20:42 ` Adam Sjøgren
2020-01-14 21:23   ` dick
2020-01-14 22:03     ` Adam Sjøgren
2020-01-14 22:18       ` dick
2020-01-14 22:45         ` Adam Sjøgren
2020-01-15  4:47           ` dick
2020-03-17 11:03             ` dick.r.chiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kyyhgdn.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).