Create ELISA Policies and Guidelines #73
Conversation
As per the discussion at the TSC meeting, adding the policies doc to the repo. Shuah Khan <[email protected]>
|
DCO continues fail on this - not sure why. |
|
|
||
| **ELISA deliverables:** | ||
| - ELISA develops an example qualitative analysis for safety critical use-cases for the Linux kernel e.g: Automotive and Medical. | ||
| - ELISA provides resources for System integrators to apply and use to analyze qualitatively and quantitatively on their systems. For example, ELISA will analyze published CWEs to identify hazards for the two use-cases. |
There was a problem hiding this comment.
@shuahkh I believe this was partially taken from the technical charter and could also be found in a previous version of the gold deck. I propose to do rewording on the ELISA deliverables.
What about creating an issue to update this part of the documentation after we have merged this. Alternative could also be to put another commit on top of this PR to correct it.
| Presentations and work in progress are not considered a publication until reviewed and added to one of the publication sites. All work in progress on github should contain licenses. | ||
|
|
||
| ### Publication Licensing Policy | ||
| All ELISA documentation deliverables shall be released under CC-BY-4.0. All published documents shall carry the following licensing information. |
There was a problem hiding this comment.
I have a concern here. If we say above that blogs count as documentation deliverable it will look strange to have the CC-BY-4.0 listed there. I believe for markdown however, this makes sense. There may be an exception if you have a documentation focused repository which include a LICENSE file.
|
|
||
| References to documents that use this header: | ||
| - https://elisa.tech/wp-content/uploads/sites/75/2021/05/ELISA_Advancing-Open-Source-Safety-Critical-Systems_Whitepaper_050521.pdf | ||
| - https://github.com/elisa-tech/wg-medical-devices/commit/79290c454ab8f4f03560090843f84d13ed7b3360 |
There was a problem hiding this comment.
If I follow the link to medical I get a headline from github mentioning: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." I guess we may have to change it to: elisa-tech/wg-medical-devices@e7eefff
|
|
||
| If contributions are added to an existing tool, they are considered to be under the license associated with the existing project. | ||
|
|
||
| ELISA uses tools and references to develop example qualitative analysis for Automotive and Medical use-cases for the Linux kernel and provides resources for System integrators to use to analyze their systems. |
There was a problem hiding this comment.
Change proposal: "analysis for Automotive and Medical use-cases" could become "analysis for ELISA reference use-cases"
| - Each repository must have a documented review policy and acceptance criteria for PRs, to provide guidance to contributors, maintainers and reviewers. | ||
| - All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license. | ||
|
|
||
| ### Investigation on safety standards use in reference process |
There was a problem hiding this comment.
Is this section the proper place for the document. We also kind of completed the reference process work, IIRC. Keeping it in is also not harming the content, so it may be an item for further discussion in a later stage.
|
@shuahkh I am not sure, if you tried this already, but there is section within the wg-automotive describing the DCO issue. But I am pretty sure you have most likely followed this, if I remember the discussion from March correctly and @reiterative was also pointing you to it. I also added a few comments, which could result in an update of this PR. Maybe this on top resolves the failing DCO check. |
As per the discussion at the TSC meeting, adding the policies doc to the repo.
Signed-off-by: Shuah Khan [email protected]