+
Skip to content

Conversation

wmader23
Copy link
Contributor

@wmader23 wmader23 commented Apr 8, 2025

This pull request introduces Stakeholder Requirements for a proposed way how to document and governs APIs in S-CORE. In addition a process is described implementing the requirements.

Ref: closes #876

Copy link

github-actions bot commented Apr 8, 2025

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ✅ Passed

Click to expand output
[License Check Output]
2025/04/10 14:09:11 Downloading https://releases.bazel.build/7.4.0/release/bazel-7.4.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (67 packages loaded, 10 targets configured)

Analyzing: target //:license-check (90 packages loaded, 10 targets configured)

Analyzing: target //:license-check (96 packages loaded, 10 targets configured)

Analyzing: target //:license-check (99 packages loaded, 10 targets configured)

Analyzing: target //:license-check (131 packages loaded, 1329 targets configured)

Analyzing: target //:license-check (133 packages loaded, 1617 targets configured)

Analyzing: target //:license-check (145 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (145 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (146 packages loaded, 2588 targets configured)

Analyzing: target //:license-check (149 packages loaded, 4611 targets configured)

INFO: Analyzed target //:license-check (150 packages loaded, 4737 targets configured).
[11 / 13] [Prepa] JavaToolchainCompileBootClasspath external/rules_java~/toolchains/platformclasspath.jar
[12 / 13] Building license.check.license_check.jar (); 0s multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 23.237s, Critical Path: 2.50s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt -review -project automotive.score -repo https://github.com/eclipse-score/score -token otyhZ4eaRYK1tKLNNF-Y
[main] INFO Querying Eclipse Foundation for license data for 76 items.
[main] INFO Found 52 items.
[main] INFO Querying ClearlyDefined for license data for 24 items.
[main] INFO Found 24 items.
[main] INFO Vetted license information was found for all content. No further investigation is required.

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.

Please check here for contributing new features,
https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html

Adding stakeholder requirements requires Feature Request, Issue First, process areas have intention to be tool independent, these contributions are either part of our PMP
https://eclipse-score.github.io/score/main/platform_management_plan/software_development.html

, or contributions
https://eclipse-score.github.io/score/main/contribute/development/index.html

@wmader23 wmader23 marked this pull request as draft April 9, 2025 12:47
@wmader23 wmader23 force-pushed the api_management_feature_request branch from 48ff17e to d135fce Compare April 10, 2025 14:08
Copy link

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

@wmader23
Copy link
Contributor Author

wmader23 commented Apr 10, 2025

In response to #874 (review) I

  • created and linked an issue which follows the template for a Feature Modification Request
  • reduced the PR to only contain tooling-agnostic stakeholder requirements.

In case the requirements are accepted, I will provide the process documentation, further requirements, etc. in a separate PR.

@wmader23 wmader23 changed the title Api management process description and stakeholder requirements Api management stakeholder requirements Apr 10, 2025
Copy link

This PR is stale because it has been open for 30 days with no activity. It will be closed in 10 days if no further activity occurs. #magic___^_^___line

@nicu1989 nicu1989 closed this Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Establish API documentation and live-cycle management: Additions to Stakeholder Requirements

8 participants

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载