THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Business Team/Beta Program/Feedback"
From SPDX Wiki
| Line 1: | Line 1: | ||
| − | <p>Add your Beta Feedback Here. Put your name & company at the beginning of your feedback.</p><p> </p><p><strong>My Company -- My Name</strong></p><ol><li>feedback item 1</li><li>feedback item 2</li></ol | + | <p>Add your Beta Feedback Here. Put your name & company at the beginning of your feedback.</p><p> </p><p><strong>My Company -- My Name</strong></p><ol><li>feedback item 1</li><li>feedback item 2</li></ol><p> </p><hr /><p> </p><p> |
<span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px; font-weight: bold;">Antelink -- Freddy Munoz</span></p> | <span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px; font-weight: bold;">Antelink -- Freddy Munoz</span></p> | ||
| − | <p><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;"><ol><li style="font-weight: normal;"><strong>How well did the SPDX format cover information you need to exchange?<br /></strong>The format provides reliable information about licenses (based on human analysis) and the distinction between the licences who are declared by the package creator and those which are found in files.</li><li style="font-weight: normal;"><strong>What was effort involved in converting to/from SPDX format?<br /></strong>The conversion from the SPDX file format to an object model was easily made.</li><li style="font-weight: normal;"><strong>Did the SPDX format help you understand what was in the software?<br /></strong>The SPDX file format gives declarative fine scale information about the licenses and the origin of each file in the package.</li><li style="font-weight: normal;"><strong>How did the standard license information work for you?<br /></strong>For us the standard license information is very important because is much more precise and reliable than a simple declaration of the licence's name with no standard formatting.</li><li style="font-weight: normal;"><strong>Can you see how using SPDX could save your organization time/money?<br /></strong>When we collect information about open source projects, it would be easier to parse information if the licence information were completely machine readable. SPDX format provides this feature.</li><li style="font-weight: normal;"><strong>Are any changes needed to make SPDX meet your needs?<br /></strong>If any file's licence cannot be defined ("none") it would be better if the format allowed to use "none" as one of concluded licenses.<br />It's necessary to impose every concluded license to be the concluded license of at least one file, otherwise some licenses could be considered as concluded licenses of the package but we cannot know from which file (component) they come from.</li></ol><p> </p><p> </p>< | + | <p><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;"> </span></p><ol><li style="font-weight: normal;"><strong>How well did the SPDX format cover information you need to exchange?<br /></strong>The format provides reliable information about licenses (based on human analysis) and the distinction between the licences who are declared by the package creator and those which are found in files.</li><li style="font-weight: normal;"><strong>What was effort involved in converting to/from SPDX format?<br /></strong>The conversion from the SPDX file format to an object model was easily made.</li><li style="font-weight: normal;"><strong>Did the SPDX format help you understand what was in the software?<br /></strong>The SPDX file format gives declarative fine scale information about the licenses and the origin of each file in the package.</li><li style="font-weight: normal;"><strong>How did the standard license information work for you?<br /></strong>For us the standard license information is very important because is much more precise and reliable than a simple declaration of the licence's name with no standard formatting.</li><li style="font-weight: normal;"><strong>Can you see how using SPDX could save your organization time/money?<br /></strong>When we collect information about open source projects, it would be easier to parse information if the licence information were completely machine readable. SPDX format provides this feature.</li><li style="font-weight: normal;"><strong>Are any changes needed to make SPDX meet your needs?<br /></strong>If any file's licence cannot be defined ("none") it would be better if the format allowed to use "none" as one of concluded licenses.<br />It's necessary to impose every concluded license to be the concluded license of at least one file, otherwise some licenses could be considered as concluded licenses of the package but we cannot know from which file (component) they come from.</li></ol><p> </p><p> </p><p> </p> |
Revision as of 10:26, 7 July 2011
Add your Beta Feedback Here. Put your name & company at the beginning of your feedback.
My Company -- My Name
- feedback item 1
- feedback item 2
- How well did the SPDX format cover information you need to exchange?
The format provides reliable information about licenses (based on human analysis) and the distinction between the licences who are declared by the package creator and those which are found in files. - What was effort involved in converting to/from SPDX format?
The conversion from the SPDX file format to an object model was easily made. - Did the SPDX format help you understand what was in the software?
The SPDX file format gives declarative fine scale information about the licenses and the origin of each file in the package. - How did the standard license information work for you?
For us the standard license information is very important because is much more precise and reliable than a simple declaration of the licence's name with no standard formatting. - Can you see how using SPDX could save your organization time/money?
When we collect information about open source projects, it would be easier to parse information if the licence information were completely machine readable. SPDX format provides this feature. - Are any changes needed to make SPDX meet your needs?
If any file's licence cannot be defined ("none") it would be better if the format allowed to use "none" as one of concluded licenses.
It's necessary to impose every concluded license to be the concluded license of at least one file, otherwise some licenses could be considered as concluded licenses of the package but we cannot know from which file (component) they come from.
