Add SPDX license headers when first BSL 1.1 file is added #8

New issue

Open

opened 2026-04-06 22:25:19 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-04-06 22:25:19 -07:00

Owner

Summary

Per cf-licensing review: when cf_voice integration begins and BSL 1.1 files first appear in the repo, add SPDX headers to ALL existing MIT files at the same time so the boundary is visually clear from the first BSL commit.

When to do this

At the start of the cf-voice integration milestone (milestone 4). Not before.

Pattern

# SPDX-License-Identifier: MIT
# Copyright (c) 2026 CircuitForge LLC

on all current files. BSL files get:

# SPDX-License-Identifier: BSL-1.1
# Copyright (c) 2026 CircuitForge LLC

Also update LICENSE file to include BSL 1.1 text as a second section.

References

cf-licensing review finding

## Summary Per cf-licensing review: when `cf_voice` integration begins and BSL 1.1 files first appear in the repo, add SPDX headers to ALL existing MIT files at the same time so the boundary is visually clear from the first BSL commit. ## When to do this At the start of the cf-voice integration milestone (milestone 4). Not before. ## Pattern ```python # SPDX-License-Identifier: MIT # Copyright (c) 2026 CircuitForge LLC ``` on all current files. BSL files get: ```python # SPDX-License-Identifier: BSL-1.1 # Copyright (c) 2026 CircuitForge LLC ``` Also update LICENSE file to include BSL 1.1 text as a second section. ## References - cf-licensing review finding