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 other license
namespaces (which would be implemented by the other proposal currently
being disc
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 spdx-meetings
repository, create an issue to capture the notes from each meeting (you
can use mar
whether it means AND or OR). There
are a number of parsers out there for this format.
Regards,
William Bartholomew
On Tue, Oct 22, 2019 at 12:33 PM Santiago Torres Arias
wrote:
> Hi,
>
> The Arch Linux community recently started a discussion around adopting
> SPDX license identifiers
During the discussion about SPDX 3.0 and positioning SPDX as an option for
the various SBoM efforts that are going on, one of the discussion points
was about making the specification more digestible by moving content that
is secondary to the format of an SPDX document out of the specification and
i