From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Tue, 19 Nov 2019 19:31:15 -0800 [thread overview]
Message-ID: <87zhgr9qbg.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8736ejsehi.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Watching this video about Magit Forge:
>
> · https://cestlaz.github.io/post/using-emacs-62-magit-forge/
>
> 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
>
> I guess Pull/Merge Requests could also be articles in the group, only
> with other default headers shown.
>
> So what I am thinking of is, say, nntp+gitlab.com:bashrc2.epicyon as the
> group, for instance, with articles:
>
> [Klaus Alexander Seistrup] User and status links: reorganisation?
> [Alex Schroeder ] System load
> [Bob Mottram ]
> [Alex Schroeder ]
> [Bob Mottram ]
> [Bob Mottram ]
> [Bob Mottram ]
> [Alex Schroeder ]
> [Bob Mottram ]
> [Bob Mottram ]
>
> (Mapped from https://gitlab.com/bashrc2/epicyon/issues)
>
> Something like that.
>
> Closing an issue could be editing the root-article and updating a
> "Status:" header from "open" to "closed". Changing labels would be
> editing the "Keywords:" header. Deleting would be cancelling the
> article. Creating a new issue: posting a new article. Commenting
> following up.
>
> For public projects you could use scoring to ignore comments from
> trolls. Or bulk delete spam.
>
> I think Gnus would be better suited to this than Magit Forge. Well, if
> you're using Gnus anyway, anyway.
>
> If I had a backend like this, I could turn off notification emails from
> GitLab at work, and I would never have to use the web-interface.
>
> (Well, Gnus would have to support Kerberos in web-requests, so I could
> see the images in the issues, but except for that.)
>
> The more I think about this, the more I like it. Gnus all the things!
>
> What do you think?
I think it's exhausting just to imagine the amount of work that would
take :)
But in principle I think it's a great idea, and I definitely think we
should be pushing the boundaries of what counts as a Gnus server. So many
things could be thought of as groups of sequential messages.
I look forward to your code!
Eric
next prev parent reply other threads:[~2019-11-20 3:31 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 [this message]
2019-11-20 4:12 ` dick.r.chiang
2019-11-20 11:33 ` Lars Ingebrigtsen
2019-11-20 12:38 ` Adam Sjøgren
[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=87zhgr9qbg.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).