github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-08-26 11:39:29 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #92 from jodh-intel/fix-markdown

Browse Source 
Fix markdown
This commit is contained in:
Xu Wang 2019-05-01 14:13:10 -06:00 committed by GitHub
commit 02c9e8b3b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -22,7 +22,7 @@
* [Main patch](#main-patch)
* [Supplementary patch](#supplementary-patch)
* [Reviews](#reviews)
* [Examples](#examples)
* [Review Examples](#review-examples)
* [Continuous Integration](#continuous-integration)
* [Contact](#contact)
* [Project maintainers](#project-maintainers)
@ -779,7 +779,7 @@ in the acknowledgement counting system.
Documentation PRs can sometimes use a modified process explained in the
[Documentation Review Process](Documentation-Review-Process.md) guide.
### Examples
### Review Examples
The following is an example of a valid "ack", as long as
the 'Approve' box is ticked in the Review changes dialog:

6
VMT/VMT.md
View File

@ -53,7 +53,7 @@ If no KCSA is warranted and there is no benefit to a KCSN then the KCSA Issue wi
If a Kata Containers Security Note ([KCSN](templates/KCSN.md)) is warranted, one should be written and posted to the [Kata Containers Security Note](https://github.com/kata-containers/documentation/security/KCSN.md) document.
The specifics are indexed in the [report taxonomy](#incident-report-taxonomy) and [task status](#KCSA-task-status) tables.
The specifics are indexed in the [report taxonomy](#incident-report-taxonomy) and [task status](#kcsa-task-status) tables.
## Patch development
@ -127,12 +127,12 @@ On the disclosure hour, open bug, push patches to GitHub PR for review on master
Embargo reminder can be removed at that point.
[MITRE's CVE Request form](https://cveform.mitre.org/) should be used again at this point, but instead select a *request type* of `Notify CVE about a publication` and fill in the coordinator's *e-mail address*, provide a *link to the advisory* (Use the links from the [Kata Containers Security Advisories page](https://github.com/kata-containers/documentation/security/KCSA.md) if this is a formal KCSA), the *CVE IDs* covered, and the *date published*.
[MITRE's CVE Request form](https://cveform.mitre.org/) should be used again at this point, but instead select a *request type* of `Notify CVE about a publication` and fill in the coordinator's *e-mail address*, provide a *link to the advisory* (Use the links from the [Kata Containers Security Advisories page](KCSA.md) if this is a formal KCSA), the *CVE IDs* covered, and the *date published*.
Once more, fill in the *security code* at the bottom of the page and *submit request*.
## Publish KCSA
Shortly after pushing the patches (potentially waiting for the first test runs to complete), publish the advisory to the [Kata Containers Dev ML](mailto:kata-dev@lists.katacontainers.io) and slack channels, and add the issue to the [list of KCSA's](//github.com/kata-containers/documentation/security/KCSA.md).
Shortly after pushing the patches (potentially waiting for the first test runs to complete), publish the advisory to the [Kata Containers Dev ML](mailto:kata-dev@lists.katacontainers.io) and slack channels, and add the issue to the [list of KCSA's](KCSA.md).
Wait until all patches are merged to supported branches before setting the KCSA Issue status to *Fix released*.
## All patches merged