Cleanup process_group_manager directory

Open Beginner friendly
#375 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
cpp
Domain
operating-systems

Research direction

Review PR #370 and inspect score/launch_manager/src/daemon/src/component_manager, especially details/process, icomponent.hpp, and run_target.hpp. Separate component-specific files from process-specific files so the directory structure matches the abstraction layers, then verify all component-specific code is distinct from process-specific code.

Written by the indexing model from the issue text.

Description

cleanup
What

After PR https://github.com/eclipse-score/lifecycle/pull/370 we should organize the directories as the directory names don't respect the abstraction layers.

score/launch_manager/src/daemon/src/component_manager
├── details
│   └── process    // Each implementation of a component has a separate sub folder
│       ├── process.hpp
│       └── process_monitor.hpp
├── icomponent.hpp  // All files need to be on the component level
└── run_target.hpp
Acceptance Criteria (DoD)
  • All component specific code is in a different directory to all process specific code.
How

No response

Dominant language
C++
Stars
6
Forks
34
Avg merge
1d 23h
Merged PRs (30d)
83

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/lifecycle

All issues in eclipse-score/lifecycle

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.