+
Skip to content

Establish the CODEOWNER file for score repo #1491

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 4, 2025
Merged

Establish the CODEOWNER file for score repo #1491

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f18d65
Establish the CODEOWNER file for score repo
aschemmel-tech Jul 23, 2025
7255fab
Establish CODEOWNERS score repo - fixes
aschemmel-tech Jul 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
98 changes: 58 additions & 40 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,46 +1,64 @@
# Comment out as not in score yet
# * @eclipse-score/infrastructure-tooling-community
# .* @eclipse-score/infrastructure-tooling-community
# .github/CODEOWNERS @eclipse-score/technical-lead
# GitHub CODEOWNERS file is a simple way to automate review system on github,
# by automatically assigning owners to a pull request based on which files
# were modified. All directories should have a proper codeowner
# Syntax: https://help.github.com/articles/about-codeowners/

# /docs @eclipse-score/process-community
# /docs/concepts @eclipse-score/automotive-score-committers
# /docs/glossary @eclipse-score/automotive-score-committers
# /docs/features @eclipse-score/technical-lead
# /docs/features/*/architecture @eclipse-score/automotive-score-committers
# /docs/features/*/requirements @eclipse-score/technical-lead
# /docs/features/*/safety_analysis @eclipse-score/safety-manager
# /docs/features/*/safety_planning @eclipse-score/safety-manager @eclipse-score/technical-lead
# /docs/features/*/verification @eclipse-score/quality-manager @eclipse-score/safety-manager
# /docs/manual @eclipse-score/automotive-score-committers
# /docs/overview @eclipse-score/project-lead
# /docs/pmp @eclipse-score/technical-lead @eclipse-score/process-community
# /docs/pmp/quality_management @eclipse-score/quality-manager
# /docs/pmp/safety_management @eclipse-score/safety-manager
# /docs/pmp/security_management @eclipse-score/security-manager
# /docs/requirements/stakeholder @eclipse-score/technical-lead
# /docs/requirements/tool @eclipse-score/infrastructure-tooling-community @eclipse-score/process-community
# /docs/release @eclipse-score/quality-manager @eclipse-score/technical-lead
# /docs/safety @eclipse-score/safety-manager @eclipse-score/technical-lead
# /docs/security @eclipse-score/security-manager @eclipse-score/technical-lead
# /docs/tutorials @eclipse-score/automotive-score-committers
# Interim solution, commented out is future solution
# * @eclipse-score/infrastructure-maintainers
* @AlexanderLanin @MaximilianSoerenPollak @dcalavrezo-qorix
# .* @eclipse-score/infrastructure-maintainers
.* @AlexanderLanin @MaximilianSoerenPollak @dcalavrezo-qorix
# .github/CODEOWNERS @eclipse-score/automotive-score-technical-leads
.github/CODEOWNERS @antonkri @FScholPer @qor-lb @johannes-esr @markert-r

# /examples @eclipse-score/automotive-score-committers
# /integration_tests @eclipse-score/automotive-score-committers
# /tools @eclipse-score/infrastructure-tooling-community
# /docs/ @eclipse-score/community-process
/docs/ @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/docs/ @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
/docs/ @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
/docs/conf.py @AlexanderLanin @MaximilianSoerenPollak @dcalavrezo-qorix

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, fixed

/docs/conf.py @AlexanderLanin @MaximilianSoerenPollak @dcalavrezo-qorix
/docs/contribute/ @eclipse-score/automotive-score-committers
# /docs/features/ @eclipse-score/automotive-score-technical-leads
/docs/features/ @antonkri @FScholPer @qor-lb @johannes-esr @markert-r
architecture/ @eclipse-score/automotive-score-committers
# requirements/ @eclipse-score/automotive-score-technical-leads
requirements/ @antonkri @FScholPer @qor-lb @johannes-esr @markert-r
# safety_analysis/ @eclipse-score/safety-managers
safety_analysis/ @aschemmel-tech @PhilipPartsch @masc2023
# safety_planning/ @eclipse-score/automotive-score-technical-leads
safety_planning/ @antonkri @FScholPer @qor-lb @johannes-esr @markert-r
verification/ @eclipse-score/automotive-score-committers
/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/automotive-score-technical-leads
/docs/platform_management_plan/ @antonkri @FScholPer @qor-lb @johannes-esr @markert-r
# /docs/quality/ @eclipse-score/quality-managers
/docs/quality/ @masc2023 @pahmann
# /docs/requirements/stakeholder/ @eclipse-score/automotive-score-technical-leads
/docs/requirements/stakeholder/ @antonkri @FScholPer @qor-lb @johannes-esr @markert-r
# /docs/requirements/tool/ @eclipse-score/community-process
/docs/requirements/tool/ @pahmann @PhilipPartsch @masc2023 @aschemmel-tech
# /docs/safety/ @eclipse-score/safety-managers
/docs/safety/ @aschemmel-tech @PhilipPartsch @masc2023
# /docs/score_releases/ @eclipse-score/automotive-score-project-leads
/docs/score_releases/ @thilo-schmitt @HartmannNico @skappel29 @grandyholger
/docs/score_tools/ @eclipse-score/automotive-score-committers
# /docs/security/ @eclipse-score/security-managers
/docs/security/ @masc2023
# /docs/verification_report @eclipse-score/automotive-score-technical-leads
/docs/verification_report @antonkri @FScholPer @qor-lb @johannes-esr @markert-r

# in separate process_description repository:
#
# /process @eclipse-score/process-community
/platform_integration_tests/ @eclipse-score/automotive-score-committers
# /tools/ @eclipse-score/infrastructure-maintainers
/tools/ @AlexanderLanin @MaximilianSoerenPollak @dcalavrezo-qorix

# in separate <module_name> repositories:
#
# /docs @eclipse-score/process-community
# /docs/manual @eclipse-score/<module_name>/safety-manager
# /docs/release @eclipse-score/<module_name>/quality-manager @eclipse-score/<module_name>/module-lead
# /docs/safety_plan @eclipse-score/<module_name>/safety-manager @eclipse-score/<module_name>/module-lead
# /docs/safety_analysis @eclipse-score/<module_name>/safety-manager
# /docs/verification @eclipse-score/<module_name>/quality-manager @eclipse-score/<module_name>/safety-manager
# /components @eclipse-score/<module_name>/technical-lead
# /components/*/ @eclipse-score/<module_name>/automotive-score-committers

# * @eclipse-score/ft-<teamname>
# .* @eclipse-score/ft-<teamname>
# /docs @eclipse-score/community-process
# /docs/manual/safety_manual @eclipse-score/safety-managers
# /docs/release @eclipse-score/automotive-score-technical-leads
# /docs/safety_mgt @eclipse-score/safety-managers
# /docs/safety_mgt/module_safety_plan @eclipse-score/automotive-score-technical-leads
# /docs/verification_report @eclipse-score/automotive-score-technical-leads
# safety_analysis/ @eclipse-score/safety-managers
88 changes: 45 additions & 43 deletions docs/contribute/general/folder.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,39 +27,38 @@ The following shows the folder structure of the platform repository (ordered alp
docs/ -> Global documentation of the platform
contribute/ -> Description on how to contribute
features/ -> All features of the platform
<feature_name>/ -> Features including sub-folders and feature (change) request
docs/ -> Documentation of the feature
architecture/ -> Feature architecture [:need:`PROCESS_wp__feature_arch`]
requirements/ -> Feature requirements [:need:`PROCESS_wp__requirements__feat`]
safety_analysis/ -> Safety analysis on feature level [:need:`PROCESS_wp__feature_fmea`, :need:`PROCESS_wp__feature_dfa`, :need:`PROCESS_wp__platform_dfa`]
safety_planning/ -> Feature specific safety workproducts planning
verification/ -> Feature verification report (reporting all feature verifications)
[:need:`PROCESS_wp__verification__platform_ver_report`]
tests/ -> Feature tests, consisting of
integration-tests/ -> Integration tests [:need:`PROCESS_wp__verification__feat_int_test`]
<feature_name>/ -> Features including sub-folders and feature (change) request [:need:`PROCESS_wp__feat_request`]
architecture/ -> Feature architecture [:need:`PROCESS_wp__feature_arch`]
requirements/ -> Feature requirements [:need:`PROCESS_wp__requirements__feat`]
safety_analysis/ -> Safety analysis on feature level [:need:`PROCESS_wp__feature_fmea`], [:need:`PROCESS_wp__feature_dfa`]
safety_planning/ -> Feature specific safety workproducts planning
security_analysis/ -> Security analysis on feature level [:need:`PROCESS_wp__feature_security_analysis`]
verification/ -> Feature verification, consisting of Architecture review [:need:`PROCESS_wp__sw_arch_verification`],
integration_tests/ -> Feature Integration tests [:need:`PROCESS_wp__verification__feat_int_test`]

toolchain/ -> Definition of toolchain
glossary/ -> Glossary of abbreviations used in the platform context
manuals/ -> user and integration manual(s)
overview/ -> Introduction and high-level description
of the platform features.
introduction/ -> Background, scope and high-level architecture of the platform features
manuals/ -> User and integration manual(s)
modules/ -> Modules of the SW platform.
platform_management_plan/ -> Overall Platform Management Plan [:need:`PROCESS_wp__platform_mgmt`]
score_releases/ -> [:need:`PROCESS_wp__platform_sw_release_note`]
safety/ -> safety documentation on platform level (SEooC):
[:need:`PROCESS_wp__feature_dfa`], [:need:`PROCESS_wp__platform_safety_manual`],
quality/ -> Quality documentation on platform level:
[:need:`PROCESS_wp__qms_report`]
requirements/ -> Requirements on platform level
stakeholder/ -> Stakeholder requirements [:need:`PROCESS_wp__requirements__stkh`]
tool/ -> Tool requirements (not covered in tool repositories)
safety/ -> Safety documentation on platform level (SEooC):
[:need:`PROCESS_wp__platform_dfa`], [:need:`PROCESS_wp__platform_safety_manual`],
[:need:`PROCESS_wp__platform_safety_package`], [:need:`PROCESS_wp__fdr_reports`],
[:need:`PROCESS_wp__audit_report`]
security/ -> security documentation on platform level
requirements/ -> requirements on platform level
stakeholder/ -> Stakeholder requirements [:need:`PROCESS_wp__requirements__stkh`]

modules/ -> Modules of the SW platform.
platform_integration_tests/ -> Integration tests on reference hardware verifying stakeholder requirements.

process/ -> process definition including workflows, workproducts,
roles, guidance [:need:`PROCESS_wp__process_definition`]
score_releases/ -> [:need:`PROCESS_wp__platform_sw_release_note`]
score_tools/ -> Tool list and [:need:`PROCESS_wp__tool_verification_report`]
security/ -> Security documentation on platform level:
[:need:`PROCESS_wp__platform_security_manual`], [:need:`PROCESS_wp__platform_security_package`], [:need:`PROCESS_wp__sw_platform_sbom`]
verification_report/ -> Platform verification report (reporting all platform feature's verifications)
[:need:`PROCESS_wp__verification__platform_ver_report`]

registry/ -> infrastructure configuration
platform_integration_tests/ -> Integration tests on reference hardware verifying stakeholder requirements. [:need:`PROCESS_wp__verification__platform_test`]
tools/ -> Platform tools (not covered in tool repositories)

README.md -> Entrypoint of the repository

Expand All @@ -76,36 +75,39 @@ The modules and components shall follow the folder structure which was presented
docs/ -> Documentation of the module
manual/ -> Module manual, e.g. integration manual, assumptions of use,
safety manual [:need:`PROCESS_wp__requirements__comp_aou`],
[:need:`PROCESS_wp__module_safety_manual`].
[:need:`PROCESS_wp__module_safety_manual`],
security_manual [:need:`PROCESS_wp__module_security_manual`].
release/ -> Module release note [:need:`PROCESS_wp__module_sw_release_note`],
safety assessment [:need:`PROCESS_wp__audit_report`]
safety_plan/ -> Module safety plan [:need:`PROCESS_wp__module_safety_plan`],
module safety case [:need:`PROCESS_wp__module_safety_package`],
conformance reviews [:need:`PROCESS_wp__fdr_reports`]
safety_analysis/ -> Safety analysis on module level [:need:`PROCESS_wp__sw_component_dfa`]
verification/ -> Module verification report
safety_mgt/ -> Module safety plan [:need:`PROCESS_wp__module_safety_plan`],
module safety package [:need:`PROCESS_wp__module_safety_package`],
formal documents reviews [:need:`PROCESS_wp__fdr_reports`]
security_mgt/ -> Module security plan [:need:`PROCESS_wp__module_security_plan`],
module securty package [:need:`PROCESS_wp__module_security_package`],
formal documents reviews [:need:`PROCESS_wp__fdr_reports_security`],
module SW bill of material [:need:`PROCESS_wp__sw_module_sbom`]
verification_report/ -> Module verification report
components verifications [:need:`PROCESS_wp__verification__module_ver_report`],
safety analysis conformance reviews [:need:`PROCESS_wp__fdr_reports`]
safety analysis formal reviews [:need:`PROCESS_wp__fdr_reports`]

<component_name>/ -> Components of the module.
Folder containing all artifacts corresponding to one component.

src/ -> Source files of the component consisting of
Include files
Source Files
Detailed Design [:need:`PROCESS_wp__sw_implementation`]
Unit tests [:need:`PROCESS_wp__verification__sw_unit_test`]
<lower_level_comp>/ -> lower level component following <component_name> folder structure

docs/ -> Documentation of the component
architecture/ -> Component architecture (only if lower level components exist)
[:need:`PROCESS_wp__component_arch`].
detailed_design/ -> Detailed Design [:need:`PROCESS_wp__sw_implementation`]
requirements/ -> Component requirements [:need:`PROCESS_wp__requirements__comp`]
safety_analysis/ -> Safety analysis on component level
[:need:`PROCESS_wp__sw_component_fmea`, :need:`PROCESS_wp__sw_component_dfa` ]
verification/ -> Architecture review [:need:`PROCESS_wp__sw_arch_verification`],
code inspection [:need:`PROCESS_wp__sw_implementation_inspection`]
safety_analysis/ -> Safety analysis on component level (only if component architecture exists)
[:need:`PROCESS_wp__sw_component_fmea`], [:need:`PROCESS_wp__sw_component_dfa`]
security_analysis/ -> Security analysis on component level (only if component architecture exists)
[:need:`PROCESS_wp__sw_component_security_analysis`]
verification/ -> Component verification, consisting of Architecture review [:need:`PROCESS_wp__sw_arch_verification`],
code inspection [:need:`PROCESS_wp__sw_implementation_inspection`],
integration_tests/ -> Component integration tests [:need:`PROCESS_wp__verification__comp_int_test`]
<lower_level_comp>/ -> Lower level component following <component_name> folder structure

tests/ -> Feature level tests, consisting of
integration tests [:need:`PROCESS_wp__verification__comp_int_test`]
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载