Steve Winslow

Updates: * #1448 closed (unmerged) in favor of #1436 * Leaving this issue open as it appears #1436 fixes _part_ of this, but also there may be other OpenSSL exceptions...

LGTM, but I'm going to hold on merging this until 3.18 is out -- so that we can keep this connected with the 3.19 docs release cycle.

Thanks for raising this for discussion @waynebeaton! Like @zvr, I'm also not opposed to recording such information in a more standardized way. We do already end up often collecting this...

Thanks @waynebeaton, this is helpful context. Personally my thoughts are that it would be useful, at a minimum, for the SPDX License List to have "this exception is intended for...

Hi @goneall, to my knowledge it is a standard AWS S3 bucket. I didn't set it up but I do have at least some level of access to it (enough...

Hi @goneall, apologies for the slow delay on this. I'm looking into the permissions I've got to see whether it looks like I can add and configure this. My guess...

Okay, yeah... I'm getting a lot of "not authorized to perform X" sorts of errors when trying to access / list or create CloudFront resources. So it looks like we'd...

Now in this repo at https://github.com/spdx/license-list-XML/blob/main/DOCS/faq.md Open for folks to do: * Can submit PRs for updating current text * Can add new questions (and answers) @jlovejoy and @swinslow happy...

I'd tend to agree with @zvr here. There's two caveats why I might not though: 1. If the "canonical" version of a particular license is usually in MarkDown, then is...

Also discuss whether folks "should" use identifiers prior to a release going out to the website