Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decision Proposal 340 - Maintenance Iteration 18 #340

Closed
CDR-API-Stream opened this issue Jan 17, 2024 · 11 comments
Closed

Decision Proposal 340 - Maintenance Iteration 18 #340

CDR-API-Stream opened this issue Jan 17, 2024 · 11 comments
Labels
Category: API A proposal for a decision to be made for the API Standards made Category: CX A proposal for a decision to be made for the User Experience Standards Category: InfoSec Information Security Technical Working Group Decision Proposal Industry: All This proposal impacts the CDR as a whole (all sectors) Status: Decision Made A determination on this decision has been made
Milestone
v1.30.0

Comments

@CDR-API-Stream
Copy link
Contributor

Maintenance Iteration 18

This decision proposal will capture the consultation for Maintenance Iteration 18.
Consultation will address change requests submitted to the standards maintenance repository.

The DSB invites the community to provide recommendations for consideration.

Dates

Consultation open: 17 January 2024
First call of this maintenance iteration: 7 February 2024

Meeting agendas and minutes will be posted in the comments below as the iteration progresses.

Useful links

Holistic thread for minor corrections
Standards maintenance repository
Standards maintenance project board
Previous Maintenance Iteration meeting notes
@CDR-API-Stream CDR-API-Stream mentioned this issue Jan 17, 2024
Closed
@ElizabethArnold-DSB ElizabethArnold-DSB added Status: Open For Feedback Feedback has been requested for the decision Category: API A proposal for a decision to be made for the API Standards made Category: CX A proposal for a decision to be made for the User Experience Standards Category: InfoSec Information Security Technical Working Group Decision Proposal Industry: All This proposal impacts the CDR as a whole (all sectors) labels Jan 30, 2024
@CDR-API-Stream
Copy link
Contributor Author

CDR-API-Stream commented Feb 7, 2024 •
edited
Loading

Maintenance Iteration 18 Kicks off

The first meeting for Maintenance Iteration 18 kicks off on today (at 2:00PM AEDT)!! The agenda is available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Agenda-(7-February-2024)

Maintenance Iteration 18

The DSB invites participants to propose items for consideration and prioritisation. You can do this by posting a comment on this issue and attending today's meeting to provide context and detail on your requirements in support of your request.

@markverstege
Copy link
Member

markverstege commented Feb 8, 2024 •
edited by CDR-API-Stream
Loading

Meeting minutes for yesterday's maintenance iteration call are available here: Minutes. The purpose of this meeting was two-fold:

  • A review of the maintenance iteration process. The output is available here: https://miro.com/app/board/uXjVNzxv1Pk=/
  • Backlog grooming to select candidate change request for maintenance iteration 18

Based on discussion with participants, the candidates proposed for consideration this maintenance iteration are:

Domain # Issue
MI 18 629 Maintenance Iteration 18 Holistic Feedback
CX 468 Secondary user approvals withdrawal standards
CX 577 Withdrawal of a SUI by an Account Holder leaving an "Empty" Authorisation
Security 628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
Energy 623 Add new pricing models to EnergyPlanContractV2
Energy 624 Improved structure for Solar Time Varying Tariffs
Energy 625 Additional field to support Step Tariff calculations
Energy 627 EnergyPlanTariffPeriod - Change to daily supply charge
Admin 626 AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide
NFR 602 NFR: Secondary Data Holder unable to determine Customer Present
NFR 603 NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds

If you have any further issues you'd like to raise on behalf of your organisation could you please suggest them here in this thread. These issues will be considered in next fortnight's call before the final scope of maintenance iteration 18 is locked in.

@CDR-CX-Stream CDR-CX-Stream mentioned this issue Feb 13, 2024
Closed
@CDR-API-Stream CDR-API-Stream mentioned this issue Feb 14, 2024
Closed
@CDR-API-Stream
Copy link
Contributor Author

The agenda for today's Maintenance Iteration Meeting is available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Agenda-(21-February-2024)

@CDR-API-Stream
Copy link
Contributor Author

Minutes from the call on 21 February have been published and are available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Minutes-(21-February-2024).

Two more candidates have been added to those listed in this comment; they are:

@CDR-API-Stream
Copy link
Contributor Author

The agenda for today's Maintenance Iteration Meeting is available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Agenda-(6-March-2024)

@CDR-API-Stream
Copy link
Contributor Author

Sincere apologies for the delay in publishing the minutes from the meeting on 6 March, they're available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Minutes-(6-March-2024).

Due to a number of items generating robust debate we will prioritise comments submitted to GitHub before the meeting and continue to timebox discussions. Posting comments on GitHub is an important aspect of DSBs open and transparent consultation processes and we encourage the community to be more active on GitHub throughout Maintenance Iterations.

Two additional Security candidates have been added:

@CDR-API-Stream
Copy link
Contributor Author

The agenda for tomorrow's Maintenance Iteration Meeting is available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Agenda-(20-March-2024)

Energy issues will be discussed first to ensure there's enough time to get through the detail.

As mentioned earlier today, priority will be given to comments submitted before the meeting and we'll continue to timebox discussion (with some leniency on Energy issues).

@CDR-API-Stream
Copy link
Contributor Author

Minutes from the meeting on 20 March are available here https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Minutes-(20-March-2024).

The DSB is progressively staging each change, please review as they become available.

@CDR-API-Stream
Copy link
Contributor Author

The agenda for tomorrow's Maintenance Iteration Meeting, the final meeting for MI18, is available here:
https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Agenda-(3-April-2024)

The purpose of this meeting is to finalise the solutions for Candidates that can be resolved in MI18 and to agree on a course of action for those that can't be resolved.

@CDR-API-Stream
Copy link
Contributor Author

Thank you to everyone who attended the MI18 meetings.

The minutes for the final meeting on 3 April are available here: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-18:-Minutes-(3-April-2024)

MI19 is scheduled to commence on 17 April. The DSB will invite interested participants to register instead of issuing calendar invites. Keep an eye out for the email.

@CDR-API-Stream
Copy link
Contributor Author

The decision for Maintenance Iteration 18 has been provided by the Data Standards Chair:
Decision 340 - Maintenance Iteration 18 - Approved.pdf

These changes will be incorporated into v1.30.0 of the Standards.

@CDR-API-Stream CDR-API-Stream added Status: Decision Made A determination on this decision has been made and removed Status: Open For Feedback Feedback has been requested for the decision labels Apr 23, 2024
@nils-work nils-work mentioned this issue May 20, 2024
Closed
@nils-work nils-work added this to the v1.30.0 milestone Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category: API A proposal for a decision to be made for the API Standards made Category: CX A proposal for a decision to be made for the User Experience Standards Category: InfoSec Information Security Technical Working Group Decision Proposal Industry: All This proposal impacts the CDR as a whole (all sectors) Status: Decision Made A determination on this decision has been made
Projects
None yet
Milestone
v1.30.0
Development

No branches or pull requests
4 participants
@markverstege @CDR-API-Stream @nils-work @ElizabethArnold-DSB