@Sandra there's a reference implementation called Vervis, and we're also implementing in an existing forge, Pagure. So, it's not just a spec ๐Ÿ™‚

However AFAIK nobody is working on implementations for GitLab and Gitea :-/


@TheMainOne several people have looked into it, but AFAIK nobody is working on it. If anyone wants to work on it, let us know ^_^


Finally writing another little update ^_^

Opening and closing tickets is implemented. Submitting patches / merge requests too.

Now implementing updates to MRs and merging MRs. Then updating the spec.

Huge thanks to @NGIZero for the funding!

I hope we can make a patch/MR federation demo sometime soon.


@Sandra yes things like tickets and merge requests, not VCS internals (I don't think there's a need to represent Git's internals in ActivityPub, how Git or any other VCS stores things shouldn't matter to federation).


@humanetech no significant news right now but it's a good reminder for me to keep posting here about what's going on ๐Ÿ™‚

I jumped to implementing federated ticket dependencies, to give more time for discussion about the vocabulary for patches and merge requests. Also made progress with OAuth2 for use by the client app. Also made important upgrades to reusable AP tools in Vervis.

I'll write soon where there's more exciting stuff to say ^_^


Progress update yay!

@zplus@gnusocial.no is working on the foundations of federation in Pagure, representing objects using ActivityPub & delivering activities between servers.

@jazzyeagle & ikomi started working on a client app for Vervis! And I'm so grateful for their help! It will connect to servers using ActivityPub C2S and some forge-related vocabulary we'll define in ForgeFed.

I'm implementing federated patches & merge requests in Vervis, going to put this in the ForgeFed spec draft soon.


Finally we signed the funding plan with NLNet!!! ๐Ÿ˜€ Thank you @NGIZero for this amazing opportunity! ๐Ÿ™๐Ÿผ

We're working, and we're so excited!! more news soon, including the actual project plan :-)

Tbh I'm also scared a bit, there's so much work to do! But bit by bit, we'll get there ๐Ÿ˜Š


news ๐Ÿ˜€

We sent @NGIZero the funding plan, waiting for them to approve it. The funded work, by zPlus and me, will be the spec, reference implementation (Vervis), implementation in existing forge (Pagure), and an implementation guide.

Possibly work on Gitea will get funded too, we don't know yet.

The virus is slowing down my work, I hope it doesn't for the others! zPlus and I happen to be in countries where it's pretty crazy right now. Stay safe and strong โ˜ฎ&โค


update! ๐Ÿ˜€

We're planning to implement in both and . Still waiting to finalize funding details with NLNet.

Implementation of author-hosted tickets in Vervis is in progress, and so is OAuth2. Next will come patches/MRs, and then we can finally release that Draft 1 along with a demo.

We're looking into making better docs, maybe a talk too. Would you prefer to read, or to see/hear me explaining? ๐Ÿ˜‹


im not sure why this is news, or why a new git-tea ticket was opened - there was already an open git-tea ticket discussing forge-fed integration - as gitlab was also mentioned though, i could add for completeness, that pagure, gitlab, git-tea, and gogs, all have analogous tickets, which have been open since around 2018


ForgeFed boosted

There is a #github issue for #ForgeFed federation in #gitea but the devs want feedback before adding #ActivityPub #fediverse support:

1. Who wants this feature? Personal gitea user / Companies with private gitea / Git hosting website via gitea or others?

2. Why they need this feature?

3. How they want to use this feature?

Maybe you can help them and provide the answers.


Do you find that the status and progress of ForgeFed is clearly communicated? Is the work visible, does it look like something real that's really happening?

Plz comment & explain, especially if your answer is no :)

Would you want to see a video / talk / presentation about the project?

I updated the website main page to explain project status, feedback on that is welcome!

Reminder, monthly review round on Friday ๐Ÿ˜€


I'm working on updating Vervis (the reference implementation) to match recent spec updates. MCFI will hopefully turn into a ForgeFed implementation for Pagure (existing forge, pagure.io).

Spec content for our first little minimal draft is nearly done. Long debate about where to host issues is finally finished, with peaceful beautiful consensus ๐Ÿ˜‹


NLNet @NGIZero has approved funding for !

There are many potential tasks and related projects that haven't been taken by anyone yet. This is an amazing chance to get funded for working on an awesome free software and decentralized internet project!

ForgeFed work and funding plan: notabug.org/peers/forgefed/iss

If there's a task you'd like to grab/suggest/discuss, please comment here ๐Ÿ™‚

Oh btw our first spec draft release is coming soon ๐Ÿ˜๐Ÿ˜๐Ÿ˜


It's time for the monthly ForgeFed community review round! ๐Ÿ™๐Ÿผ๐Ÿ˜„

Instructions: talk.feneas.org/t/monthly-comm

Thank you and enjoy and happy new year :)

Work has been slow recently because we've been giving the world time to give feedback on some core decisions. In mid January or so, we stop waiting and proceed at a fast pace with what/who we have. Thank you for the patience. Hoping for 2020 to be the year of federated forges!! More news soon :)


Reminder: I'm trying to assemble a Working Group talk.feneas.org/t/working-grou and a Community Group talk.feneas.org/t/monthly-comm

This is the time to ask developers of forges (GitLab, Gitea, etc.) and ticket trackers (OpenProject, Taiga, etc.) to implement federation and to join the work on ForgeFed.

If you don't join, you don't get your needs taken into account, and we'll have a less useful lower quality spec.

Reminder, join if this stuff matters to you. And spread the word.


It's time for a round of review of ForgeFed discussions! ๐Ÿ˜€ ๐Ÿ˜€ ๐Ÿ˜€

Instructions: talk.feneas.org/t/monthly-comm

Happy participation! We need you, let's make federated forges happen :)

More news ๐Ÿ˜

We're going to have monthly community review rounds yay! They'll happen on the 1st Friday of each month. If you can't make it on Friday that's fine (let's try to focus the effort on the week following the Friday).

This Friday, 2 days from now, will be the first community review round! Mark the date :)

Instructions: talk.feneas.org/t/monthly-comm

๐Ÿ™ ๐Ÿ™ ๐Ÿ™ ๐Ÿ™ ๐Ÿ™


On Fridays 7PM UTC there is a weekly project jam on IRC/Matrix (see links in profile) and everyone is welcome!!

Show more

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).