Skip to content

fix: broken links #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 19, 2025
Merged

fix: broken links #29

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ba5f777
fix: broken links
opajonk Jun 19, 2025
31fe074
fix: technical glitch, wrong UTF-8 character
opajonk Jun 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/get_involved.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ https://github.com/eclipse-score/score/blob/main/CONTRIBUTION.md
How to get involved into SCORE
------------------------------

The :underline:`only` way to influence SCORE is TO CONTRIBUTE. Everybody can contribute – SCORE is open.
The :underline:`only` way to influence SCORE is TO CONTRIBUTE. Everybody can contribute - SCORE is open.

Active Contributions to the SCORE project are the basis for getting involved. The SCORE Project works according to
the Eclipse Project Handbook and has named and elected project leads and committers (see https://projects.eclipse.org/projects/automotive.score/who).
Expand All @@ -51,13 +51,13 @@ lead circle. Meeting notes are transparent via the SCORE github organization. (s

We aim to build a safety ready full stack architecture, where components fit to each other in
automotive grade Software Quality and performance. To achieve this, 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>`_
`feature roadmap and architecture <https://eclipse-score.github.io/score/main/score_releases/index.html#roadmap>`_
and a `rigid software development process <https://eclipse-score.github.io/process_description/main/index.html>`_
(currently under development).

Contributions to the SCORE project must therefore follow the technical direction of the project and the SCORE
architecture. All work in SCORE will therefore follow a
`Contribution Request Guideline <https://eclipse-score.github.io/score/process/guidance/contribution_request/index.html>`_.
`Contribution Request Guideline <https://eclipse-score.github.io/score/main/contribute/index.html>`_.
Features on the roadmap of SCORE are defined, Contribution Requests create the basis for individual contributions from
within the SCORE project and also from the outside.

Expand All @@ -79,4 +79,4 @@ We value real code based collaboration and will judge new potential contributors
Active and sustaining contributions are the basis for the ability to shape SCORE.

Making active code contributions via the contribution request process described in the
`SCORE project handbook <https://eclipse-score.github.io/score/platform_management_plan/project_management.html>`_.
`SCORE project handbook <https://eclipse-score.github.io/score/main/platform_management_plan/project_management.html>`_.