Steve Winslow

Given discussion in https://github.com/spdx/license-list-XML/issues/1856, I'm going to mark this as closed.

I guess I have a few thoughts: I'm not particularly concerned from the legal side, as @goneall said the point is to submit to a public open source community, whether...

That's great -- thank you @CatalinStratu!

Thanks @CatalinStratu. If there are some tests that need refactoring, that makes sense and that's fine to include in a proposed PR. I'd suggest breaking up refactoring changes into small...

Oh, I forgot to mention -- in case you're wondering what this verification code thingy is, [section 7.9 of the SPDX spec](https://spdx.github.io/spdx-spec/package-information/#79-package-verification-code-field) has more details.

Thanks @ianling. For what it's worth, the way I addressed this in the original tag-value code and SPDX model for the Golang tools was to add a second parameter, `IsFilesAnalyzedTagPresent`:...

I believe the first paragraph of this is a match for the various markup options from [HPND](https://spdx.org/licenses/HPND.html). Language from the second paragraph appears in various forms in [Rdisc](https://spdx.org/licenses/Rdisc.html) and [DOC](https://spdx.org/licenses/DOC.html)....

# License Inclusion Decision ## Decision: - [X] approved - [ ] not approved ## License full name xlock License ## Short ID xlock ## XML markup N/A ## Additional...

@richardfontana Good point on the "you must extend this exception" language being different from the more permissive "you may" language of the way we've traditionally thought about exceptions. I think...

Note that I've added [documentation on the release process](https://github.com/spdx/license-list-XML/blob/main/DOCS/release-process.md) for 3.19. The "Overview" part at the top includes some generally neutral details on license IDs during the interim period between...