Open robmartin33 opened 2 months ago
Action Items from TF-3 meeting on July 5:
Thanks for this Rob... This is exactly what I was looking for so we don't all go off and raise many many duplicate support requests to the billing generators
Action Items raised during TF-3 call on Friday, July 12:
@robmartin33 Rob Martin is leading this issue.
Description
When FOCUS adopters identify an issue with a FOCUS dataset, how should they communicate this to the various interested parties? Issues might include:
The issue may indicate:
As a result, a user-identified issues will likely need to be communicated to some combination of:
Proposed approach
Issue reporting by non-members of FOCUS cannot be done easily in the FOCUS_Spec repo, and there is a likelihood that misunderstandings and a large number of Use Case suggestions will come in during early release times, so for discussion purposes, the following are assumed to be required to handle the submission of issues:
Someone adopting FOCUS who is a Member may open an issue in the FOCUS_Spec if they wish.
Github issue or Reference
Context
This issue was raised at the 5 July 2024 Task Force 3 meeting by Alex Hullah
There is a strong correlation between this issue's resolution and the establishment of a FOCUS Conformance Compliance program which the SteerCo will discuss in detail at the 25 July 2024 monthly meeting.