Remove Technical Lead Role

According to community discussion, Technical Lead Role is removed and replace by Project Lead Role
Project Lead Role Definition is reworked to meet ECLIPSE Handbook guidance
Remove S-CORE from some parts

Resolves: #71

Author: masc2023

process/folder_templates/features/feature_name/index.rst

@@ -84,7 +84,7 @@ Specification
 
    .. note::
       A CR shall specify the stakeholder requirements as part of our platform/project.
-      Thereby the :need:`rl__technical_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
+      Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
 
 
 

process/folder_templates/modules/module_name/component_name/docs/index.rst

@@ -72,7 +72,7 @@ Specification
 
    .. note::
       A CR shall specify the component requirements as part of our platform/project.
-      Thereby the :need:`rl__module_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
+      Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
 
 
 

process/process_areas/architecture_design/guidance/architecture_guideline.rst

@@ -166,7 +166,7 @@ Following roles should be included in the review:
 
 * :need:`[[title]] <rl__safety_manager>`
 * :need:`[[title]] <rl__security_manager>`
-* :need:`[[title]] <rl__technical_lead>`
+* :need:`[[title]] <rl__project_lead>`
 * :need:`[[title]] <rl__committer>`
 
 .. _create_component_architecture:

process/process_areas/change_management/change_management_concept.rst

@@ -54,7 +54,7 @@ Stakeholders for the Change Requests
    * Approves all change request activities besides changes closing
    * Is responsible to initiate the the closure of the change request
 
-#. :need:`Technical Lead <rl__technical_lead>`, :need:`Module Lead <rl__module_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 
    * Supports all change request activities
    * Approves the closing of the change request
@@ -106,8 +106,7 @@ by authorized persons.
 
 Authorized person includes
 
-#. :need:`Technical Lead <rl__technical_lead>`
-#. :need:`Module Lead <rl__module_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 #. :need:`Safety Manager <rl__safety_manager>`
 #. :need:`Security Manager <rl__security_manager>`
 #. :need:`Quality Manager <rl__quality_manager>`
@@ -124,7 +123,7 @@ monitored.
 The Change Request implementation must be tracked until it is closed.
 
 The status of the Change Request must be communicated by the
-:need:`Technical Lead <rl__technical_lead>` or :need:`Module Lead <rl__module_lead>` until
+:need:`Project Lead <rl__project_lead>` until
 the implementation is completed and confirmed.
 
 .. _chm_closing:

process/process_areas/change_management/change_management_roles.rst

@@ -21,8 +21,7 @@ Contributing Roles:
 
    * :need:`Contributor <rl__contributor>`
    * :need:`Committer <rl__committer>`
-   * :need:`Technical Project Lead <rl__technical_lead>`
-   * :need:`Module Project Lead <rl__module_lead>`
+   * :need:`Project Lead <rl__project_lead>`
    * :need:`Safety Manager <rl__safety_manager>`
    * :need:`Security Manager <rl__security_manager>`
    * :need:`Quality Manager <rl__quality_manager>`

process/process_areas/change_management/change_management_workflow.rst

@@ -23,7 +23,7 @@ Workflow Change Management
    :tags: change_management
    :responsible: rl__contributor
    :approved_by: rl__committer
-   :supported_by: rl__technical_lead, rl__module_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
+   :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
    :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
@@ -41,7 +41,7 @@ Workflow Change Management
    :status: valid
    :tags: change_management
    :responsible: rl__contributor
-   :approved_by: rl__technical_lead, rl__module_lead
+   :approved_by: rl__project_lead
    :supported_by: rl__committer, rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request
@@ -64,7 +64,7 @@ Workflow Change Management
    :tags: change_management
    :responsible: rl__contributor
    :approved_by:  rl__committer
-   :supported_by: rl__technical_lead, rl__module_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
+   :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
    :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
@@ -89,7 +89,7 @@ Workflow Change Management
    :status: valid
    :tags: change_management
    :responsible: rl__committer
-   :approved_by: rl__technical_lead, rl__module_lead
+   :approved_by: rl__project_lead
    :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request

process/process_areas/change_management/guidance/change_management_guideline.rst

@@ -93,15 +93,15 @@ This section describes in detail which steps need to be performed for a Change R
    * - :ref:`2. <chm_analyze_change_request>`
      - Analyze Change Request
      - :need:`[[title]] <rl__contributor>`
-     - :need:`[[title]] <rl__technical_lead>`, :need:`[[title]] <rl__module_lead>`
+     - :need:`[[title]] <rl__project_lead>`
    * - :ref:`3. <chm_imp_mon_change_request>`
      - Implement and Monitor Change Request
      - :need:`[[title]] <rl__contributor>`
      - :need:`[[title]] <rl__committer>`
    * - :ref:`4. <chm_close_change_request>`
      - Close Change Request
      - :need:`[[title]] <rl__committer>`
-     - :need:`[[title]] <rl__technical_lead>`, :need:`[[title]] <rl__module_lead>`
+     - :need:`[[title]] <rl__project_lead>`
 
 
 .. _chm_create_change_request:
@@ -172,7 +172,7 @@ When ready to review and to analyze, the author sets the status to "in review" m
 
 Analyze Change Request
 ----------------------
-The projects :need:`[[title]] <rl__technical_lead>` or :need:`[[title]] <rl__module_lead>` supported by
+The projects :need:`[[title]] <rl__project_lead>` supported by
 :need:`[[title]] <rl__committer>` (includes Safety, Security and Quality Manager) analyzes the change
 request together with the :need:`[[title]] <rl__contributor>` and takes a decision with
 the submitting/authoring contributor for accepting or rejecting it.
@@ -241,8 +241,8 @@ When ready to implement, the author sets the status to "in implementation" manua
   | * The **Development** section should be used to link to an pull request
   | * The **Create a branch** action may used to create automatically a linked pull request
 
-During the implementation of the change the responsible lead :need:`[[title]] <rl__technical_lead>`
-or :need:`[[title]] <rl__module_lead>` reports regularly the status to the affected
+During the implementation of the change the responsible lead :need:`[[title]] <rl__project_lead>`
+reports regularly the status to the affected
 projects teams.
 
 The author has the freedom to cancel the change request at any time by setting the status to "rejected".
@@ -262,7 +262,7 @@ is sufficient before the status is changed to closed. To check, if it is suffici
 Further the effectiveness of the implemented measure is confirmed and the availability
 of the required reports, as well as verification results, if applicable.
 
-When confirmed, the :need:`[[title]] <rl__technical_lead>` or :need:`[[title]] <rl__module_lead>`
+When confirmed, the :need:`[[title]] <rl__project_lead>`
 sets the status to "closed" manually, if not done automatically.
 
 .. note::

process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst

@@ -53,7 +53,7 @@ Estimates for realization
 [Describe here which stakeholder and which roles of the stakeholder are involved to execute the Change Request]
 
    .. note::
-      Typically the :need:`Technical Project Leads <rl__technical_lead>` or :need:`Module Leads <rl__module_lead>` are involved
+      Typically the :need:`Project Leads <rl__project_lead>` are involved
       for planning and approval activities. As well as :need:`Safety Manager <rl__safety_manager>` or :need:`Security Manager <rl__security_manager>`
       are responsible for Change Request which has impact on functional safety or security.
 

process/process_areas/configuration_management/configuration_concept.rst

@@ -42,7 +42,7 @@ Inputs
 Stakeholders
 ^^^^^^^^^^^^
 
-#. :need:`Technical Lead <rl__technical_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 
    * for creating a module or a platform release a baseline of all configuration items is needed
 

process/process_areas/configuration_management/configuration_getstrt.rst

@@ -19,7 +19,7 @@ Getting Started
    :id: doc_getstrt__configuration_process
    :status: valid
 
-In case you are appointed as a :need:`Technical Lead <rl__technical_lead>` by the :need:`rl__project_lead` in the project:
+In case you are appointed as a :need:`rl__project_lead` in the project:
 
 * On platform level, process community provides a draft configuration management plan,
   based on the template :need:`gd_temp__config_mgt_plan`, just set it to "valid"