THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Business Team/Adoption"
(→Use of META Tags) |
(→License List) |
||
| Line 14: | Line 14: | ||
The license list is a key component for SPDX. | The license list is a key component for SPDX. | ||
| − | + | ||
| − | + | === Goals === | |
| − | + | ||
| + | We talked about one year goals. Should we have one and five? | ||
| + | |||
=== Metrics === | === Metrics === | ||
Revision as of 16:01, 28 August 2013
DRAFT AS OF 28 August 2013 Currently it is a draft until we formulate the plan at which time this sentence will be removed.
Contents
Adoption
This page is being used to track the adoption of SPDX.
We will track adoption in three key areas:
- SPDX License List
- Generating or consuming SPDX Documents
- Using SPDX meta tags in software
License List
The license list is a key component for SPDX.
Goals
We talked about one year goals. Should we have one and five?
Metrics
How we will measure adoption of the license list.
Proposal: Keep a running list of organizations/people who are using?
Generation and Consumption of SPDX Documents
Metrics
How we will measure adoption.
Use of META Tags
This is a new area. It focuses on using META tags in code to help in identification of licensing and possibly other SPDX information. The technical team is looking at writing this up. Currently the U-boot community has started using a field called SPDX-License-Identifier. You can see an example here: http://git.denx.de/?p=u-boot.git;a=blob;f=post/post.c;h=4af5355fa5a20f9c2e763f37b269bea38d43e8ea;hb=6612ab33956ae09c5ba2fde9c1540b519625ba37
Metrics
How we will measure adoption of this.
