Philippe, I agree with you but I think it is orthogonal, the SPDX license inclusion guidelines would govern what goes in the official SPDX license namespace, it does not restrict what could go into ot

While I am biased, GitHub issues are pretty useful and some of these scenarios are pretty well handled with issues and it gives people one place to look for content. For example, we could create an sp

I have added a new section at the bottom of this document that maps the fields to profiles, I've incorporated nearly all of the original proposal content into that table: https://docs.google.com/docum

My feedback (and feel free to pass this onto their list) would be to ensure they adopt SPDX Expressions (https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60) rather than accepting a sing