-
Notifications
You must be signed in to change notification settings - Fork 0
halnasri-Resolve_TT_CONFIDENCE_Feedback #132
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?
Changes from all commits
e0c2f91
571e525
f23dbc7
427a6ab
dcc7e50
b9cfa22
a6da396
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,10 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: web_content | ||
| url: "https://eclipse-score.github.io/inc_nlohmann_json/main/generated/dashboard.html#summary" | ||
| description: "Dashboard showing distributions of evidence scores and SME (subject-matter expert) scores." | ||
| --- | ||
|
|
||
| Each statement is scored based on SME reviews or automatic validation functions. (TODO) | ||
| Each leaf node in the Trustable Graph is scored either based on an SME review alone or on a combination of an SME review and an automatic validation function. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,10 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: web_content | ||
| url: "https://score-json.github.io/json/main/concept.html#scoring" | ||
| description: "Description of the algorithm how scores are accumulated, reviewed." | ||
| --- | ||
|
|
||
| Scores are reasonably, systematically and repeatably accumulated. (TODO) | ||
| Scores are reasonably, systematically and repeatably accumulated. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,12 +2,29 @@ | |
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: project_website | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you explain why these are 3 different types of references here? especially the first and third link look really similar to me |
||
| url: "https://github.com/nlohmann/json/blob/develop/.github/CODEOWNERS" | ||
| description: "CODEOWNERS file specifying that changes to any file requests @nlohmann for code review in case of a pull request" | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json?tab=contributing-ov-file#readme" | ||
| description: "nlohmann/json contribution guidelines" | ||
| - type: website | ||
| url: https://eclipse-score.github.io/process_description/main/general_concepts/score_review_concept.html | ||
| description: "Documentation of S-CORE methodologies" | ||
| url: "https://github.com/nlohmann/json/actions?query=event%3Apush+branch%3Amaster" | ||
| description: "GitHub reviews of nlohmann/json filtered for push to master" | ||
| - type: verbose_file | ||
| path: "/workspaces/json/ChangeLog.md" | ||
| description: "A mirror of the Changelog of nlohmann/json's Changelog" | ||
| evidence: | ||
| type: https_response_time | ||
| configuration: | ||
| target_seconds: 2 | ||
| urls: | ||
| - "https://github.com/nlohmann/json/actions?query=event%3Apush+branch%3Amaster" | ||
| - "https://github.com/nlohmann/json?tab=contributing-ov-file#readme" | ||
| - "https://github.com/nlohmann/json/blob/develop/.github/CODEOWNERS" | ||
| score: | ||
| Jonas-Kirchhoff: 1.0 | ||
| Erikhu1: 1.0 | ||
| --- | ||
|
|
||
| The S-Core methodologies are followed. | ||
| All contributions to the nlohmann/json repository are reviewed according to the project’s documented contribution and review process. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This sounds similar to JLS-06 and JLS-25. I think we need to understand TA-METHODOLOGIES better |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: verbose_file | ||
| path: "/workspaces/json/TSF/README.md" | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please use relative path instead (i.e., without the "workspaces/json") |
||
| description: "release management and update process description" | ||
| --- | ||
|
|
||
| Releases and updates of the score-json repository are carried out in accordance with defined and documented release and update process. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: web_content | ||
| url: "https://score-json.github.io/json/main/generated/trustable_report_for_Software.html#compliance-for-ta" | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please always use the report of the inc_nlohmann_json repo |
||
| description: "Trustable Compliance Report showing scores for different TA items." | ||
| --- | ||
|
|
||
| The confidence in the nlohmann/json library also incorporates confidence scores derived from other TA items. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I dont really understand this statement or the idea behind it. Can you explain?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I understand that you are trying to target this However, I think the combination of JLS-08 and JLS-09 are already indirectly stating the same thing as this. Instead, I would reformulate it to something like |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json/blob/develop/.github/CONTRIBUTING.md" | ||
| description: "nlohmann/json contribution guidelines describing analysis, testing, and review expectations" | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json/tree/develop/.github" | ||
| description: "Project workflows and configuration supporting automated analysis and testing for nlohmann/json" | ||
| - type: file | ||
| path: "TSF/scripts/generate_list_of_misbehaviours.py" | ||
| description: "Script generating a report of known misbehaviours of the nlohmann/json library based on GitHub issues" | ||
| - type: verbose_file | ||
| path: "TSF/README.md" | ||
| description: "TSF-related description of analysis, verification processes, and update concepts for score-json" | ||
| evidence: | ||
| type: https_response_time | ||
| configuration: | ||
| target_seconds: 2 | ||
| urls: | ||
| - "https://github.com/nlohmann/json/blob/develop/.github/CODE_OF_CONDUCT.md" | ||
| - "https://github.com/nlohmann/json/tree/develop/.github" | ||
| --- | ||
|
|
||
| Manual verification activities that complement automated analysis for the nlohmann/json library are documented, reviewed against defined criteria, and considered for their impact on identifying and addressing misbehaviours. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What exactly is a "misbehavior"?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Misbehaviour is an established term in TSF (defined as 'any behaviour of the software that deviates from the defined expectations'). However, I think this statement is still on a too high level. It needs to be more explicit (or broken down into further supporting statements). What are the manual activities? what are the defined criteria?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For example: Then reference to e.g., this https://github.com/nlohmann/json/security/advisories/new
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe even better examples: "The manual activity of issuing a vulnerability or bug report for the nlohmann/json library is a well-defined process." "All manual pull requests to the nlohmann/json repository are expected to describe the rationale behind any non-trivial changes, and link to an existing issue"
"Feature requests for the nlohmann/json library are actively investigated by Niels Lohmann"
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| --- | ||
| level: 1.1 | ||
| normative: true | ||
| references: | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json/blob/develop/.github/CODEOWNERS" | ||
| description: "Definition of responsible owners and reviewers for the nlohmann/json repository" | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json/blob/develop/.github/CONTRIBUTING.md" | ||
| description: "nlohmann/json contribution guidelines describing contribution, testing, and review expectations" | ||
| - type: project_website | ||
| url: "https://github.com/nlohmann/json/blob/develop/.github/CODE_OF_CONDUCT.md" | ||
| description: "Code of Conduct defining behavioural expectations during collaboration and review" | ||
| - type: verbose_file | ||
| path: "TSF/README.md" | ||
| description: "TSF documentation describing responsibilities, verification processes, and change control for score-json" | ||
| evidence: | ||
| type: https_response_time | ||
| configuration: | ||
| target_seconds: 2 | ||
| urls: | ||
| - "https://github.com/nlohmann/json/blob/develop/.github/CODE_OF_CONDUCT.md" | ||
| - "https://github.com/nlohmann/json/blob/develop/.github/CONTRIBUTING.md" | ||
| - "https://github.com/nlohmann/json/blob/develop/.github/CODEOWNERS" | ||
| --- | ||
|
|
||
| Responsibilities for manual verification and review follow documented, competence-based processes and guidelines, and the associated processes and checks are regularly reviewed and updated under defined change control. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here we need the information to which repos/libraries this statement should apply. In the references you name score-json and nlohmann/json - is the statement meant for both?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Again, also needs to be more explicit or broken down into smaller statements. What are the "responsibilities" and "competence based processes and guidelines"? |
||

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.
what exactly is reviewed here? is the description reviewed or how scores are accumulated?
Uh oh!
There was an error while loading. Please reload this page.
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.
The description here is just copied from Mr. Schemmel's PR. I guess it is referring to the fact that we updated the concept section of the report.
We should remove the "reviewed" and just have "Description of the algorithm on how scores are calculated and accumulated"