ICM 0.3.0 - preparing the scope for meta-release Spring25

[jpengar]

Problem description

This issue should serve for collecting topics to be addressed by next release of ICM. Please add your proposals in the comments and open issues if needed.

Meta-release Spring25

M0:

• 30/09/2024 kick-off preparation

M1 (Commonalities & ICM):

• 15/10/2024

Ref: Milestone activities

Expected action

The WG should review as candidates those issues labeled with ICM-backlog to decide whether to include or discard them (at least for now). And WG participants can submit new proposals for the next release to be considered as well.

Proposed candidate topics:

• Documentation improvements
  • https://github.com/camaraproject/IdentityAndConsentManagement/pull/182
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/178
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/190
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/191
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/200
• CAMARA Security and Interoperability Profile - Restrictions
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/194
• New features
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/125
  • https://github.com/camaraproject/IdentityAndConsentManagement/issues/145
• ...

Additional context This issue is analogous to the one open in Commonalities: https://github.com/camaraproject/Commonalities/issues/273

[eric-murray]

I added the following issue as a candidate for 0.3.0

• 194

[murthygorty]

Let's please consider this issue for 0.3.0 DPoP support in CAMARA OIDC Profile #125

@gmuratk @mengan @AxelNennker

[shilpa-padgaonkar]

Please consider https://github.com/camaraproject/IdentityAndConsentManagement/issues/145

[jpengar]

• Next Steps:
  • Should we start talking about the candidates to decide whether to include them in Spring25? Or do it after the M0 date and wait for more candidates until then?
  • Should we already include all ICM backlog labeled issues in the list of candidates for analysis, i.e. to decide if they will eventually be part of Spring25 scope?
  • Should we start working on PR #182 and the rest of the documentation topics that seem to be needed for sure for Spring25?

[jpengar]

200 was requested by @tanjadegroot. I'll add it to the list of candidates, as agreed in today's WG call.

[jpengar]

https://github.com/camaraproject/IdentityAndConsentManagement/labels/spring25-candidate label created for explicitly requested items as candidates for the next meta-release scope.

As agreed in today's WG call, other items labeled with https://github.com/camaraproject/IdentityAndConsentManagement/labels/ICM-Backlog but not explicitly requested by the issue owner or other WG participants will not be considered candidates by default, to avoid the overhead of having technical discussions about them without the support of the owner or other participants behind it.