DRAFT: monthly report, November 2021

Most of the work during the last month was around implementing fedeproxy and contributing to Gitea. A proposal to change the name of the project from fedeproxy to forgefriends is well on the way. The November 2021 monthly update videoconference will be held 2021-11-18T16:00:00Z2021-11-18T17:00:00Z and is open to everyone.

Software Development

The switch to go was delayed by two weeks, during which contributions to advance federation in Gitea were done, with the help of a cheatlist. It was also an opportunity to publish a number of code walkthrough explaining the Gitea codebase in the areas that are relevant to federation.

The addition of the go-fed dependency triggered a discussion about the impact on the Gitea codebase and may require a significant change in the release process, i.e. distributing dependencies separately. For the purpose of integrating go-fed in Gitea, the integration of go-fed in existing applications (writefreely and GoToSocial) were studied. It turned out the apcore framework, which is part of the go-fed project, is a better source of inspiration.

But this is not an immediate concern and the first ActivityPub endpoints were added: one for Person which allows to retrieve basic information about a user (actor in the ActivityPub parlance) and one for Repository which is defined by forgefed. The httpsig library was used to sign and verify ActivityPub requests.

The fedeproxy specific part of the development included the creation of a repository dedicated to storing and sharing the file representation of issues, pull requests etc. It is essentially the same as what is done for the wiki, which stores pages in a repository created alongside the repository for code. This repository is populated implicitly when the endpoint to retrieve the ActivityPub repository information is used.

Fedeproxy has been kept in sync weekly with Gitea and it was no trouble at all so far.


The experiment in simultaneous interpretation happened during the October 2021 monthly update, with two English speaker and one person speaking only French and translated simultaneously. It was a little bumpy but not to the point of disruption . The technical setup was fragile and another one was proposed and tested. An alternative was also proposed by @mariha: a modified Jitsi server implemented by @jfinn.

Storytelling is an important part of how a project communicates about diversity and a post was published about a first hand testimony related to Asperger’s Syndrom and Meltdowns.

Details on the work done to foster diversity are available in the forum.


Chapril forge

@pilou and @dachary did their duties, upgrading Gitea, participating in the monthly Chapril meeting, moderating user accounts and the web interface was customized.


As mentioned in the development part of this monthly report, there has been quite a few code contributions to Gitea regarding ActivityPub. However, since the author does not have a GitHub account, they were submitted via the forum which is a much slower process. Although there are some exceptions.

There does not seem to be a way to participate in the chatroom without using discord. But there is progress on hosting Gitea on Gitea so that code contributions are possible without using GitHub. This would greatly ease the collaboration between fedeproxy and Gitea.


A few recurring issues led to an offer to help with the maintenance of the go-fed resources.


The Gitea fork of codeberg.org was analyzed and turns out to be minimal. One of the allows the publication of a notice which may be useful for the Chapril forge. @dachary is a member of the non-profit running codeberg and participated in private discussions regarding the Term of Use and the moderation. They both became significant issues as Codeberg users grew to over 10,000. @misc relayed a talk that moderating a decentralized network works best when it is small: this may also be true of centralized resources such as Codeberg.


@bouviermullerp mentioned SemApps and there were some discussions to explore the possibility of collaboration. A few other projects and ideas were explored, most notably buggregator, ASK and fedeproxy UX/UI.

Communication and Branding

An inventory of the community building and channel needs of the fedeproxy project was submitted and discussed. It clarifies the areas that need work and why they are an essential part of the development of the project. There were some followups on how to fund the required work.

The October 2021 monthly event happened, with Rado, @aschrijver and Loïc and @Alexandra translated simultaneously from French to English.

@aschrijver proposed a new name and a new logo for the project. A favorable poll led to a formal proposal to change the name of the fedeproxy project. A consensus was reached and the name and the logo were adopted November 17th, 2021. The change will be reflected everywhere in the following weeks. It remains to be decided where the new name will be used.

The Fedeproxy website has been updated (following the comments of @aschrijver)

Transparency and funding

The third DAPSI call led to discussions that clarified (to some extent) how fundraising can happen in a horizontal community in general. And how it could happen for this specific call. The deadline is approaching (November 23rd, 2021) and there has not yet been any proposal drafted and nobody is working on that at the moment.

On November 9th, 2021 @dachary announced he will not be needing the remaining funds from DAPSI (12,400€) to keep working on fedeproxy and invited people to take his seat.

There was some confusion about the scope of the User Interface deliverables for the DAPSI grant and it was clarified with a discussion: it should be a CLI, not a web interface.

The fedeproxy project is atypical in how it is radically transparent, down to the last financial detail. This led to a discussion on what it means for people who are currently funded to work on the project.

An agreement was reached on how to settle the balance of expenses engaged by the members of the community since the beginning of the project, in December 2021.

Details on transparency and funding are available in the forum.

@pilou as discussed a few days ago, here is a draft of the monthly report, well in advance this time :slight_smile: So far I wrote all of them but it does not mean I have a monopoly. They are not difficult to write but a little tedious and I’d be grateful if you could draft this one. The method I use is super simple:

  • I write whatever comes to mind, keeping the sections from the previous meetings.
  • When I’m finished with what I have in memory, I go through all messages in this forum and fill the blanks. Everything that happens in fedeproxy is written down in this forum, you’re 100% guaranteed to not miss anything.

These reports turned out to be a great way to communicate at a high level about the project, for people who look at it from a distance and can’t go through the zillion of details published in the forum and elsewhere. They also were the foundation for the report sent in September to the organization funding your work and mine which we compiled together by mostly copy/pasting their content. This is a motivation to keep the current section names: they closely match the deliverables and will make it easier to compile the final report that is due in January.

Although the reports are numbered X/9, they proved useful in general and I’m very motivated to keep writing them, even after the obligations towards the funding organization are complete.

I’ll work on the draft of this report today.

The draft is ready for review. It will be published tomorrow so that @Alexandra has time to read it and prepare for the simultaneous translation.