Logging CFT Weekly [2026-09-01] #3238
arsibo
started this conversation in
Logging FT
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Participants
Agenda & Meeting Minutes
- https://github.com/eclipse-score/score/milestones
- https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/pi2.html
@arsibo : convert into backlog task
Code coverage
add the tracing feature to logging ?? => check with @hoppe-and-dreams + decision
- Change the feature name from logging to log_and_trace
- add tracing requirement
- architecture API/component
- NOTE: https://eclipse-score.github.io/.github/#naming
- 01.09.2026: add tracing is fine. the needed adaptions shall be planed by an epic.
- 8.09.2026 : component naming discussion
feature requirements (TODO)
v0.10
04.08.2026: move content of log_rust to /score/mw/log/rust + adoptions due to process baselibs#390
@arsibo check with the process community about the usage of mw folder . mw has also a meaning of a stateful component (Markus Bechter / Andrej knows about that) => https://eclipse-score.github.io/score/main/contribute/general/folder.html will be updated . MW is used if it isn't only lib . It is used for runtimes. @rmaddikery please send out a PR to change https://eclipse-score.github.io/score/main/contribute/general/folder.html @anmittag has the latest info. regarding this and apprently its decided that "mw" can be used and the module structure will be updated (issue link to be added here)
11.08.2026: Will be discussed in the process mention on 13.08.2026
follow up
Info
All reactions