Sent the following reply today.
Hi,
Please add loic@dachary.org to otf-talk. I have reviewed the OTF talk guidance document and the examples are very useful. I will have an immediate use of it for the purpose of user research, as it requires participation from people outside of the F3 project.
Here is a description of F3 for inclusion on the OTF website. The logo is attached. It would be more accurate to describe F3 as “F3 will be” rather than “F3 is” because there is barely more than scaffolding at this point. This will be revisited if a decision is made to advertise F3 so as to not confuse people. Right now, although the description is public, this did not confuse anyone AFAICT.
URL: https://f3.forgefriends.org/
The Friendly Forge Format (abbreviated F3) is an Open File Format for storing the information from a forge such as issues, pull/merge requests, milestones, release assets, etc. as well as the associated VCS (Git, Mercurial, etc.).
The structure of the archive is a hierarchy of files that are:
- JSON files with a normative JSON schema to describe what is usually stored in a forge database (issues, labels, etc.)
- Content addressable files (avatars, release assets, attachments, software packages, etc.)
- VCS directories (git, hg, etc.)
A reference implementation in Go is provided with drivers to mirror the forges to and from F3, with drivers for Forgejo, GitLab and Gitea.
I have noted the required date & format (again very useful to have an example) for the monthly report.
I’m available for a talk at your earliest convenience and my schedule is quite flexible. Let me know two dates / time that are good for you and odds are I’ll be available. I am in the UTC+1 timezone.
Cheers