William Bartholomew

404 page isn't working

1

If you visit a URL that doesn't exist in the spdx-spec (for example, https://spdx.github.io/spdx-spec/this-does-not-exist) you get a broken page with missing stylesheets and a TOC that doesn't work.

Simultaneous deployments fail

1

If there are two PRs deploying at the same time one will fail because `gh-pages` changes under them. This is a good behavior because it prevents content being lost but...

Resolves #475, #476

Move Appendix G (CC License) and J (Differences From Earlier Versions) to be Appendix A and B

1

These two appendices will always exist so I suggest we move them to be the first two appendices to simplify future section renumbering.

Reverse order of Annex J

1

Currently the way Annex J is ordered every time we release a new version we will have to re-number every section on that page. If we reverse the order so...

For the 3.0 version of the specification we should remove all sections and fields that were marked as deprecated in SPDX 2.x.

Issue #72 is a prerequisite for this. In the configuration for a crawler you should be able to specify patterns that will set the preferred queue for a request based...

When queuing a request you should be able to specify a preferred queue for that request. The preferred queue should be transitive for any child requests queued from that request.

Version range

29

Is there desire for PURL to support version ranges or is that out of scope? For example, to describe vulnerable versions of a package.

New rule: package.json validation for NodeJS

3

- [ ] license parseable as a SPDX expression - [ ] description provided - [ ] keywords provided - [ ] homepage provided - [ ] author provided -...