This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
openchain:spec-2016-h1-public-comments [2016/10/04 22:05] mgisi [19) Suggest: Reconsider the definition of Supplied Software] |
openchain:spec-2016-h1-public-comments [2016/10/05 00:03] (current) mgisi |
||
|---|---|---|---|
| Line 253: | Line 253: | ||
| This could be a subsection of "Review and Approve FOSS Content" or an own main section ("Knowing License Conditions"). | This could be a subsection of "Review and Approve FOSS Content" or an own main section ("Knowing License Conditions"). | ||
| + | |||
| + | ---- | ||
| + | |||
| + | === Response: === | ||
| + | Although the first version of the specification has been finalized (August 2016), your feedback is still timely in that we are embarking on the next revision round in September. I added your comments to the issues list for consideration. | ||
| + | |||
| + | ==== *22) Suggest: Defining a Remediation Path ==== | ||
| + | Submitted By: Mark Gisi | ||
| + | |||
| + | Currently no requirement to ensure an organization has a remediation and/or escalation path. | ||
| ---- | ---- | ||