-
Notifications
You must be signed in to change notification settings - Fork 14
docs: update landing page to recent status #18
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.
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
Conversation
Implements: #17 Signed-off-by: Philipp Ahmann <[email protected]>
Implements: #17 Signed-off-by: Philipp Ahmann <[email protected]>
Implements: #17 Signed-off-by: Philipp Ahmann <[email protected]>
closes: #17 Signed-off-by: Philipp Ahmann <[email protected]>
e2da0cc
to
60fb7dd
Compare
Are we renaming SCORE to S-SCORE? Please note that for all technical elements we will stick with score, as And most notably score and score_xy repos 😆 |
@@ -19,9 +19,9 @@ | |||
# -- Project information ----------------------------------------------------- | |||
# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information | |||
|
|||
project = "SCORE" | |||
project = "S-CORE" | |||
copyright = "2024, Score" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copyright is not updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. I basically had a find and replace for SCORE as match case. On your point with S-CORE vs score. I would stick to score in any form of pathes, tooling and so on. I observed on the other hand that we already have a mixture of S-CORE and SCORE within the score repo. I created an issue #663 in score for exactly that thing.
This PR gets superseded by eclipse-score/score#618 |
The PR will be closed as all findings are implemented in eclipse-score/score#618 |
Modifications are:
Closes: #17