Re: Gnus backend for GitHub/GitLab?

["Adam Sjøgren" <asjo@koldfront.dk>]

Adam 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

So, I have gotten a little further on this - I have some code that
allows me to list projects as groups in Gnus, and to show issues of a
project as articles in a summary.

It's fairly straight forward (using ghub.el).

However, there is a snag.

I *really* like the mapping sketched out above, where each GitLab
project maps to a newsgroup, and each issue/comment maps to an article/a
follow up.

But... the numbering. GitLab numbers issues within a project 1, 2, 3,
... - as you, and a newsgroup, would expect.

However, comments on an issue are numbered 1, 2, 3, ...

Whoops. I would like them to be follow ups _in the same group_. So they
need to map to article numbers in the same group.

Ouch.

Any good ideas on how to handle this?

My first thought was "oh, just add a billion to the global comment id",
but I seem to remember that newsreaders aren't really happy about huge
gaps, and you wouldn't know when new issues arrived, only when new
comments did.

I could have a group per issue, which holds the comments, but that's
also a major mismatch with the newsreader-model.

I can't see any good solution :-/


  Best regards,

    Adam

-- 
 "More than anything, I won't try"                          Adam Sjøgren
                                                       asjo@koldfront.dk