Support for Sourcehut's API would be awesome (especially since they also are big fans of being able to work offline)

Fair warning, this is something that will only exist if somebody sit down and actually do it. I don't have the bandwidth for it.

wow, came here to post this one too.

But thanks to https://sr.ht/~emersion/hut/ I'll be able to jump on this one doing one of the live streams and smash out something. Could possibly look into BTS, sourceforge, Savannah, GNATSweb, and debbugs if there is an interest.

Could possibly look into BTS, sourceforge, Savannah, GNATSweb, and debbugs if there is an interest.

The gitea integration (#80) might be worthwhile, seeing how it's probably among the most used platforms.

gitea

Gitea is ok and already has a cli tool https://gitea.com/gitea/tea and also looks like one would need to introduce https://gitea.com/gitea/go-sdk or go-swagger as a dependency.

I'll leave that for #80 to be discussed since sr.ht and GNU based forges are what I'm currently supporting.

As also noted in the gitea equivalent of this issue, an other option to a bridge is for source-hut to use git-bug as the back-end. I would prefer this personally, but it is of course harder to achieve (socially/politically). A bridge would already be great!

Related discussion @sourcehut

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

Not stale.

github-actions (github-actions) removed label lifecycle/stale 1 year ago

sudoforge added label area/bridge 1 year ago

sudoforge added label kind/feature 1 year ago

sudoforge added label priority/important-longterm 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/stale 1 year ago

github-actions (github-actions) removed label lifecycle/idle 7 months ago

Could anybody here review the linked draft PR?

@mcepl i should have time to take a cursory look at #1499 some time over the coming weeks.