diff --git a/docs/platform_management_plan/project_management.rst b/docs/platform_management_plan/project_management.rst index a7cb0c2a89..d3bfaa4bf5 100644 --- a/docs/platform_management_plan/project_management.rst +++ b/docs/platform_management_plan/project_management.rst @@ -1,6 +1,6 @@ .. # ******************************************************************************* - # Copyright (c) 2024 Contributors to the Eclipse Foundation + # Copyright (c) 2026 Contributors to the Eclipse Foundation # # See the NOTICE file(s) distributed with this work for additional # information regarding copyright ownership. @@ -29,7 +29,7 @@ Purpose +++++++ The purpose of the Project Management Plan is to define -- how to manage, analyse and control changes of the work products during the project life cycle. +- how to manage, analyze and control changes of the work products during the project life cycle. - the project stakeholder and how to communicate with them. - how and where to create and maintain the project schedule. - how to track planned work. @@ -75,47 +75,9 @@ Steering Committees ^^^^^^^^^^^^^^^^^^^ Steering of the project is done with the help of *Lead Circles*. -.. _PLCTLCMBRS: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _PLCTLCSPK: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _PLCTLCMM: https://github.com/eclipse-score/score/wiki/TLCM -.. _PLCTLCSLC: https://sdvworkinggroup.slack.com/archives/C085F44D2CS -.. _PLCTLCBKL: https://github.com/orgs/eclipse-score/projects/3 - -.. list-table:: Steering - :header-rows: 1 - :widths: 22,7,7,7,7,7,24 - - * - Purpose - - Members - - Speaker - - Meeting Minutes - - Slack Channel - - Backlog - - Owned Repository - - * - .. _pmp_pm_plctlc: - - **PLC/TLC** - - **Project/Technical** - - **Lead** - - **Circle** - - **-----------** - - **-----------** - - **-----------------------** - * - - Decisions about strategical topics - - Review and approval of contributions, e.g. Feature Requests, which add or modify features - - Project Management - - High-level project control and coordination between multiple software modules. - - Deciding of adding / removing Repositories - - Planning and Approval of Releases - - Escalation instance - - - `PLCTLCMBRS`_ - - `PLCTLCSPK`_ - - `PLCTLCMM`_ - - `PLCTLCSLC`_ - - `PLCTLCBKL`_ - - - https://github.com/eclipse-score/score +.. _pmp_pm_lc: + +- `TLC - Technical Lead Circle `_ .. _pmp_pm_communities: @@ -125,182 +87,17 @@ Communities commonly used development & testing infrastructure, processes or final integration & release. Each *Community* has a *Community Lead* to organize the community`s work. -.. _ARCMBRS: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _ARCLD: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _ARCMM: https://github.com/eclipse-score/score/wiki/ARCM -.. _ARCSLC: https://sdvworkinggroup.slack.com/archives/C08C1HG5AKY -.. _ARCBKL: https://github.com/orgs/eclipse-score/projects/3 - -.. _INFMBRS: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _INFLD: https://github.com/eclipse-score/score/blob/main/.github/CODEOWNERS -.. _INFMM: https://github.com/eclipse-score/score/wiki/INFM -.. _INFSLC: https://sdvworkinggroup.slack.com/archives/C0894QGRZDM -.. _INFBKL: https://github.com/orgs/eclipse-score/projects/6 - -.. _PRCMBRS: https://github.com/eclipse-score/process_description/blob/main/.github/CODEOWNERS -.. _PRCLD: https://github.com/eclipse-score/process_description/blob/main/.github/CODEOWNERS -.. _PRCMM: https://github.com/eclipse-score/score/wiki/PRCM -.. _PRCSLC: https://sdvworkinggroup.slack.com/archives/C0864L05332 -.. _PRCBKL: https://github.com/orgs/eclipse-score/projects/21 -.. _PIMBKL: https://github.com/orgs/eclipse-score/projects/7 - -.. _TSTMBRS: https://github.com/eclipse-score/itf/blob/main/.github/CODEOWNERS -.. _TSTLD: https://github.com/eclipse-score/itf/blob/main/.github/CODEOWNERS -.. _TSTMM: https://github.com/eclipse-score/score/wiki/TSTM -.. _TSTSLC: https://sdvworkinggroup.slack.com/archives/TSTC08B6C78EF3 -.. _TSTBKL: https://github.com/orgs/eclipse-score/projects/5 - -.. _INTMBRS: https://github.com/eclipse-score/reference_integration/blob/main/.github/CODEOWNERS -.. _INTLD: https://github.com/eclipse-score/reference_integration/blob/main/.github/CODEOWNERS -.. _INTMM: https://github.com/eclipse-score/score/wiki/INTM -.. _INTSLC: https://sdvworkinggroup.slack.com/archives/INT -.. _INTBKL: https://github.com/orgs/eclipse-score/projects/INT - -.. _MCMMBRS: https://github.com/orgs/eclipse-score/teams/automotive-score-MCM-team -.. _MCMLD: https://github.com/orgs/eclipse-score/teams/automotive-score-MCM-lead -.. _MCMMM: https://github.com/eclipse-score/score/wiki/MCMM -.. _MCMSLC: https://sdvworkinggroup.slack.com/archives/C032X75QGTT -.. _MCMBKL: https://github.com/orgs/eclipse-score/projects/11 - - -.. list-table:: Community - :header-rows: 1 - :widths: 22,7,7,7,7,7,24 - - * - Purpose - - Members - - Lead - - Meeting Minutes - - Slack Channel - - Backlog - - Owned Repository - * - .. _pmp_pm_arc: - - **ARC** - - **Architecture** - - **Community** - - **-----------** - - **-----------** - - **-----------** - - **-----------------------** - * - - clarification of software architecture topics, e.g. discussion of new features or coding guidelines - - `ARCMBRS`_ - - `ARCLD`_ - - `ARCMM`_ - - `ARCSLC`_ - - `ARCBKL`_ - - https://github.com/eclipse-score/score - * - .. _pmp_pm_prc: - - **PRC** - - **Process** - - **Community** - - **-----------** - - **-----------** - - **-----------** - - **-----------------------** - * - - defining and maintaining the software development process (incl. safety, security and quality) - - defining and maintaining the process implementation (PIM) - - `PRCMBRS`_ - - `PRCLD`_ - - `PRCMM`_ - - `PRCSLC`_ - - `PRCBKL`_ - `PIMBKL`_ - - | https://github.com/eclipse-score/process_description - | https://github.com/eclipse-score/score - * - .. _pmp_pm_inf: - - **INF** - - **Infrastructure** - - **Community** - - **-----------** - - **-----------** - - **-----------** - - **-----------------------** - * - - providing and maintaining the development infrastructure: Compiler, IDE, build toolchains - - `INFMBRS`_ - - `INFLD`_ - - `INFMM`_ - - `INFSLC`_ - - `INFBKL`_ - - | Toolchain Repositories: - - | https://github.com/eclipse-score/bazel_platforms - | https://github.com/eclipse-score/toolchains_gcc - | https://github.com/eclipse-score/toolchains_gcc_packages - | https://github.com/eclipse-score/toolchains_qnx - | https://github.com/eclipse-score/toolchains_rust - - | Tooling Repositories: - - | https://github.com/eclipse-score/devcontainer - | https://github.com/eclipse-score/docs-as-code - | https://github.com/eclipse-score/tooling - - | other Repositories: - - | https://github.com/eclipse-score/apt-install - | https://github.com/eclipse-score/cicd-workflows - | https://github.com/eclipse-score/bazel_registry - | https://github.com/eclipse-score/bazel_registry_ui - | https://github.com/eclipse-score/.eclipsefdn - | https://github.com/eclipse-score/examples - - * - .. _pmp_pm_tst: - - **TST** - - **Testing** - - **Community** - - **-----------** - - **-----------** - - **-----------** - - **-----------------------** - * - defining and maintaining testing strategy and infrastructure - - `TSTMBRS`_ - - `TSTLD`_ - - `TSTMM`_ - - `TSTSLC`_ - - `TSTBKL`_ - - | https://github.com/eclipse-score/itf - | https://github.com/eclipse-score/testing_tools - * - .. _pmp_pm_int: - - **INT** - - **Integration &** - - **Release** - - **Community** - - **-----------** - - **-----------** - - **-----------------------** - * - - integration of available modules to one or several reference integrations - - releasing - - - `INTMBRS`_ - - `INTLD`_ - - `INTMM`_ - - `INTSLC`_ - - `INTBKL`_ - - | https://github.com/eclipse-score/reference_integration - * - .. _pmp_pm_mcm: - - **MCM** - - **Integration &** - - **Release** - - **Community** - - **-----------** - - **-----------** - - **-----------------------** - * - - coordination of public relations, e.g. the maintenance of the website & organization of general events - - `MCMMBRS`_ - - `MCMLD`_ - - `MCMMM`_ - - `MCMSLC`_ - - `MCMBKL`_ - - | https://github.com/eclipse-score/eclipse-score.github.io - | https://github.com/eclipse-score/eclipse-score-website - | https://github.com/eclipse-score/eclipse-score-website-preview - | https://github.com/eclipse-score/eclipse-score-website-published +.. _pmp_pm_arc: + +- `ARC - Architecture Community `_ +- `PRC - Process Community `_ +- `INF - Infrastructure Community `_ +- `TST - Testing Community `_ +- `REL - Release Community `_ + +.. _pmp_pm_mcm: + +- `MCM - Marketing and Communication Community `_ .. _pmp_pm_feature_teams: @@ -312,224 +109,17 @@ One *Team* may work independently of other *Teams* on the team-assigned *GitHub and needs at least one :need:`Committer ` who can approve & merge the Pull Requests. Each *Feature Team* has one *Lead* to organize the Team`s work. -.. _BASMBRS: https://github.com/eclipse-score/baselibs/blob/main/.github/CODEOWNERS -.. _BASLD: https://github.com/eclipse-score/baselibs/blob/main/.github/CODEOWNERS -.. _BASMM: https://github.com/eclipse-score/score/wiki/BASM -.. _BASSLC: https://sdvworkinggroup.slack.com/archives/C090UKSL5L2 -.. _BASBKL: https://github.com/orgs/eclipse-score/projects/24 - -.. _COMMBRS: https://github.com/eclipse-score/communication/blob/main/.github/CODEOWNERS -.. _COMLD: https://github.com/eclipse-score/communication/blob/main/.github/CODEOWNERS -.. _COMMM: https://github.com/eclipse-score/score/wiki/COMM -.. _COMSLC: https://sdvworkinggroup.slack.com/archives/C08C0JATADP -.. _COMBKL: https://github.com/orgs/eclipse-score/projects/19 - -.. _CFGMBRS: https://github.com/eclipse-score/inc_config_management/blob/main/.github/CODEOWNERS -.. _CFGLD: https://github.com/eclipse-score/inc_config_management/blob/main/.github/CODEOWNERS -.. _CFGMM: https://github.com/eclipse-score/score/wiki/CFGM -.. _CFGSLC: https://sdvworkinggroup.slack.com/archives/CFG -.. _CFGBKL: https://github.com/orgs/eclipse-score/projects/CFG - -.. _FEOMBRS: https://github.com/eclipse-score/feo/blob/main/.github/CODEOWNERS -.. _FEOLD: https://github.com/eclipse-score/feo/blob/main/.github/CODEOWNERS -.. _FEOMM: https://github.com/eclipse-score/score/wiki/FEOM -.. _FEOSLC: https://sdvworkinggroup.slack.com/archives/FEO -.. _FEOBKL: https://github.com/orgs/eclipse-score/projects/9 - -.. _KYRMBRS: https://github.com/eclipse-score/kyron/blob/main/.github/CODEOWNERS -.. _KYRLD: https://github.com/eclipse-score/kyron/blob/main/.github/CODEOWNERS -.. _KYRMM: https://github.com/eclipse-score/score/wiki/KYRM -.. _KYRSLC: https://sdvworkinggroup.slack.com/archives/KYR -.. _KYRBKL: https://github.com/orgs/eclipse-score/projects/38 - -.. _LCMMBRS: https://github.com/eclipse-score/lifecycle/blob/main/.github/CODEOWNERS -.. _LCMLD: https://github.com/eclipse-score/lifecycle/blob/main/.github/CODEOWNERS -.. _LCMMM: https://github.com/eclipse-score/score/wiki/LCMM -.. _LCMSLC: https://sdvworkinggroup.slack.com/archives/C094Z3BN1K4 -.. _LCMBKL: https://github.com/orgs/eclipse-score/projects/33 - -.. _LOGMBRS: https://github.com/eclipse-score/logging/blob/main/.github/CODEOWNERS -.. _LOGLD: https://github.com/eclipse-score/logging/blob/main/.github/CODEOWNERS -.. _LOGMM: https://github.com/eclipse-score/score/wiki/LOGM -.. _LOGSLC: https://sdvworkinggroup.slack.com/archives/C089XP2PGQZ -.. _LOGBKL: https://github.com/orgs/eclipse-score/projects/31 - -.. _ORCMBRS: https://github.com/eclipse-score/orchestrator/blob/main/.github/CODEOWNERS -.. _ORCLD: https://github.com/eclipse-score/orchestrator/blob/main/.github/CODEOWNERS -.. _ORCMM: https://github.com/eclipse-score/score/wiki/ORCM -.. _ORCSLC: https://sdvworkinggroup.slack.com/archives/C099W80FU2C -.. _ORCBKL: https://github.com/orgs/eclipse-score/projects/29 - -.. _PERMBRS: https://github.com/eclipse-score/persistency/blob/main/.github/CODEOWNERS -.. _PERLD: https://github.com/eclipse-score/persistency/blob/main/.github/CODEOWNERS -.. _PERMM: https://github.com/eclipse-score/score/wiki/PERM -.. _PERSLC: https://sdvworkinggroup.slack.com/archives/C08B339ETQU -.. _PERBKL: https://github.com/orgs/eclipse-score/projects/20 - -.. list-table:: Feature Teams - :header-rows: 1 - :widths: 22,7,7,7,7,7,24 - - * - Purpose - - Members - - Lead - - Meeting Minutes - - Slack Channel - - Backlog - - Owned Repository - * - .. _pmp_pm_bas: - - **BAS** - - **Baselibs** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of the base libraries - - `BASMBRS`_ - - `BASLD`_ - - `BASMM`_ - - `BASSLC`_ - - `BASBKL`_ - - | https://github.com/eclipse-score/baselibs - | https://github.com/eclipse-score/baselibs_rust - * - .. _pmp_pm_com: - - **COM** - - **Communication** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of the communication and protocols - - `COMMBRS`_ - - `COMLD`_ - - `COMMM`_ - - `COMSLC`_ - - `COMBKL`_ - - | https://github.com/eclipse-score/communication - | https://github.com/eclipse-score/inc_mw_com - | https://github.com/eclipse-score/inc_someip_gateway - * - .. _pmp_pm_cfg: - - **CFG** - - **Configuration** - - **Management** - - **Feature** - - **Team** - - **-----------** - - **-----------------------** - * - - development of configuration management - - `CFGMBRS`_ - - `CFGLD`_ - - `CFGMM`_ - - `CFGSLC`_ - - `CFGBKL`_ - - | https://github.com/eclipse-score/config_management - | https://github.com/eclipse-score/inc_config_management - * - .. _pmp_pm_feo: - - **FEO** - - **Fixed** - - **Execution** - - **Order** - - **Feature** - - **Team** - - **-----------------------** - * - - development of fixed execution order - - `FEOMBRS`_ - - `FEOLD`_ - - `FEOMM`_ - - `FEOSLC`_ - - `FEOBKL`_ - - | https://github.com/eclipse-score/feo - | https://github.com/eclipse-score/inc_feo - * - .. _pmp_pm_kyr: - - **KYR** - - **Kyron** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of Kyron - - `KYRMBRS`_ - - `KYRLD`_ - - `KYRMM`_ - - `KYRSLC`_ - - `KYRBKL`_ - - | https://github.com/eclipse-score/kyron - * - .. _pmp_pm_log: - - **LOG** - - **Logging** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of Logging - - `LOGMBRS`_ - - `LOGLD`_ - - `LOGMM`_ - - `LOGSLC`_ - - `LOGBKL`_ - - | https://github.com/eclipse-score/logging - | https://github.com/eclipse-score/inc_mw_log - - * - .. _pmp_pm_lcm: - - **LCM** - - **Lifecycle** - - **Management &** - - **Health Monitoring** - - **Feature** - - **Team** - - **-----------------------** - * - - development of Lifecycle Management and Health Monitoring - - `LCMMBRS`_ - - `LCMLD`_ - - `LCMMM`_ - - `LCMSLC`_ - - `LCMBKL`_ - - | https://github.com/eclipse-score/lifecycle - - * - .. _pmp_pm_ocr: - - **OCR** - - **Orchestrator** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of Orchestrator - - `ORCMBRS`_ - - `ORCLD`_ - - `ORCMM`_ - - `ORCSLC`_ - - `ORCBKL`_ - - | https://github.com/eclipse-score/orchestrator - - * - .. _pmp_pm_per: - - **PER** - - **Persistency** - - **Feature** - - **Team** - - **-----------** - - **-----------** - - **-----------------------** - * - - development of Persistency - - `PERMBRS`_ - - `PERLD`_ - - `PERMM`_ - - `PERSLC`_ - - `PERBKL`_ - - | https://github.com/eclipse-score/persistency +- `BAS - Baselibs Feature Team `_ +- `COM - Communication Feature Team `_ +- `CFG - Configuration Feature Team `_ +- `DIA - Diagnostics Feature Team `_ +- `FEO - Fixed Execution Order Feature Team `_ +- `LCM - Lifecycle Feature Team `_ +- `LOG - Logging Feature Team `_ +- `ORC - Orchestration Feature Team `_ +- `PER - Persistency Feature Team `_ +- `SEC - Security Feature Team `_ +- `TIM - Timings Feature Team `_ Organization Management ^^^^^^^^^^^^^^^^^^^^^^^ @@ -549,7 +139,7 @@ In case a new Feature Team creation is necessary, the following steps have to be `orgs.newRepo `_. - Definition of Repository specific :ref:`CODEOWNERS `. - `Creation of a Team GitHub Project `_ with a Kanban View and a Task View. -- `Creation of a Team Meeting Wiki `_ for the meeting minutes +- `Creation of a Team Discussion `_ for basic information and meeting minutes etc. - Creation of a Team Label .. code:: @@ -616,7 +206,7 @@ within the following :ref:`Module Folder Structure `. Codeowners ^^^^^^^^^^ -While creating a new repository, :ref:`Project / Technical Leads ` nominate initial `CODEOWNERS `_, +While creating a new repository, :ref:`Project / Technical Leads ` nominate initial `CODEOWNERS `_, whose review is mandatory for merging PRs to the repository and who are at the end allowed to merge PRs to the repository as well as maintaining it. Possible members are software developers , who @@ -635,11 +225,11 @@ Cadence Iteration """"""""" -The Project calendar is devided into iterations. Each iteration is two weeks long. +The Project calendar is divided into iterations. Each iteration is two weeks long. -Release Frequence +Release Frequency """"""""""""""""" -After every 3rd iteration, the work is baselined into a Release. +After every 4th iteration, the work is released and baseline is created. Planning & Tracking Infrastructure @@ -676,7 +266,7 @@ Architectural Issues A *Feature Request* represents an independent work package used to describe and track a high-level request for the project. *Feature Request* work packages can be linked to other work packages, but they must not be treated as parent work packages. *Feature Request* covers new Features as well as significant modifications of existing Features. -They are in the responsibility of the :ref:`Architecture Community `, shall aligned with :ref:`Project / Technical Lead Circle ` and the issues are part of the :ref:`Root Repository `. +They are in the responsibility of the :ref:`Architecture Community `, shall aligned with :ref:`Lead Circle ` and the issues are part of the :ref:`Root Repository `. `About Features `_ @@ -706,7 +296,7 @@ A *Product Increment* represents the highest level in the work package hierarchy cannot be linked as a child of another issue. If you need to group multiple *Product Increment* work packages, labels have to be used. One *Product Increment* is the planning element for a version of a :ref:`Module `. A *Product Increment* can have multiple *Epic* work packages as children. *Product Increments* are owned by -:ref:`Project / Technical Lead Circle ` and are part of the :ref:`Root Repository `. +:ref:`Lead Circle ` and are part of the :ref:`Root Repository `. `Product Increment issue template `_ @@ -806,7 +396,7 @@ a Release or a Process Audit, etc. Releases ^^^^^^^^ -*Releases* are special milestones and used for baselining of the development activities. +*Releases* are special milestones and used to baseline the development activities. .. _pmp_pm_gh_labels: @@ -855,7 +445,7 @@ The `GitHub Table `_ is supporting the Road View, provididing a high-level visualization of your project across a configurable timespan. +The `GitHub Roadmap `_ is supporting the Road View, providing a high-level visualization of your project across a configurable time span. Traceability ^^^^^^^^^^^^ @@ -868,7 +458,7 @@ Planning of Work Generally, every team is responsible for planning its work within its own plan with the help of its :ref:`GitHub Project ` filled with :ref:`Epics `, :ref:`Tasks ` and :ref:`Bugs `. The planning of :ref:`Feature Requests ` and :ref:`Component Requests ` is in the responsibility of the :ref:`Architects `, -whereas the overall top-down plan is in the responsibility of the :ref:`Project / Technical Lead Circle ` with the help of :ref:`Product Increments `, +whereas the overall top-down plan is in the responsibility of the :ref:`Lead Circle ` with the help of :ref:`Product Increments `, :ref:`Milestones ` and :ref:`Releases `. .. image:: _assets/score_project_management_process_issue_overview.drawio.svg @@ -881,13 +471,11 @@ whereas the overall top-down plan is in the responsibility of the :ref:`Project Tracking Progress ^^^^^^^^^^^^^^^^^ -The :ref:`Project / Technical Lead Circle ` regularly monitors the status of the work for upcoming Milestones and Releases in https://github.com/orgs/eclipse-score/projects/17/ based on +The :ref:`Lead Circle ` regularly monitors the status of the work for upcoming Milestones and Releases in https://github.com/orgs/eclipse-score/projects/17/ based on :ref:`Product Increments `. Dashboards """""""""" -GitHub offers mechanism in form of charts to track issues: - -- `Product Increments Open last 3 months `_ +GitHub offers mechanism in form of charts to track issues see `Insights `_.