> By what metrics will you define the successful completion of the project?

* The frequency of stable releases of the F3 format
* The frequency of stable releases of the F3 reference implementation
* The number of forge service providers supporting F3
* The number of developers using F3
* The number of forges natively supporting F3
* The number of people (paid staff and volunteers) participating in the evolution of F3 (format and reference implementation)
* The funding obtained to sustain F3 as a whole

> How are you planning to collect that information? And how will you document it?

The Frequency of stable releases is collected from the registry where they are published.

Lists of forge service providers, software forges and service providers are maintained in a repository, sorted to record those using or implementing F3 to keep track of them over time. As F3 becomes more popular it may be difficult to maintain such lists and the only way to collect that information would be to actively poll organizations and people.

People participating in the evolution of F3 are conveniently listed in the changes they authored in the VCS repositories. Some people provide advice's instead of authoring a change that is recorded, which makes them more difficult to account for. Such mentoring is however important and relies on the memory of the people collecting the information manually.

The funding is systematically and publicly recorded in a spreadsheet and a forum and can be collected from there.

> By what means will you determine that the project was successful in reaching its goals?

* The F3 stable releases are published at least twice a year
* All forges natively support F3 (hence all developers and forge providers)
* There are more volunteers participating in F3 than paid staff
* The funding covers the cost of running F3, including the paid staff salary

> How will you collect and share learnings from this project?

In the first few years all information worth learning from is expected to be published in the F3 forum. Once a month all messages are browsed and a report is written as a digest. Something similar is done with the pull requests from the F3 specifications and the reference implementation. The authors of the report will do their best to write it in an objective and dispassionate way but they will inevitably make choices that reflect their own interest.

The monthly report allows for participation from people who are not engaged daily in the project by providing them with a high level view. In addition to the synchronous communication channel (Matrix chatroom) and the asynchronous communication channel (Forum), a recurring meeting is organized to share learnings with all stakeholders:

* A monthly report is published to reflect the progress of F3
* A monthly videconference is organized and open to the public to discuss the monthly report
* A presentation of the progress of F3 is made in a synthetic way during a webinar once a year

> Do you expect any major milestones during this project?

The first stable release of the F3 format and the Go reference implementation.

> What instrument or process will you use to document the impact of this project on your local community, beneficiaries, or Internet freedom ecosystem?

The projects supported by OTF and their dependencies will be approached and invited to participate in User Research initially. Their input will define themes that matter to them and when the implementation is stable, they will be invited to use F3 to solve the problem they have. The impact will be positive if the need observed during the User Research phase is fulfilled by the F3 release.