-
Notifications
You must be signed in to change notification settings - Fork 74
docs: Adding requirements and a component change request for vajson #2358
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
base: main
Are you sure you want to change the base?
docs: Adding requirements and a component change request for vajson #2358
Conversation
Adapting json architecture doc to include vajson as a new backend and adding component requirements.
Dummy commit to report author details.
Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
|
Feature/Component request does not follow Process, needs to use https://github.com/eclipse-score/score/blob/main/.github/ISSUE_TEMPLATE/3-change.yml Compare also https://eclipse-score.github.io/score/main/contribute/contribution_request/index.html |
FScholPer
left a comment
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.
Needs agreement in architecture community. Do we have something like that for vajson?
Fix Sphinx RST build issues. Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
Fix requirement linking. Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
Issue 2310 - Component request: (JSON parsing) VaJson in S-CORE Fix indenting. Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com> Signed-off-by: Linnea Bennerhed <72805813+linnealinnea@users.noreply.github.com>
|
The created documentation from the pull request is available at: docu-html |
|
@FScholPer The component was accepted in the baselib FT MeetingNotes, and my understanding is that @4og will bring this up on next architecture community meeting after Christmas. |
|
@linnealinnea thank you for your PR and great to hear that it is already aligned in the Feature Team. Let's, however, get the buy-in from the Architecture Community also. We have to make sure that we uphold our principle "one solution only for any given aspect", which is watched over by the Architecture Community. |
Adding first version of "Change Management Component Request"
Fix failing doc build
|
Keeping the PR in draft mode until next Architecture Community round |
| # SPDX-License-Identifier: Apache-2.0 | ||
| # ******************************************************************************* | ||
|
|
||
| .. _component_template: |
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.
you can remove that or replace by reference you need for your specific component
| :safety: ASIL_B | ||
| :security: NO | ||
| :realizes: wp__cmpt_request | ||
| :tags: contribution_request, feature_request |
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.
it seems a component_request, not new feature?
Adapting json architecture doc to include vajson as a new json backend and adding component requirements. Related to #2310.