Broken links and outdated information on landing page
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content, documentation
Research direction
Locate the landing page source containing the listed links and review each target, the December 2024 wording, and the SCORE/S-Core naming. Update the link destinations and outdated text, then verify that every referenced page resolves and the project name is consistent throughout the landing page.
Written by the indexing model from the issue text.
Description
On the landing page there are some links which are broken or point to wrong location.
- Page not existing: To start working with bazel in the SCORE project, you should check this introduction page.
- Outdated and wrong link: Please be aware, that this roadmap will be also transfered to the GitHub project. Please follow this link to get the latest state of the planning.
- Outdated: We plan to start regular exchange in the scope of the SCORE project in December 2024.
- Broken links:
- we follow a strict feature roadmap and architecture
- and a rigid software development process (currently under development).
- All work in SCORE will therefore follow a Contribution Request Guideline.
- contributions via the contribution request process described in the SCORE project handbook.
Additionally, some areas call it SCORE and others S-Core.
- Dominant language
- Python
- Stars
- 8
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/eclipse-score.github.io
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
align gitlint configOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in eclipse-score/eclipse-score.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FuRongJun-1999/dsh-memory#56 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pgadmin-org/pgadmin4#10503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#3857 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
rai-opensource/spatialmath-python#235 ·
Maintainers usually reply within 1 day
-
needs-ac
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Ikalus1988/MisakaNet#2845 ·
Maintainers usually reply within 1 day