> ... how this effort will achieve sustainability over the funding period and beyond.

F3 needs to evolve to keep up with the evolution of software forges. As new development methods and tools are implemented, F3 must be updated to represent them. If it is to succeed, it will require an active engagement from dozens if not hundred of developers over decades. A likely scenario involves a few full time paid staff whose mission is partly to advance F3 on a technical level (release cycle, online resources, etc.) and partly to empower a larger community of volunteers (on-boarding, training, meetings, roadmaps, etc.).

> ... funding received from other funders or other revenue models.

During the first years, F3 is bootstrapped by seeking funding with OTF, NLnet and European R&D tax relief schemes. The goal is to create the conditions for F3 to be natively supported by each forge and facilitate participation in the maintenance of F3 by all stakeholders. At which point the organizations developing the forges as well as the service providers selling services based on Free Software forges will have a vested interest in devoting a fraction of their revenue to keep F3 going.

> ... collaborations with other organizations and your role and relation to communities around your project.

F3 is developed bottom up (see above for a detailed explanation) to become a de-facto standard. As it matures a dialog with standard bodies such as OASIS or W3C will be engaged. The goal is that ultimately one of them supports F3. In the meantime relationships with organizations and people developing software forges (Forgejo, Gitea, GitLab, etc.) are the primary focus because they are involved in making the native support of F3 a reality. Organizations running forges (Framasoft, Codeberg, Gna!, etc.) as well as Free Software providers (Webarchitects, Easter-Eggs, Bearstech, etc.) have an incentive to be early adopters of the F3 reference implementation (to migrate and mirror software projects, for instance). Finally, the Free Software developer community is the primary community involved in User Research to sort out F3 priorities.

> ... how this project provides resources to others or how others can reuse the resources you develop.

F3 is developed in the context of the forgefriends project, a horizontal community with a [radically transparent governance](https://forum.forgefriends.org/t/a-guide-to-forgefriends-governance/511). Anyone and everyone has access to all the resources of the project, subject to their acceptance of the Code of Conduct. The resources developed by F3 are all released under a Free Software license.

#### Adoption efforts

Wide adoption of F3 is difficult to achieve, it requires a long term effort. But can be done incrementally.

The adoption of F3 will require:

- endorsement by a standard body
- a concise, precise and unambiguous documentation
- complete and reliable reference implementations in multiple programming languages
- native integration in all major software forges

At present the primary adoption blocker is that GitHub is unlikely to support F3 or any other Open Format facilitating software project migration and mirroring.

An incremental adoption should start by:

- creating the format with a bottom up approach (see above for a detailed explanation)
- providing a reference implementation
- focusing on practical advantages this reference implementation brings to Free Software developers (e.g. cross forges issue tracking)

Further iterations will then expand the scope of the F3 specifications and provide additional practical advantages via the reference implementation to drive the change.