diff --git a/.github/ISSUE_TEMPLATE/1-bugfix.yml b/.github/ISSUE_TEMPLATE/1-bugfix.yml deleted file mode 100644 index c3784949cb..0000000000 --- a/.github/ISSUE_TEMPLATE/1-bugfix.yml +++ /dev/null @@ -1,107 +0,0 @@ -# ******************************************************************************* -# Copyright (c) 2025 Contributors to the Eclipse Foundation -# -# See the NOTICE file(s) distributed with this work for additional -# information regarding copyright ownership. -# -# This program and the accompanying materials are made available under the -# terms of the Apache License Version 2.0 which is available at -# https://www.apache.org/licenses/LICENSE-2.0 -# -# SPDX-License-Identifier: Apache-2.0 -# ******************************************************************************* - -name: Problem Report -description: Issue to track a bug -title: "Bug: Your bugfix title" -labels: ["codeowner_review"] -type: 'Bug' -body: - - type: markdown - attributes: - value: "## Bug Ticket creation" - - type: textarea - attributes: - label: Description - description: | - Description of the Bug - Root cause / Impact / Notification required? - validations: - required: true - - type: textarea - attributes: - label: Analysis results - description: | - Documentation of the analysis results - validations: - required: true - - type: textarea - attributes: - label: Solution - description: | - Documentation of the solution - Link to Pull Request containing the solution - validations: - required: true - - type: dropdown - attributes: - label: Error Occurrence Rate - options: - - Single Event - - Sporadic - - Highly Intermittent - - Reproducible - - type: textarea - attributes: - label: How to reproduce - description: How to reproduce? - - type: textarea - attributes: - label: Supporting Information - description: | - During which operational state did the issue occur - Observations / Screenshots / Traces - validations: - required: false - - type: dropdown - attributes: - label: Classification - options: - - minor - - major - - critical - - blocker - default: 0 - validations: - required: true - - type: dropdown - attributes: - label: Affected Version - options: - - pre-0.5 - - 0.5 - - 1.0 - default: 0 - validations: - required: true - - type: dropdown - attributes: - label: Expected Closure Version - options: - - 0.5 - - 1.0 - default: 0 - validations: - required: false - - type: checkboxes - attributes: - label: Category - options: - - label: Safety Related - - label: Security Related - - type: textarea - attributes: - label: ASIL classification - description: Add ASIL classification, e.g. ASIL_B or ASIL_D - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/2-improvement.yml b/.github/ISSUE_TEMPLATE/2-improvement.yml deleted file mode 100644 index fa14031a1d..0000000000 --- a/.github/ISSUE_TEMPLATE/2-improvement.yml +++ /dev/null @@ -1,52 +0,0 @@ -# ******************************************************************************* -# Copyright (c) 2025 Contributors to the Eclipse Foundation -# -# See the NOTICE file(s) distributed with this work for additional -# information regarding copyright ownership. -# -# This program and the accompanying materials are made available under the -# terms of the Apache License Version 2.0 which is available at -# https://www.apache.org/licenses/LICENSE-2.0 -# -# SPDX-License-Identifier: Apache-2.0 -# ******************************************************************************* - -name: "Improvement / Task" -description: Issue to track a improvement / task -title: "Improvement: Your Improvement title" -labels: ["codeowner_review"] -body: - - type: textarea - attributes: - label: What - description: | - - Goal of the Improvement / Task - - If Req/Architecture is affected, the template of - [Change Management](https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_impact_analysis_template.html) needs to be used - validations: - required: true - - type: textarea - attributes: - label: How - description: Details on implementation approach - validations: - required: false - - type: textarea - attributes: - label: Estimates for realization - description: | - - Estimate the effort, resources, risk for the realization - - Impact to users of the feature - validations: - required: true - - type: checkboxes - attributes: - label: Category - options: - - label: Affects Detailed Design - - type: checkboxes - attributes: - label: Requirements / Architecture - options: - - label: Requirements / Architecture are not affected by this change? - required: true diff --git a/.github/ISSUE_TEMPLATE/3-change.yml b/.github/ISSUE_TEMPLATE/3-change.yml deleted file mode 100644 index 7119196e01..0000000000 --- a/.github/ISSUE_TEMPLATE/3-change.yml +++ /dev/null @@ -1,94 +0,0 @@ -# ******************************************************************************* -# Copyright (c) 2025 Contributors to the Eclipse Foundation -# -# See the NOTICE file(s) distributed with this work for additional -# information regarding copyright ownership. -# -# This program and the accompanying materials are made available under the -# terms of the Apache License Version 2.0 which is available at -# https://www.apache.org/licenses/LICENSE-2.0 -# -# SPDX-License-Identifier: Apache-2.0 -# ******************************************************************************* - -name: "Change Request" -description: Issue to track a change -title: "Change: Your Change Request title" -labels: ["codeowner_review"] -body: - - type: dropdown - attributes: - label: Change Request Type - options: - - Feature Request - - Feature Modification - - Component Request - - Component Modification - default: 0 - validations: - required: true - - type: textarea - attributes: - label: Description of the Change Request - description: | - - Exact description of the Change Request - - Impact to users of the feature/component - - Use following template within a PR and link it to this issue - [Change Management Feature Request Template](https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_feature_template.html) needs to be used - [Change Management Component Request Template](https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_component_template.html) needs to be used - [For (Process) Improvements, Improvement Issue Template](https://github.com/eclipse-score/process_description/blob/main/.github/ISSUE_TEMPLATE/2-improvement.yml) needs to be used - validations: - required: true - - type: textarea - attributes: - label: Estimates for realization - description: | - - Estimate the effort, resources, risk for the realization - validations: - required: true - - type: checkboxes - attributes: - label: Affects work products - options: - - label: Requirements - - label: Architecture - - label: Safety/Security Analysis - - label: Detailed Design - required: true - - type: textarea - attributes: - label: Impact analysis - description: | - - Details on the impacted work products - - Use the following template and/or run the impact analysis tool provided - If the following template is use within a PR, link it to this issue - [Change Management Impact Analysis Template](https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_impact_analysis_template.html) needs to be used - validations: - required: true - - type: checkboxes - attributes: - label: Safety or Security relevance - options: - - label: none - - label: Safety relevant - - label: Security relevant - validations: - required: true - - type: dropdown - attributes: - label: ASIL classification - options: - - QM - - ASIL_B - default: 0 - validations: - required: true - - type: dropdown - attributes: - label: Expected Implementation Version - options: - - 0.5 - - 1.0 - default: 0 - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index bb96199601..0000000000 --- a/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1,14 +0,0 @@ -# ******************************************************************************* -# Copyright (c) 2025 Contributors to the Eclipse Foundation -# -# See the NOTICE file(s) distributed with this work for additional -# information regarding copyright ownership. -# -# This program and the accompanying materials are made available under the -# terms of the Apache License Version 2.0 which is available at -# https://www.apache.org/licenses/LICENSE-2.0 -# -# SPDX-License-Identifier: Apache-2.0 -# ******************************************************************************* - -blank_issues_enabled: true diff --git a/process/process_areas/change_management/change_management_workflow.rst b/process/process_areas/change_management/change_management_workflow.rst index b715eff60f..25783f01b9 100644 --- a/process/process_areas/change_management/change_management_workflow.rst +++ b/process/process_areas/change_management/change_management_workflow.rst @@ -24,8 +24,8 @@ For a detailed explanation of workflows and their role within the process model, :status: valid :tags: change_management :responsible: rl__contributor - :approved_by: rl__committer - :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager + :approved_by: rl__architecture_community + :supported_by: rl__platform_team :input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record @@ -42,9 +42,9 @@ For a detailed explanation of workflows and their role within the process model, :id: wf__change_analyze_cr :status: valid :tags: change_management - :responsible: rl__contributor + :responsible: rl__architecture_community :approved_by: rl__project_lead - :supported_by: rl__committer, rl__safety_manager, rl__security_manager, rl__quality_manager + :supported_by: rl__platform_team :input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record @@ -53,20 +53,21 @@ For a detailed explanation of workflows and their role within the process model, The Change Request is analyzed. Until the template is not filled out properly, the Change Request may be set back to - “open” from the :need:`Committer `. + “open” from the :need:`Architecture Team `. If the Change Request shall be implemented, the Change Request status is set to "in implementation", otherwise to "rejected". - The author of the Change Request may cancel it, thus the status is set to "rejected". + If the author, :need:`Contributor `. of the Change Request decides to + cancel it, thus the status is set to "rejected" too. .. workflow:: Implement and Monitor Change Request :id: wf__change_implement_monitor_cr :status: valid :tags: change_management - :responsible: rl__contributor - :approved_by: rl__committer - :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager + :responsible: rl__delivery_team, rl__platform_team + :approved_by: rl__delivery_team, rl__platform_team + :supported_by: rl__project_lead :input: wp__issue_track_system, wp__feat_request, wp__cmpt_request :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record @@ -77,22 +78,21 @@ For a detailed explanation of workflows and their role within the process model, This may require additional activities, including creating ISSUEs and PRs. These are linked to the Change Request and monitored until closure. - The Change Request is done, if all linked activities has been closed and confirmed. - Before closing the Change Request, :need:`Committer ` must check the + The Change Request is done, if all linked activities has been closed and confirmed, + which is done by the approval of the selected codeowners. + Before closing the Change Request, :need:`Delivery Team ` must check the correctness. - The :need:`Committer ` may still reject it, thus the status is set to - "rejected". - - The author of the Change Request may cancel it, thus the status is set to "rejected". + The :need:`Delivery Team ` may still reject it, thus the status + is set to "rejected". .. workflow:: Close Change Request :id: wf__change_close_cr :status: valid :tags: change_management - :responsible: rl__committer - :approved_by: rl__project_lead - :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager + :responsible: rl__delivery_team, rl__platform_team + :approved_by: rl__delivery_team, rl__platform_team + :supported_by: rl__project_lead :input: wp__issue_track_system, wp__feat_request, wp__cmpt_request :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record @@ -101,9 +101,10 @@ For a detailed explanation of workflows and their role within the process model, The Change Request is closed. The Change Request is closed only, if the implementation is sufficient. That is verified - by the :need:`Committer ` finally. + by the :need:`Delivery Team ` finally, especially the selected + codeowners of the team must approve. - Otherwise the :need:`Committer ` keeps the status "in implementation". + Otherwise the :need:`Delivery Team ` keeps the status "in implementation". .. needextend:: docname is not None and "process_areas/change_management" in docname :+tags: change_management diff --git a/process/process_areas/change_management/guidance/change_management_guideline.rst b/process/process_areas/change_management/guidance/change_management_guideline.rst index 5b63575605..6b7a884722 100644 --- a/process/process_areas/change_management/guidance/change_management_guideline.rst +++ b/process/process_areas/change_management/guidance/change_management_guideline.rst @@ -43,7 +43,7 @@ to provide e.g. a change request issue template. .. note:: An example template for the Issue Tracking System in GitHub (`GitHub Issues `_) can be found here: - `Issue Template Change Request `_ + `Issue Template Change Request `_ Improvements including Process Improvements are not Change Requests. The project's selected Issue Tracking System may also provide a template for improvements, @@ -52,7 +52,7 @@ e.g. an improvement issue template. .. note:: An example template for the Issue Tracking System in GitHub (`GitHub Issues `_) can be found here: - `Issue Template Improvement `_ + `Issue Template Improvement `_ Attributes @@ -128,7 +128,7 @@ automatically included or copied by the different users. .. note:: For the Issue Tracking System in GitHub, there is a template created, which can be be found here: - `Issue Template Change `_ + `Issue Template Change `_ .. note:: A Change Request Example based on that template is here: diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst index 9229a17969..b2d5f96bc7 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst @@ -36,7 +36,7 @@ in project's selected Issue Tracking System: :need:`[[title]]`_) can be found here: - `Issue Template Bugfix `_ + `Issue Template Bugfix `_ Attributes ---------- @@ -102,7 +102,7 @@ from the different users. .. note:: For the Issue Tracking System in GitHub, there is a template created, which can be be found here: - `Issue Template Bugfix `_ + `Issue Template Bugfix `_ .. note:: A Problem Report Example based on that template is here: diff --git a/process/process_areas/process_management/guidance/process_management_guideline.rst b/process/process_areas/process_management/guidance/process_management_guideline.rst index 22dbdad21d..d17df9b938 100644 --- a/process/process_areas/process_management/guidance/process_management_guideline.rst +++ b/process/process_areas/process_management/guidance/process_management_guideline.rst @@ -117,7 +117,7 @@ Monitor/Improve Process If potential improvements are detected, the :need:`[[title]] ` triggers an ISSUE for improvement by using the -`Issue Template Improvement `_. +`Issue Template Improvement `_. The potential improvement is discussed during the public Process Community Meetings and if decided to implement, a pull request to follow :ref:`pm_create_maintain_strategy` diff --git a/process/roles/index.rst b/process/roles/index.rst index ab751b3dc9..c587318086 100644 --- a/process/roles/index.rst +++ b/process/roles/index.rst @@ -108,6 +108,28 @@ Project Development Roles The testing community members are responsible for the test case development from component to platform level. They shall be included in any requirements reviews. They can also improve independence argumentation when involved in the development of unit testing on safety critical + units. In this way the testing community takes a supportive role for unit testing. + +.. role:: Architecture Community Member + :id: rl__architecture_community + :status: valid + :tags: architecture_design + :contains: rl__committer + + The architecture community members are responsible for the features and components of + the platform. Feature and Components requests, which add new ones or modifications, are + in their responsibility. They are aligned with the Project Leads. + +About Features + +Feature Request issue template + +Component Request + +A Component Request represents an independent work package used to describe modifications inside a Feature, either adding new components or modifying existing ones. Component Request work packages can be linked to other work packages, but they must not be treated as parent work packages. They shall be discussed with Architecture Community and the issues are owned by a Team and are part of the Team`s main repository.. + + They shall be included in any requirements reviews. They can also improve + independence argumentation when involved in the development of unit testing on safety critical units. In this way the testing community takes a supportive role for unit testing .. role:: Project Security Team @@ -126,9 +148,12 @@ Project Teams :id: rl__platform_team :status: valid :tags: cross_functional - :contains: rl__project_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer, rl__infrastructure_tooling_community, rl__process_community + :contains: rl__project_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer, rl__infrastructure_tooling_community, rl__process_community, rl__architecture_community - The platform team is responsible for all artifacts within the platform SEooC. Additionally it is also responsible for the overall process including its support by tooling. + The platform team is responsible for all artifacts within the platform SEooC. + Additionally it is also responsible for the overall process including its support + by tooling. + Depending on the platform artifacts, some of them are assigned as codeowner. .. role:: Delivery Team :id: rl__delivery_team @@ -136,8 +161,12 @@ Project Teams :tags: cross_functional :contains: rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer - The delivery team is responsible for all artifacts within the Delivery Container SEooCs containing the Dependable Elements. Each Delivery Container has only one responsible team. - One of the committers in the team acts as the "Project Manager" and is responsible for planning and reporting. + The delivery team is responsible for all artifacts within the Delivery Container + SEooCs containing the Dependable Elements. Each Delivery Container has only one + responsible team. + One of the committers in the team acts as the "Project Manager" and is responsible + for planning and reporting. + Depending on the delivery container artifacts, some of them are assigned as codeowner. .. role:: Release Team :id: rl__release_team