Minutes from previous meeting (7 Feb 19) approved.

Roll call via WebEx accepted.

Use cases on GitHub: 

• Outstanding 
• Central FDC3 GitHub 

Discussion items 

• Not all use cases had been added to GitHub repo so Kat will put them in markdown, Johan will add them to the repo and Saori will review (and approve if appropriate).
• Confirmed that FDC3 PMC agreed that WGs can set their own additional permissioning requirements.
• Reminder that anything merged into the repo is auto-deployed onto the microsite.
• Agreed to merge CODEOWNERS (and Tom modified so that it would work when merged to the new single repository). This adds the requirement of approval from one of the three named individuals - the WG chairs.
• Discussed the crossover from the old to the new, single GitHub repository and confirmed approach to complete all necessary merges outstanding in current repo before migrating to new single repo.
• The group reviewed a number of issues/PRs, which can be found here.

• Saori reminded the group that the only use case in GitHub are the ones that have been accepted in Confluence.

• Discussed the best way to represent links from the use cases to the specifications/standards that are relevant for implementation of the specific workflows/functions, e.g. keep in confluence, embed within the Use Cases in GitHub, provide sample code, challenges pinpointing the specific points of the specs to reference, highlighting the links in a clean, clear way, etc.
• Agreed that the priority for the FDC3 release is to have the accepted use cases in the repo and any other documentation complete and that the linkages could be addressed after and that GitHub Issues could be the right place to have this discussion and engage the user community.
• Reviewed a rendering issue and reminder that some front matter needs to remain as the tool that does the auto-deploy to web requires this.