eclipse-score / eclipse-score/eclipse-score.github.io

Broken links and outdated information on landing page

Open
#17 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
8
Forks
16
PR merge metrics
No merged PRs in 30d

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](https://github.com/eclipse-score/blob/main/README.md).
- Outdated and wrong link: Please be aware, that this roadmap will be also transfered to the [GitHub project](https://github.com/orgs/eclipse-score/projects/1). 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](https://eclipse-score.github.io/score/score_releases/index.html#releases)
- and a [rigid software development process](https://eclipse-score.github.io/score/process/index.html#process-description) (currently under development).
- All work in SCORE will therefore follow a [Contribution Request Guideline](https://eclipse-score.github.io/score/process/guidance/contribution_request/index.html).
- contributions via the contribution request process described in the [SCORE project handbook](https://eclipse-score.github.io/score/platform_management_plan/project_management.html).

Additionally, some areas call it SCORE and others S-Core.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.