I found the following tools to have a simpler method than emailing patches: How to anonymize your GitHub activity - Livable Software
Is framagit still up and running, and accepting even new projects?
Seems alive. Framasofts two major projects are hosted there - Projects · Explore · GitLab
By the way, there was a more concrete proposal for Gitea ForgeFed integration since: Design Discussion: ActivityPub support + ForgeFed vocabulary · Issue #14186 · go-gitea/gitea · GitHub
A number of people in outreachy are starting to internalize details of github, rather than gitlab or gitea, as their first git web system because the ocaml community is using it de facto. It’s a very minor detail, but feels like these decisions compound over time.
If we are serious about exposing a non-GitHub interface to publishing, it’s doable, with some effort and integration work of course. The basics should be covered by an API like:
# Register a new publisher
POST /opam/register/:publisher_name
# Publish a new package version
POST /opam/publish/:package_name.version
Authorization: Bearer :token # Received from register endpoint
<Package blob>
# Cancel an in-progress publish
DELETE /opam/publish/:package_name.version
Authorization: Bearer :token # ^
Of course it can get complicated than that, depending on if the opam maintainers want to keep the review process that they currently have, or just allow anyone to publish anything.
This API should be doable today by hooking in to GitHub. And down the line if opam moves off GitHub it can be adapted for that too.
P.S. GitHub wrangled the US government into allowing Iranians to access it, just saying.
A headsup about a new project that is looking for users: it is a federated forge service in the style of Peertube (except for code, not videos). https://fedeproxy.eu/
I encourage those interested in trying more decentralised approaches to coding in OCaml to give this a whirl, and any feedback you might have about it.