A new feature for OSC 1.x which requires alignment of OSC 1.x, OSC 2.x domain models

A proposal which is currently open for members to enroll for.

An issue that has been accepted by the group, which needs to be assigned to a responsible, given a due date and needs a clear specification of requirements to be fulfilled. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that has a type and that needs to be accepted by the group. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that has a solution in an associated merge request, which is ready to be reviewed by the group. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that is assigned a responsible, has a due date and clear requirements, which now needs to be implemented in a solution. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that has been integrated and has an integration reviewer, which is ready to be checked and all open comments are resolved. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

A new issue that needs to be classified to a type. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that has been integrated and is assigned to the workflow manager, which is ready to be merged. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that has a been accepted by the group, has an assigned integrator, which is ready to be integrated into the standard or project. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that contains contradictions or errors in the standard. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue documenting meeting minutes for an ASAM CCB meeting. Meeting minutes should be kept for each official CCB meeting. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue that contains general structural and editorial changes for the whole documentation. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue that amends or improves existing features. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue related to the repository infrastructure such as CI, builds, document toolchain or similar. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.