This repository is used to contain discussions and contributions from the community of participants and other interested parties in the Australian Consumer Data Right regime. Please refer to the Main Standards Repository for more information.
The next maintenance iteration will commence in the first week of April 2020.
Phase 1: Backlog Grooming - 6th April 2020 commencement. 2 weeks duration
Phase 2: Consultation - 20th April 2020 commencement. 4 weeks duration
Phase 3: Approval - 18th May 2020 commencement. 1 week duration
Phase 4: Documentation - 25th May 2020 commencement. 1 week duration
Call to discuss backlog - 9th April 2020 @2pm for 1 hour
Call details are:
WebEx Link:
https://csiro.webex.com/csiro/j.php?MTID=mc8d05a7751925374edd395e45e81b723
Dial In Number: +61 2 6246 4433
Dial In Access Code: 786 191 844
Quick Dial: +61262464433,786191844%23%23
Call to discuss proposals - 14th May 2020 @2pm for 1 hour
Call details are:
WebEx Link: https://csiro.webex.com/csiro/j.php?MTID=m04f83fb26610fae4b1db5d007f573fe3
Dial In Number: +61 2 6246 4433
Dial In Access Code: 782 783 445
Quick Dial: +61262464433,782783445%23%23
Call to conduct Maintenance Iteration 3 retrospective and Maintenance Iteration 4: Kickoff and backlog review - 4th June 2020 @2pm for 1 hour
Call details are:
WebEx Link:
https://csiro.webex.com/csiro/j.php?MTID=m42eb4e5db9f2b31ac97dda244915fecd
Dial In Number: +61 2 6246 4433
Dial In Access Code: 786 481 756
Quick Dial: +61262464433,786481756%23%23
Each maintenance iteration will cover a period of eight weeks broken down in the following phases:
Backlog Grooming - 2 weeks During this phase participants will comment on issues that have been raised and the DSB will assess the relevant complexity and importance of the issues (as identified by the community). The phase will culminate in the selection of items for the iteration backlog by the DSB according to perceieved priority and team capacity.
Consultation - 4 weeks During this phase the DSB, and the community, will provide proposed changes to the standards and provide feedback on their relative merits. At the end of this phase a specific proposal will be formulated for submission to the Data Standards Chair for approval. If a single acceptable proposal cannot be identified then the issue may be carried over to a subsequent iteration.
Formal Approval & Update - 2 weeks During this phase the recommended proposals will be provided to the relevant Advisory Council for final review and then submitted to the Data Standards Chair for approval. The approved proposals will then be incorporated into the formal standards documentation.
Due to the national scope of the CDR regime the bulk of consultation and collaboration is expected to be conducted online using the issue tracker on this repository and the associated project boards.
In addition to this consultation two additional rituals are expected to be conducted:
- A teleconference to discuss the selected backlog items during week 2 of each iteration
- A teleconference to discuss the final proposals prior to submission to the Advisory Council during week 6 of each iteration
A project board for each sector will be maintained in this repository. These poject boards will be used to track progress on each of the prioritised issues.
Currently only a single project board exists: the Banking Maintenance Project Board
Any interested contributor is encouraged to raise new issues for queries or requests for change on the issue tracker. Issue templates have been created for change requests and for questions. It is requested that these templates be used when raising issues.
A series of labels have also been created so that issues can be categorised when they are raised. It is requested that these labels are applied, as appropriate, when the issue is raised. Of special note is the 'Urgent' label that is used to identify changes that need to be dealt with outside of the normal cadence. Please use this label judiciously.
It is expected that issue categorisation is done by the individual raising the issue through the application of labels. Once raised the DSB may re-apply labels if the issue is identified as being miscategorised. This may occur in response to feedback and comments identifying a different root cause for the change than originally expected.
If an issue is identified as being too complex or impactful to the standards to be managed via the maintenance process the DSB may elect to recategorise the issue as a fully fledged decision proposal. If this occurs then the issue will be closed in the maintenance repository and a new issue will be raised in the main standards repository.
The DSB will prioritise the open issues taking participant feedback into account. This priortisation will be managed via the order of the issues in the 'Full Backlog' column of the relevant project board.
At the end of the grooming phase the DSB will select a set of issues to be considered for the iteration. Issues will be selected according to priority but selection will also take into account the relative complexity of the issues and the capacity of the DSB team available for the iteration. Final decision of backlog items rests with the API Standards and InfoSec Lead under the supervision of the Data Standards Chair.
All decision making authority rests with the Data Standards Chair. Neither DSB members or community contributors have formal decision rights for the CDR regime. As a consequence all proposals are considered recommendations until the Data Standards Chair has formally approved them. Once approval is obtained this will be documented in the main standards repository.
In the event of an issue being advised as being urgent (perhaps to support a critical implementation issue, defect or security flaw) the issue will be dealt with as a priority and, once a recommendation is identified, will be immediately submitted to the Data Standards Chair for approval. It is hoped that urgent changes can be minimised and, to help ensure this, the DSB reserves the right to verify whether an issue is considered urgent or not.
We're committed to undertaking conversations relating to the technical standards in the open. Questions or comments that participants might ask us via email or private message are likely to be questions or comments other participants have as well. Our answers will be of interest to everyone. There are likely to be experiences and lessons everybody working in this ecosystem can learn from. Having these conversations transparently helps us reduce duplication, resolve issues faster and keep everyone up to date with the conversation.
We ask that all contributors to the Consumer Data Standards repositories comply with the GitHub Community Forum Code of Conduct.
In addition, it would be appreciated if the following rules are adhered to when commenting or contributing:
- Please provide a single, considered response to each proposal covering all feedback concerning the proposal.
- For transparency, if you work at or are associated with an organisation with an interest in the standards, please indicate this in your response.
- Please ensure you are aware of and compliant with any social media guidelines or internal processes for response set by your organisation before providing feedback.
- The creation of new issues by contributors is encouraged in this repository