openchain:spec-2016-h1-public-comments
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
openchain:spec-2016-h1-public-comments [2016/07/18 17:33] mgisi [17) Suggest: 3.1 and 3.2 sub-section consolidation] |
openchain:spec-2016-h1-public-comments [2016/09/19 23:48] mgisi [21) Suggest: Adding - identify the license conditions of the applicable licenses] |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| ---- | ---- | ||
| - | ==== 3) Suggested removing historical view from Introduction ==== | + | ==== *3) Suggested removing historical view from Introduction ==== |
| Submitted By: Martin Yagi | Submitted By: Martin Yagi | ||
| Line 74: | Line 74: | ||
| ---- | ---- | ||
| - | ==== 7) Request to Add text stating value of compliance in generally has value ==== | + | ==== *7) Request to Add text stating value of compliance in generally has value ==== |
| Submitted By: Karen Sandler | Submitted By: Karen Sandler | ||
| Line 117: | Line 117: | ||
| - | ==== 11) Suggest including: "scripts used to control compilation and installation" ==== | + | ==== *11) Suggest including: "scripts used to control compilation and installation" ==== |
| Submitted By: Karen Sandler | Submitted By: Karen Sandler | ||
| Line 211: | Line 211: | ||
| ---- | ---- | ||
| - | ==== 18) Suggest: 3.1 and 3.2 sub-section consolidation ==== | + | ==== *18) G5 - Should cover code that the organization provides as open source ==== |
| Submitted By: Jilayne Lovejoy | Submitted By: Jilayne Lovejoy | ||
| Line 218: | Line 218: | ||
| === Response: === | === Response: === | ||
| - | TBD | + | It was recognized that the section G5 was the section that will likely go through the most evolution in the next few up coming releases (versions) of the specification. Instead of trying to make significant changes to G5 in this final stage of the first release we decided to add this item to the issues consideration queue for the next version of the spec. |
| ---- | ---- | ||
| Line 229: | Line 229: | ||
| === Response: === | === Response: === | ||
| - | TBD | + | The Supplied Software definition was discussed. It was decided to keep the definition as is (more genera). |
| ---- | ---- | ||
| Line 239: | Line 239: | ||
| === Response: === | === Response: === | ||
| - | TBD | + | The consideration noted here was discussed with the conclusion that it should be addressed by the OpenChain curriculum team and not in he spec. The spec focuses on the "what and why" where this issue was viewed as a "how and when" topic. |
| ---- | ---- | ||
| + | ==== *21) Suggest: Adding - identify the license conditions of the applicable licenses ==== | ||
| + | Submitted By: Till Jaeger | ||
| + | [Feedback was receive after the first version of the spec was finalized] | ||
| + | I'm very happy with the current draft but I have one major issue for consideration (in this or a later version): in my experience, it is a common problem that companies do not (properly) identify the license conditions of the applicable licenses. | ||
| + | Thus, I recommend to add something in the specification like "(process for) identifying license conditions of applicable FOSS licenses". | ||
| + | |||
| + | 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. | ||
openchain/spec-2016-h1-public-comments.txt · Last modified: 2016/10/05 00:03 by mgisi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
