All Projects → spdx → License List Xml

spdx / License List Xml

Licence: other
This is the repository for the master files that comprise the SPDX License List

Labels

Projects that are alternatives of or similar to License List Xml

Cloud Mta Build Tool
Multi-Target Application (MTA) build tool for Cloud Applications https://sap.github.io/cloud-mta-build-tool
Stars: ✭ 94 (-6.93%)
Mutual labels:  makefile
Adb root
Magisk Module that allows you to run "adb root".
Stars: ✭ 97 (-3.96%)
Mutual labels:  makefile
Libreelec.tv
Just enough OS for KODI
Stars: ✭ 1,358 (+1244.55%)
Mutual labels:  makefile
Http restful api
整理HTTP后台端的RESTful API方面的知识
Stars: ✭ 94 (-6.93%)
Mutual labels:  makefile
Gomk
An opinionated Makefile for Go projects.
Stars: ✭ 96 (-4.95%)
Mutual labels:  makefile
Ozon Icon Theme
Official icon theme for Ozon OS
Stars: ✭ 97 (-3.96%)
Mutual labels:  makefile
Dockerphp
基于Docker容器化PHP开发环境解决方案
Stars: ✭ 93 (-7.92%)
Mutual labels:  makefile
Udict
A command line urban dictionary.
Stars: ✭ 99 (-1.98%)
Mutual labels:  makefile
Docker Tunnel
a (simple) dockerized ssh tunnel
Stars: ✭ 96 (-4.95%)
Mutual labels:  makefile
Moztt
Fonts used on FirefoxOS
Stars: ✭ 98 (-2.97%)
Mutual labels:  makefile
Ayu Jetbrains
Ayu colour scheme for JetBrains' IDEs.
Stars: ✭ 94 (-6.93%)
Mutual labels:  makefile
Buildroot
Buildroot, making embedded Linux easy. Note that this is not the official repository, but only a mirror. The official Git repository is at http://git.buildroot.net/buildroot/. Do not open issues or file pull requests here.
Stars: ✭ 1,320 (+1206.93%)
Mutual labels:  makefile
Cgc Release Documentation
DARPA Cyber Grand Challenge Documentation
Stars: ✭ 97 (-3.96%)
Mutual labels:  makefile
Counter Strike Docker
Docker image for Counter Strike 1.6 Dedicated Server
Stars: ✭ 93 (-7.92%)
Mutual labels:  makefile
Openwrt V2ray
V2Ray for OpenWrt
Stars: ✭ 1,358 (+1244.55%)
Mutual labels:  makefile
Docker Nginx Php Mysql
Docker running Nginx, PHP-FPM, MySQL & PHPMyAdmin
Stars: ✭ 1,322 (+1208.91%)
Mutual labels:  makefile
Dotfiles
💻 Use command line interface manager for macOS configuration.
Stars: ✭ 97 (-3.96%)
Mutual labels:  makefile
Sklearn tutorial
Tutorial for astronomy data processing with scikit-learn
Stars: ✭ 100 (-0.99%)
Mutual labels:  makefile
Kernel Tools
🐧 Kernels on Scaleway
Stars: ✭ 99 (-1.98%)
Mutual labels:  makefile
Techladder
Job titles and descriptions for UA engineering
Stars: ✭ 97 (-3.96%)
Mutual labels:  makefile

.github/workflows/deploy.yaml.github/workflows/validate.yaml

SPDX License List

What

The SPDX License List is an integral part of the SPDX Specification. The SPDX License List itself is a list of commonly found licenses and exceptions used in free and open or collaborative software, data, hardware, or documentation. The purpose of the SPDX License List is to enable easy and efficient identification of such licenses and exceptions in an SPDX document, in source files or elsewhere. The SPDX License List includes a standardized short identifier, full name, vetted license text including matching guidelines markup as appropriate, and a canonical permanent URL for each license and exception.

Why

The purpose of the SPDX License List is to enable efficient and reliable identification of such licenses and exceptions in an SPDX document, in source files or elsewhere. The SPDX short identifiers combined with the matching guidelines ensures that anyone can reliably know exactly what license text is being referred to for a given SPDX identifier.

How

  • For more about how SPDX license identifiers are used in an SPDX document, a software bill of materials, or other places that store license data, see SPDX Specification, Sections 3, 4, and 6 and Appendices II, IV, and V.
  • For examples of use of SPDX license identifiers in source code, see https://spdx.org/ids. Please note, a license not on the SPDX License List can be included in an SPDX document by using a 'LicenseRef-' and including the full license text as per the specification. If you think there is a license that should be on the SPDX License List, please follow the instructions CONTRIBUTING

This Repository

This repository contains the XML source and schema files used to generate the authoritative, supported SPDX list file formats, including the web pages you see at spdx.org/licenses and other generated data formats found in the SPDX license-list-data repository.

How to contribute/participate

We welcome participants and contributions! The SPDX License List is maintained by the SPDX Legal Team. Work and discussion is primarily done via:

  • mailing list: Please introduce yourself and let us know a bit about your interest in SPDX! The mailing list is our traditional form of communication. Join the mailing list, see archive, and manage your subscription via lists.spdx.org.
  • bi-weekly calls: used to discuss topics and issues that may be difficult to only discuss via email or via Github. Information on the bi-weekly calls and the working area for the SPDX Legal Team, can be found on the SPDX legal team wiki
  • this Github repo: comments and issues and PRs related to specific changes to the files that comprise the SPDX License List, e.g., update a URL, recommend additional markup for matching purposes, or other such changes.

See our contribution documentation for details.

Consuming License Data from this Repository

Output files in the SPDX license-list-data repository are generated from the XML source in this repository. These output files are stable and well-supported, and make the License List available in RDFa, HTML, text, and JSON formats. You can use SPDX tools (or create your own) to consume the supported formats of the license list.

Please note that the XML format for this repository is internal to the SPDX legal team and is subject to change, so any direct consumers of this repository's source files should expect occasional, backwards-incompatible changes.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].