THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Technical Team/Best Practices
From SPDX Wiki
This is a place holder for working on the Best Practices document.
Best Practices
Contents
Introduction
Interpreting the Specification
Clarify and help with what is in the spec. Structure sections around the spec?
Tools
Best practices around using the SPDX tools
Contributing to SPDX
how to provide feedback, get involved, etc
Producing
Best practices around the process of doing it. Examples of how this is done.
Consuming
Best practices around the process of doing it. Examples of how this is done.
Notes from LinuxCon 2013 17 Sept 2013
What should be in a best practices, how does it relate to the spec?
Possibilities:
- examples
- particular questions (sort of like a FAQ)
- Could start with things that are not well defined but end up in the specification
- I need a field for X, its not there, what field could I use?
- best practices around the specification and best practices around contributing to SPDX. Maybe two documents?
- Snapshot best practices document at intervals and post on site. Use wiki for active discussions, new proposals, etc.,.
- Should we have a getting started guide?
- best practices for meta tagging like u-boot did. maybe link it in here but should be separate page. Could possibly include other information for developers supporting spdx and producing spdx friendly code. Look at things like U-boot, Mozilla, etc.,.
