Arthit Suriyawongkul
Arthit Suriyawongkul
A separate section might be a nice idea, in a way that it will allow us to choose what to be generated in which circumstances. If the "Example" section is...
For example, if the PowerPoint file is from 2025-04-11 meeting, it should be named `operations/2025/2025-04-11-XXXX.pptx`
Unfortunately, me neither. But I think it's good for the merge.
We currently use MkDocs with its "readthedocs" lookalike theme and its default search plugin. Nothing you can change much with it apart from the shortest length of words for indexing...
On the star search, interesting. Thanks for putting this to our awareness. Not sure if we can enable this by default. Or maybe find a way to put a sentence...
Need to update the GitHub workflow in the support branch to keep up with the changes in the spec-parser command line interface.
@goneall That is possible. Need to setup at both side, at the Repo A that will trigger / dispatch the rebuilding signal and at the Repo B that will receive...
This document also has a concept of "known unknown" https://www.cisa.gov/resources-tools/resources/2025-minimum-elements-software-bill-materials-sbom
The example validation failed, because https://spdx.org/schema/3.0/spdx-json-schema.json is not exist yet. - Need to fix this issue first #1246
We don't yet have a clear path to republish `support/3.0` yet. As I understand, if we are still in 3.0.x and don't have 3.1 yet, do we have to push...