From 82a7c527f93faa2ab5b7ed2a1c639046ad9ee409 Mon Sep 17 00:00:00 2001 From: Thomas Dutrion Date: Thu, 22 Jul 2021 12:08:25 +0200 Subject: [PATCH] Highlight the proprietary license trick MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From the Symfony Dev #french slack channel (symfony-devs.slack.com), people look confused regarding the value to use as license for proprietary projects, even though it's written in the documentation. Because proprietary software is still a massive part of composer's usage, I think it can be interesting to have it as a note, more readable to people. Extract from the conversation: > J’étais sur la bonne page, il me manquait deux lignes de scroll pour voir ça -.- On a tous nos petits moments de faiblesse Which roughly translates to: > I was looking at the right page, just about two lines above... We all have our weak moments --- doc/04-schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/04-schema.md b/doc/04-schema.md index 05149d331..849e5ee68 100644 --- a/doc/04-schema.md +++ b/doc/04-schema.md @@ -160,7 +160,7 @@ The recommended notation for the most common licenses is (alphabetical): Optional, but it is highly recommended to supply this. More identifiers are listed at the [SPDX Open Source License Registry](https://spdx.org/licenses/). -For closed-source software, you may use `"proprietary"` as the license identifier. +> **Note:** For closed-source software, you may use `"proprietary"` as the license identifier. An Example: