Cross-VM IPC (#916)

.devcontainer/devcontainer.json

@@ -1,4 +1,4 @@
 {
     "name": "eclipse-s-core",
-    "image": "ghcr.io/eclipse-score/devcontainer:1.0.0"
+    "image": "ghcr.io/eclipse-score/devcontainer:v1.1.0"
 }

.github/CODEOWNERS

@@ -6,44 +6,44 @@
 # Note: last match wins
 
 # By Default reviews go to the infrastructure community, to address missing lines in this document.
-*                                     @AlexanderLanin @dcalavrezo-qorix
+*                                     @AlexanderLanin @dcalavrezo-qorix @MaximilianSoerenPollak
 
 # All special files go to infrastructure as well
-.*                                    @AlexanderLanin @dcalavrezo-qorix
+.*                                    @AlexanderLanin @dcalavrezo-qorix @MaximilianSoerenPollak
 
-.github/ISSUE_TEMPLATE/               @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
+.github/ISSUE_TEMPLATE/               @pahmann @masc2023 @aschemmel-tech @PandaeDo
 .github/CODEOWNERS                    @antonkri @FScholPer @qor-lb @johannes-esr
 
-/docs/                                @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
-/docs/conf.py                         @AlexanderLanin @dcalavrezo-qorix
+/docs/                                @pahmann @masc2023 @aschemmel-tech @PandaeDo
+/docs/conf.py                         @AlexanderLanin @dcalavrezo-qorix @MaximilianSoerenPollak
 /docs/contribute/                     @eclipse-score/automotive-score-committers
 # /docs/features/                     @eclipse-score/automotive-score-technical-leads
 /docs/features/                       @antonkri @FScholPer @qor-lb @johannes-esr
 architecture/                         @eclipse-score/automotive-score-committers
 # requirements/                       @eclipse-score/automotive-score-technical-leads
 requirements/                         @antonkri @FScholPer @qor-lb @johannes-esr
 # safety_analysis/                    @eclipse-score/safety-managers
-safety_analysis/                      @aschemmel-tech @PhilipPartsch @masc2023
+safety_analysis/                      @aschemmel-tech @masc2023 @PandaeDo
 # safety_planning/                    @eclipse-score/automotive-score-technical-leads
 safety_planning/                      @antonkri @FScholPer @qor-lb @johannes-esr
 verification/                         @eclipse-score/automotive-score-committers
-/docs/design_decisions/*infra*        @AlexanderLanin @dcalavrezo-qorix
+/docs/design_decisions/*infra*        @AlexanderLanin @dcalavrezo-qorix @MaximilianSoerenPollak
 /docs/glossary/                       @eclipse-score/automotive-score-committers
 /docs/introduction/                   @eclipse-score/automotive-score-committers
 /docs/manuals/                        @eclipse-score/automotive-score-committers
 /docs/modules/                        @eclipse-score/automotive-score-committers
 # /docs/platform_management_plan/     @eclipse-score/community-process
-/docs/platform_management_plan/       @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
+/docs/platform_management_plan/       @pahmann @masc2023 @aschemmel-tech @PandaeDo
 # /docs/quality/                      @eclipse-score/quality-managers
 /docs/quality/                        @masc2023 @pahmann @PandaeDo
 # /docs/requirements/stakeholder/     @eclipse-score/automotive-score-technical-leads
 /docs/requirements/stakeholder/       @antonkri @FScholPer @qor-lb @johannes-esr
 # /docs/requirements/tool/            @eclipse-score/community-process
-/docs/requirements/tool/              @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
+/docs/requirements/tool/              @pahmann @masc2023 @aschemmel-tech @PandaeDo
 # /docs/safety/                       @eclipse-score/safety-managers
-/docs/safety/                         @aschemmel-tech @PhilipPartsch @masc2023 @PandaeDo
+/docs/safety/                         @aschemmel-tech @masc2023 @PandaeDo
 # /docs/score_releases/               @eclipse-score/automotive-score-project-leads
-/docs/score_releases/                 @thilo-schmitt @HartmannNico @skappel29 @grandyholger
+/docs/score_releases/                 @thilo-schmitt @HartmannNico @skappel29 @grandyholger @antonkri @FScholPer @qor-lb @johannes-esr
 /docs/score_tools/                    @eclipse-score/automotive-score-committers
 # /docs/security/                     @eclipse-score/security-managers
 /docs/security/                       @masc2023 @PandaeDo
@@ -52,4 +52,4 @@ verification/                         @eclipse-score/automotive-score-committers
 
 /platform_integration_tests/          @eclipse-score/automotive-score-committers
 # /tools/                             @eclipse-score/infrastructure-maintainers
-/tools/                               @AlexanderLanin @dcalavrezo-qorix
+/tools/                               @AlexanderLanin @dcalavrezo-qorix @MaximilianSoerenPollak

.github/ISSUE_TEMPLATE/1-bugfix.yml

@@ -15,6 +15,7 @@ name: Problem Report
 description: Issue to track a bug
 title: "Bug: Your bugfix title"
 labels: ["codeowner_review"]
+type: 'Bug'
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -11,4 +11,4 @@
 # SPDX-License-Identifier: Apache-2.0
 # *******************************************************************************
 
-blank_issues_enabled: true
+blank_issues_enabled: false

.gitignore

@@ -27,3 +27,7 @@ __pycache__/
 
 # Mac
 .DS_Store
+
+# IDE
+/.clwb
+/.idea

.vscode/settings.json

@@ -88,8 +88,12 @@
     },
     "cSpell.words": [
         "__getitem__",
+        "baselibs",
         "bazel",
         "buildifier",
+        "Codeowner",
+        "codeowners",
+        "docname",
         "getstrt",
         "metatags",
         "reqs"

CONTRIBUTION.md

@@ -1,35 +1,61 @@
-# Eclipse Safe Open Vehicle Core (SCORE)
+# Eclipse Safe Open Vehicle Core (S-CORE)
 The [Eclipse Safe Open Vehicle Core](https://projects.eclipse.org/projects/automotive.score) project aims to develop an open-source core stack for Software Defined Vehicles (SDVs), specifically targeting embedded high-performance Electronic Control Units (ECUs).
-Please check the [documentation](https://eclipse-score.github.io) for more information.
+Please check the [documentation](https://eclipse-score.github.io/score/main/) for more information.
 The source code is hosted at [GitHub](https://github.com/eclipse-score).
 
-The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev) and GitHub issues & pull requests (PR). And we have a chatroom for community discussions here [Eclipse SCORE chatroom](https://chat.eclipse.org/#/room/#automotive.score:matrix.eclipse.org).
+The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev), [Discussions](https://github.com/orgs/eclipse-score/discussions) and GitHub issues & pull requests (PR).
+We have a Slack channel for community discussions here [Eclipse S-CORE Slack Channel](https://sdvworkinggroup.slack.com/archives/C083Z4VL90B).
 
-Please note that for the project the [Eclipse Foundation’s Terms of Use](https://www.eclipse.org/legal/terms-of-use/) apply.
-In addition, you need to sign the [ECA](https://www.eclipse.org/legal/ECA.php) and the [DCO](https://www.eclipse.org/legal/dco/) to contribute to the project.
 
 ## Contributing
+
+### Code of Conduct
+
+Please be familiar with the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Eclipse Contributor Agreement & Developer Certificate of Origin
+
+Please note that for the project the [Eclipse Foundation’s Terms of Use](https://www.eclipse.org/legal/terms-of-use/) apply.
+
+Before your contribution can be accepted by the project team contributors must
+electronically sign the Eclipse Contributor Agreement (ECA).
+
+* https://www.eclipse.org/legal/eca/
+
+
+For more information, please see the Eclipse Committer Handbook:
+https://www.eclipse.org/projects/handbook/#resources-commit
+
+To complete and submit a ECA, log into the
+[Eclipse projects forge](https://www.eclipse.org/contribute/cla/)
+(you will need to create an account with the Eclipse Foundation if you have not already done so).
+Click on "Eclipse Contributor Agreement" and complete the form.
+Be sure to use the same email address when you register for the account
+that you intend to use when you commit to Git.
+
+In addition, you need to sign the [DCO](https://www.eclipse.org/legal/dco/) to contribute to the project.
+
+
 ### Getting the source code & building the project
 Please refer to the [README.md](README.md) for further information.
 
 ### Getting involved
 
 #### Setup Phase
-This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on non-functional Stakeholder_Requirements<!-- TODO: fill link to correct page with requirements -->. During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure).
+This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on [Non-functional Stakeholder_Requirements](https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html). During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure).
 
 #### Bug Fixes and Improvements
 Improvements are adding/changing processes and infrastructure, bug fixes can be also on development work products like code.
 In case you want to fix a bug or contribute an improvement, please perform the following steps:
 1) Create a PR by using the corresponding template ([Bugfix PR template](.github/PULL_REQUEST_TEMPLATE/bug_fix.md) or [Improvement PR template](.github/PULL_REQUEST_TEMPLATE/improvement.md)). Please mark your PR as draft until it's ready for review by the Committers (see the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#contributing-committers) for more information on the role definitions). Improvements are requested by the definition or modification of [Stakeholder Requirements](docs/stakeholder_requirements) or [Tool Requirements](docs/tool_requirements) and may be implemented after acceptance/merge of the request by a second Improvement PR. The needed reviews are automatically triggered via the [CODEOWNERS](.github/CODEOWNERS) file in the repository.
 2) Initiate content review by opening a corresponding issue for the PR when it is ready for review. Review of the PR and final merge into the project repository is in responsibility of the Committers. Use the [Bugfix Issue template](.github/ISSUE_TEMPLATE/bug_fix.md) or [Improvement Issue template](.github/ISSUE_TEMPLATE/improvement.md) for this.
 
-Please check here for our Git Commit Rules in the [Configuration_Tool_Guidelines](https://eclipse-score.github.io/score/process_description/guidelines/index.html).
+Please check here for our Git Commit Rules in the [Git Guidelines](https://eclipse-score.github.io/score/main/contribute/general/git.html).
 
-Please use the [Stakeholder and Tool Requirements Template](https://eclipse-score.github.io/score/process_description/templates/index.html) when defining these requirements.
 
 ![Contribution guide workflow](./docs/_assets/contribution_guide.svg "Contribution guide workflow")
 
 #### Additional Information
 Please note, that all Git commit messages must adhere the rules described in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#resources-commit).
 
-Please find process descriptions here: [process description](https://eclipse-score.github.io/score/process_description/).
+Please find process descriptions here: [process description](https://eclipse-score.github.io/process_description/main/index.html).

MODULE.bazel

@@ -13,7 +13,7 @@
 
 module(
     name = "score_platform",
-    version = "0.4.2",
+    version = "0.5.2",
     compatibility_level = 0,
 )
 
@@ -22,11 +22,11 @@ module(
 # Python version
 #
 ###############################################################################
-bazel_dep(name = "rules_python", version = "1.4.1")
+bazel_dep(name = "rules_python", version = "1.8.3")
 
 PYTHON_VERSION = "3.12"
 
-python = use_extension("@rules_python//python/extensions:python.bzl", "python")
+python = use_extension("@rules_python//python/extensions:python.bzl", "python", dev_dependency = True)
 python.toolchain(
     configure_coverage_tool = True,
     is_default = True,
@@ -36,7 +36,7 @@ use_repo(python)
 
 # Additional Python rules provided by aspect, e.g. an improved version of
 # `py_binary`. But more importantly, it provides `py_venv`.
-bazel_dep(name = "aspect_rules_py", version = "1.6.3")
+bazel_dep(name = "aspect_rules_py", version = "1.6.6", dev_dependency = True)
 
 ###############################################################################
 #
@@ -72,6 +72,6 @@ bazel_dep(name = "rules_java", version = "8.15.1")
 # Score custom modules loading
 #
 ###############################################################################
-bazel_dep(name = "score_tooling", version = "1.0.2")
-bazel_dep(name = "score_docs_as_code", version = "2.1.0")
-bazel_dep(name = "score_process", version = "1.3.2")
+bazel_dep(name = "score_tooling", version = "1.1.0")
+bazel_dep(name = "score_docs_as_code", version = "3.0.0")
+bazel_dep(name = "score_process", version = "1.4.3")

docs/contribute/contribution_request/index.rst

@@ -112,7 +112,7 @@ The figure below shows a simplified workflow for a PR.
 
 Content in general may contain features, requirements, architectural designs, modules, components, detailed designs, implementations and source code, tests, process descriptions, any documentations, guidelines, tutorials, tools, or infrastructure topics and more of the *S-CORE* project. In case of doubt or for any other input we strongly encourage to open a *GitHub Issue* (:need:`doc__issue_guideline`) first.
 
-The *PR* should provide all required information of the new or changed content. Therefore the *S-CORE* project provides content specific templates, which the contributor (:need:`Contributor <rl__contributor>`) must use for his *PR* (ToDo link here to the templates overview). Templates may be *PR* templates, *GitHub Issue* templates and also additional document or work product templates.
+The *PR* should provide all required information of the new or changed content. Therefore the *S-CORE* project provides content specific templates, which the contributor (:need:`Contributor <rl__contributor>`) must use for their *PR* (ToDo link here to the templates overview). Templates may be *PR* templates, *GitHub Issue* templates and also additional document or work product templates.
 
 The content of any *PR* is the commit content and the description as well as the comments given in GitHub and is kept in a versioned repository, their revision history is the historical record of the PR.
 

docs/contribute/development/index.rst

@@ -19,6 +19,7 @@ Development
    :maxdepth: 1
 
    development_environment
+   traceability_tooling
    api_guideline
    cpp/index
    rust/index

docs/contribute/development/python/coding_guidelines.rst

@@ -67,6 +67,7 @@ Testing
   implementation details. Overly fine-grained tests lead to brittle code and high maintenance.
 - **Boundary conditions:** - Edge cases often break things. Think about invalid input, large data
   sets, empty cases, and concurrency issues.
+- **Enesure Traceability** - Make sure to use the pytest decorator where applicable to enable traceabillity throughout. More infos on how to use it `example here <https://eclipse-score.github.io/docs-as-code/main/how-to/test_to_doc_links.html>`_ and `more through documentation here <https://eclipse-score.github.io/docs-as-code/main/internals/extensions/source_code_linker.html>`_ 
 
 Documentation
 --------------------