Proposal to Archive - Guide to Security Tools SIG

[afmarcum]

Based on "Application for archiving of a project" in the Project Lifecycle Process because the
process has not been defined for SIGs or WGs.

Reasons for archiving:
Spec has been published and there is no group meeting or continued communication on updates. The spec will remain an available resource of the Security Tooling WG, but the SIG itself does not need to remain listed as a sub-group of the WG.
Guide to Security Tools SIG

Please review and inform the project maintainers, OpenSSF end user community and wider community of this archiving proposal. The proposal must remain open for at least 2 weeks of discussion after the maintainers are informed and a vote must be finalized with 2/3 approval from the TAC or parent WG to complete the archive process.

[david-a-wheeler]

I think the SIG should be disbanded, and maintenance of the guide be transferred to a (newly re-invigorated) tools WG. My understanding is that the "SBOM Everywhere" work will become just one part of the tools WG, and maintaining the guide would be a sensible part of the WG role.