Agenda; FINOS board headlines (non-FDC3 related); OSSF

There was a focus on delivering things that people can start using, e.g. MVPs and actual products.

The idea of marketplace was also raised, i.e. when you come to FINOS you can see what FINOS offers and what the Foundation is producing. Whether this looks like an app store or marketplace is still under consideration.

The group also discussed the importance of communicating the value of FINOS and its programs in business terms.

A top priority for this body is to get to all WGs to produce first versions of standards/specs and get them ratified by the end of year, if not sooner.

Intents WG has approved the first version of the draft spec to be presented to the wider FDC3 community for approval. Unfortunately, the wider group doesn’t meet for another 4 weeks and last time attendance was low for FDC3 General Meeting. An alternative in-line with the existing ratification process is to send out a description of the proposed standard to the wider FDC3 mailing list with a request for comments to the Intents WG. Following this review period the proposal can be put forward to PMC in two weeks.

If ratified, it gets labelled as a release with npm published and a document, e.g. the Spec for the API, also published as a pdf on Confluence. This will be labelled as v1.

The PMC can also vote over email out of a meeting. At end of the comment period the group can vote by email. Next steps are to:

• Send a proposal to ratify Intents to the full FDC3 list
• Allow two weeks of comment. If there are no negative comments then this can go to a vote without being presented to PMC.