Introduction
A CX Guideline is an example of a key requirement or recommendation. Implementing a CX Guideline is optional. While the CX Guidelines are not mandatory, the rules indicate that CDR Participants must have regard to them.
To suggest a change to the Consumer Experience (CX) Guidelines, create a CX Guidelines Change Request. You can request a change to an existing guideline, or an addition to the guidelines.
CX Guidelines, suggested via a CX Guidelines Change Request, may require community consultation before they are published.
Raising change requests
CDR participants can raise a request to create new guidelines or change existing guidelines on the standards maintenance repository. An issue template has been created for such change requests and questions. It is requested that this template be used when raising these issues.
Instructions on raising a CX Guidelines issue can be found in Creating a CX Guidelines Change Request.
The DSB may also raise a CX Guidelines issue if the proposed guidelines have potential for implementation impacts.
Consultations
These guidelines are primarily consulted on via GitHub. Although they are not part of Consumer Data Standards maintenance cycle, they will be considered an iteration candidate and may be discussed on Maintenance Iteration (MI) calls. For more on Maintenance Iterations, see the guidance on Standards Maintenance.
Guidelines that are ready for feedback will be noted on GitHub and discussed during the MI call with a prescribed feedback window.
Issues that are put on hold will be moved to the backlog. This action will be shown on the issue’s GitHub page and recorded in the meeting minutes. Once the issue progresses, it can be brought back as an iteration candidate for active discussion.
Consultation conclusion
When consultation concludes and an outcome has been decided, the issue will be closed and the DSB will publish the changes on the CX Guidelines website.
The author may close the issue if they have received an answer that resolves their query or request. Alternatively, the DSB may close issues where an answer has been supplied with a "Proposal made" label, and no additional feedback for change is given.
The outcome will also be added to the Decision Proposal for the Maintenance Iteration in which the issue was concluded, under the heading ‘no decision required’.
Comments
0 comments
Please sign in to leave a comment.