RIOTJan 9
We #didit too! After moving away from Twitter a while ago, we will make our videos from YouTube available soon on @MakerTube over at @[email protected]! Hope to see you there! #did #iot #fediverse
Show threadchrysnJan 9
@RIOT_OS Now let's do GitHub next ;-)
Show threadmaribu

@chrysn @RIOT_OS The https://git.riot-os.org/ mirror has been up and running since a few years to at least allow cloning / pulling without running into 429 Too Many Requests that Github has started to greet people with.

Forgejo's vision of allowing to report an issue and create a pull request on any federated server would be super cool. And some EU legislation forcing monopolistic git forges to implement those APIs.

As of now, I fear pulling out fully of Github may leave users behind.

RIOT-OS git forge

Gitea (Git with a cup of tea) is a painless self-hosted Git service written in Go

RIOT-OS git forge
Jan 9 at 10:38pmWeb
Show threadMartine (she/they)Jan 9
@maribu @chrysn @RIOT_OS I personally would prefer, if we would actually use Forgejo there instead of Gitea. But that's just my 2ct.
Show threadmaribuJan 9
@chrysn @RIOT_OS But maybe turning Github into the mirror and a more friendly forge such as Codeberg into the primary repo would be an option?
Show threadchrysnJan 9
@maribu @miri64 For mirroring of the source code we wouldn't need a forge; a plain HTTP git mirror would do.
The tricky part are the issues; so far, @forgejo can do one-off imports, but not constant replication. (I wouldn't want to sync, more like have a mirror and two issue namespaces for a transition period).
As for leaving users behind -- yeah, mirror to GitHub, and put up a warning "yeah you can file issues and PRs here but they'll be processed more slowly".