Roadmap & site discussion:
- Group requested that FINOS produce a style guide to be referenced for the FDC3 site.
- Discussed adding links to GitHub from the start age, folder structure (some flat some multiple folders)Image Added
- Frank will try to compile once the merge is complete.
- Frank noted that although he generally prefers separate repositories he does not object to the consolidation.
- Agreed the roadmap should be on the website. Question about whether there should be roadmaps for each individual WG or one across FDC3 as a whole. Agreed to create for AppD and push to PMC.
- Discussion on the level of detail required and useful for the roadmap, e.g. dates and priorities as well as the distinction between a backlog and a roadmap (backlog = active issues, work committed to; roadmap = direction, request for features, new functionality, new work proposed including resulting from community exploration)
Use cases integration discussion:
- Homework for the group to review where AppD is relevant for the existing, approved, use cases. Aim to link back to AppD from the use cases.
- Potentially useful to note what AppD will, might and won't cover in the use cases.
- Also important to identify where there are more use cases that need to be added, i.e. that have been identified by AppD but may not be covered in existing Use Cases.
Group agreed that primary importance is to look at the pattern of the AppD use case to show how it is used in context of real live prod workflow and make sure that there are clear linkages from Use Cases back to AppD use case patterns.
Need to review the output of Kat’s work and highlight where there are already identified linkages to AppD.