Skip to content

Improvement: correct config mgt start page #110

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
aschemmel-tech merged 1 commit into from
Jul 14, 2025
Merged

Improvement: correct config mgt start page #110

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions process/process_areas/configuration_management/configuration_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,11 @@ Stakeholders
* wants know which work products's version has to be used as input for his work
* wants to share their created work product with others for example to get those reviewed
* wants to integrate their created work product with other work products

Configuration Management Tooling
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Almost all requirements of the standards towards configuration management can be covered by
standard versioning tooling and of tooling for the "Docs-as-Code" approach.

For the automated storage additional tooling is needed see :doc:`guidance/configuration_process_req`)
9 changes: 0 additions & 9 deletions process/process_areas/configuration_management/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,6 @@
Configuration Management
========================

Configuration Management Tooling
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Almost all requirements of the standards towards configuration management can be covered by
standard tooling of the Eclipse Foundation (github for versioning) and of the S-CORE project
(sphinx-needs for text based identification of work products).

For the automated storage additional tooling is created (see :doc:`guidance/configuration_process_req`)

.. toctree::
:maxdepth: 1

Expand Down