Bonjour,
For the record, as of yesterday[0] go-ap is a dependency of Gitea for the purpose of implementing federation with ActivityPub. It is in the development branch that will be released some time at the end of 2022 as Gitea 1.18. The work continues and the best way to follow it is to subscribe to the corresponding task list[1].
Cheers
[0] https://github.com/go-gitea/gitea/pull/19133
[1] https://gitea.com/Ta180m/gitea/issues/3
--
Loïc Dachary, Artisan Logiciel Libre
On 22-06-20 15:58:11, Loïc Dachary wrote:
> For the record, as of yesterday[0] go-ap is a dependency of Gitea for the purpose of implementing federation with ActivityPub.
Hi Loïc,
If I'll have any changes to the libraries that might impact Gitea, how
should I announce them? Usually I just send an email here, but probably
I can open a ticket on github for you guys.
Cheers,
/Marius
On 21/06/2022 08:56, Marius Orcsik wrote:
> On 22-06-20 15:58:11, Loïc Dachary wrote:>> For the record, as of yesterday[0] go-ap is a dependency of Gitea for the purpose of implementing federation with ActivityPub.> > Hi Loïc,> > If I'll have any changes to the libraries that might impact Gitea, how> should I announce them? Usually I just send an email here, but probably> I can open a ticket on github for you guys.
I don't have a GitHub account so I won't see it. But most Gitea communication goes through GitHub so it would make sense.
However... Anthony went out of his way to avoid GitHub and works at https://gitea.com/Ta180m/gitea/ instead, mirroring what he does to GitHub. He also maintains a well curated task list at https://gitea.com/Ta180m/gitea/issues/3 which is referenced from GitHub. For all intent and purposes his repository is where most Gitea federation work happens. So it feels like opening an issue on https://gitea.com/Ta180m/gitea would be an effective way to notify everyone involved that something happened go-ap side.
With federation that kind of concern will go away. But it's going to take a while I'm afraid.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre