add documentation examples#58
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
| Placeholder for the description that will be generated from doxygen |
There was a problem hiding this comment.
We aren't using doxygen, is this a typo / old copy paste error?
There was a problem hiding this comment.
The description itself is directly moved from process description. Maybe the process description was wrong.
There was a problem hiding this comment.
Lets discuss this outside this PR.
| | `score/` | Source files and Unit Tests for the module | | ||
| | `tests/` | Component and Feature Integration Tests (CIT&FIT) | | ||
| | `examples/` | Example files used for guidance | | ||
| | `docs/` | Documentation (Doxygen for C++ / mdBook for Rust) | |
There was a problem hiding this comment.
As far as I know doxygen is not used currently.
OR am I on old information?
There was a problem hiding this comment.
This is unchanged (was there also before PR). We have to check that.
There was a problem hiding this comment.
Implementation process is not finalised yet, that was planned for implementation, detailed design
|
After discussion with Roland and the discussion in the process meeting (02.04.2026) In case that the new DR can not be decided in the next two weeks, we need a workaround step for that PR. |
|
The folder structure already documented in https://eclipse-score.github.io/score/main/contribute/general/folder.html#module-folder-structure does not have the problem as I understand (the entry point for sphinx would be <module_name> folder). Why not use this? But I understand that we would not like to have a path which is like https://github.com/eclipse-score/<repository_name>/<module_name> because these may be the same, but please consider that we defined "This Delivery Container can contain one or more Dependable Elements" in https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html so a reposity could contain more than one module. |
aschemmel-tech
left a comment
There was a problem hiding this comment.
comments resolved apart from minor stuff
Move the documentation examples from process documentation to module template.
See belonging PR eclipse-score/process_description#632 in process.