Skip to content

Fix top-level documentation - #259

Open
rmaddikery wants to merge 5 commits into
mainfrom
rama_fix_docu
Open

Fix top-level documentation#259
rmaddikery wants to merge 5 commits into
mainfrom
rama_fix_docu

Conversation

@rmaddikery

@rmaddikery rmaddikery commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

See rendered documentation here:
#259 (comment)

Fix top-level documentation

  • Adds high-level overview explaining the mw::log structure
  • Remove outdated documentation
  • Restructure documentation to where it fits

@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: c1eaed4e-326d-4326-870d-648b80964f38
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'score_process', the root module requires module version score_process@1.5.4, but got score_process@1.6.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
Analyzing: 0 targets (5 packages loaded)
INFO: Elapsed time: 12.941s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@github-actions

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@rmaddikery
rmaddikery marked this pull request as draft August 12, 2026 18:00
@rmaddikery
rmaddikery deployed to workflow-approval August 12, 2026 18:27 — with GitHub Actions Active
@rmaddikery
rmaddikery deployed to workflow-approval August 12, 2026 19:09 — with GitHub Actions Active
@rmaddikery
rmaddikery deployed to workflow-approval August 13, 2026 07:16 — with GitHub Actions Active
@rmaddikery
rmaddikery deployed to workflow-approval August 13, 2026 10:15 — with GitHub Actions Active
@rmaddikery rmaddikery moved this from Backlog to In Progress in LOG - Logging FT Aug 13, 2026
@rmaddikery
rmaddikery deployed to workflow-approval August 13, 2026 10:27 — with GitHub Actions Active
@rmaddikery
rmaddikery marked this pull request as ready for review August 13, 2026 10:50
@rmaddikery
rmaddikery deployed to workflow-approval August 13, 2026 10:55 — with GitHub Actions Active
@rmaddikery
rmaddikery deployed to workflow-approval August 14, 2026 06:55 — with GitHub Actions Active

@arsibo arsibo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

first formal findings

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

A component's architecture describes how it is constructed from subcomponents. Since this component contains no subcomponents, this content should be moved to the detailed design section.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

file_output_backend and datarouter_backend are not shown in this diagram

=====================

.. comp:: Logging Component
:id: comp__mw_logging

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should mw_looging be the final component name? I thought we wanted to use log_backend in the logging repo and 'log' in the baselibs repo.

@rmaddikery rmaddikery Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No. baselibs will have one dependable_element in which mw::log will be part of.
So we keep mw_log in score_logging and create a safety plan here.
in baselibs a sefetyplan will forward aous and link the score_logging safety plan

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

That means we will have three components in the logging feature

  1. log in baselibs
  2. mw_log in logging
  3. datarouter in logging

right ? In the safety artifacts we working with references . That means the safety artifact for log (baseline) includes only an reference to mw_log (logging)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

file shall be moved to ./mw_log/requirements/
See folder structure under <component_name>/ https://eclipse-score.github.io/score/main/contribute/general/folder.html

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Shall we add a folder _assets for that ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Comment thread docs/guides/index.rst Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

content shall be moved to docs/manuals/

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Comment thread docs/components/datarouter/index.rst Outdated

.. comp:: Data Router
.. comp:: Datarouter
:id: comp__data_router

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

component id shall be 🆔 comp__datarouter due to folder name datarouter

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Comment thread docs/components/mw_log/index.rst Outdated
Runtime plugin loading remains experimental and is not a supported
production capability.

.. uml:: mw_log_repository_boundary.puml

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this belongs to the feature architecture . Feature architecture has to be modeled in sphinx needs

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

written is less then requested.

![Action Diagram](./score/mw/log/design/slot_drainer_action_diagram_design.puml)
<img alt="SlotDrainerActionDiagram" src="https://www.plantuml.com/plantuml/proxy?src=https://raw.githubusercontent.com/eclipse-score/baselibs/refs/heads/main/score/mw/log/design/slot_drainer_action_diagram_design.puml">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

puml file was not rendered

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

will be fixed after fixed in baselibs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The file shall be included as reference to detailed design or there should be folder on the rendered website design decisions

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

fixed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

file_output_backend and datarouter_backend are not shown in this diagram

### Process structure

[context-highlevel](uml/context-highlevel.puml)
<img alt="CONTEXT_HIGHLEVEL" src="https://www.plantuml.com/plantuml/proxy?src=https://raw.githubusercontent.com/eclipse-score/logging/refs/heads/main/score/datarouter/doc/design/uml/context-highlevel.puml">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Diagramm shows an Adptive Autosar ECU

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

fixed

@@ -50,9 +50,9 @@ The following constraints influenced the logging infrastructure design:
## Context

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

chapter could be copied/moved to feature description

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done

Comment thread README.md Outdated
| `project_config.bzl` | Project-specific metadata for Bazel macros |
| `LICENSE.md` | Licensing information |
| `CONTRIBUTION.md` | Contribution guidelines |
## 📂 Key Files

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would remove that, usless

Comment thread README.md Outdated

---

## ⚙️ `project_config.bzl`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

would remove all that below for project_config.bzl

Comment thread README.md Outdated
@@ -35,84 +30,55 @@ It provides a **standardized project structure**, ensuring best practices for:
### 1️⃣ Clone the Repository

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

not needed

- Adds high-level overview of the mw::log decomposition
- Remove outdated documentation
- Restructure documentation to where it fits
- Replace duplicated content with redirection to
single source that resides next to source code rendered
by Sphinx
- Reflect score folder structure guideline
- Adds high level architecture documentation
and references related diagrams
:safety: ASIL_B
:safety: QM
:status: valid
:implements: logic_arc_int__logging__logging

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

comp__datarouter don't implement logic_arc_int__logging__logging.
This interface is implemented by mw_log.

  • Feature logging defines logic_arc_int__logging__buffer
  • mw_log implements logic_arc_int__logging__buffer
  • datarouter uses logic_arc_int__logging__buffer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants