Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@antonkri
Copy link
Contributor

@antonkri antonkri commented Oct 23, 2025

@github-actions
Copy link

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@masc2023 masc2023 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only comments, as author labeled it with needs-rework

# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
How-Tos
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this not called Handbook directly?

@@ -0,0 +1,16 @@

S-Core Book
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in general we use in other documentation S-CORE (Big letters), the comment applies to the whole document

==========================

As it was already stated in the "Overview of the technologies" part, S-Core project consists of multiple
bazel modules, normally located in separate repositories. Majority of S-Core modules are part of S-Core
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bazel-Modules, according to our model Modules realized as Bazel-Modules


S-Core module is the central part of the s-core project, where the software architecture is defined. Here you will find the list and explanation of the features,
that are provided by the S-Core platform, definition of the high level architecture, break down of the high level architecture to the modules
and the definition of the functionality (logical interfaces) for every module.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You miss here PMP, which defines the deployment of the Process Definition in process_description, Tool Lists, Design Decisions, and Requirements

We automatically generate for every repository html documentation from rst files.
You can easily open it as shown at the picture (TODO: Link)

The process repository defines the S-Core process. It defines both general concepts and ideas of the S-Core software development process approach and
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It defines Processes compliant to standards, a kind of Framework, Management System, independent from any tools. The PMP in the s-core repo documents, how they are deployed in S-CORE.
That's why it can also used for other projects outside S-CORE.

@antonkri antonkri force-pushed the ankr_score_book branch 7 times, most recently from 2018000 to 68b232e Compare October 30, 2025 14:25
@antonkri antonkri force-pushed the ankr_score_book branch 2 times, most recently from 6746b36 to dd73027 Compare October 30, 2025 14:53
@@ -0,0 +1,181 @@
<root> ([email protected])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants