[codex] Switch project licensing to Apache 2.0#561
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Switches CrewCmd's public licensing and launch messaging from BSL/source-available to Apache-2.0 open source.
Why
CrewCmd is being positioned as trusted self-hosted agent ops with room for a future managed service. The repo should use consistent open-source licensing language before promotion.
How
Apache-2.0.rogerchappel/crewcmdto match the current remote.Verification
rgfound no remaining BSL/source-available license messaging.git diff --check origin/main..HEADpnpm typecheckpnpm buildvia pre-push hook; passed with existing Next/Turbopack warnings.Risk
Medium. The code impact is docs/metadata only, but the license change is legally meaningful and should be reviewed intentionally before merge.