Missing scheduling concept
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 61/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reading the lifecycle inspection guidance around scheduling policies and priorities. Clarify where this point should be addressed in the lifecycle and update the relevant guidance; done means the documentation explains how to handle the inspection item. The issue does not name a file or test, so locating the relevant entry will take some reading around.
Written by the indexing model from the issue text.
Description
What
Missing strategy for scheduling on platform level fails the inspection item
If your software architectural design includes processes and tasks, are their scheduling policies and priorities (or at least the necessary relationships among them) defined to ensure that timing requirements are met? Please note that the specific priorities or priority ranges will probably be defined in the project handbook or the software development plan.
Acceptance Criteria (DoD)
Clarified how to address this point in lifecycle
How
No response
- Dominant language
- C++
- Stars
- 7
- Forks
- 37
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 117
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-score/lifecycle
-
Make integration tests have debug assertsPossibly taken @hskang-amelia claimed this 10 days ago. Opentests
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
eclipse-score/lifecycle#843 ·
Maintainers usually reply within 1 day
-
Move all "Default" asserts to debugPossibly taken @hskang-amelia claimed this 10 days ago. Opencleanup good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
eclipse-score/lifecycle#842 ·
Maintainers usually reply within 1 day
-
cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eclipse-score/lifecycle#375 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
eclipse-score/lifecycle#952 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-score/lifecycle#951 ·
Maintainers usually reply within 1 day
All issues in eclipse-score/lifecycle
Similar issues
-
Linux npm packaging leaves workspace files that block subsequent CI checkoutPossibly taken @Spockkk0225 claimed this today. Openci
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
alibaba/neug#1195 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SCIInstitute/SCIRun#2909 ·
Maintainers usually reply within 2 days
-
area: packaging blocked dependencies P3: low post-stable value: medium
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
patrick-hudson/put.gd-desktop#1210 ·
Maintainers usually reply within 1 day