-
Notifications
You must be signed in to change notification settings - Fork 61
Api management stakeholder requirements #874
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
Api management stakeholder requirements #874
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-check Status: ✅ Passed Click to expand output
|
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.
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
48ff17e
to
d135fce
Compare
The created documentation from the pull request is available at: docu-html |
In response to #874 (review) I
In case the requirements are accepted, I will provide the process documentation, further requirements, etc. in a separate PR. |
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 |
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