feat(new-repo): early-licence opt-in for promotion-planned private repos - #37
Merged
Conversation
…pos (refs #32) The promotion path wants nothing to scrub at flip time, yet following it used to require declaring a variance to stamp LICENSE before going public. The interview now asks private repos "is a public release already planned?" - yes stamps LICENSE at Core from the existing Public-tier template, plus a minimal NOTICE when third-party licensed material is expected while still private (attribution is owed from the moment the material arrives). Recorded in ADR-0001, no variance row: the standard's Promotion path section states the early licence IS the promotion path. Default stays no. Decided in ADR-0011. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013g4xpqBjwwzfqtKyEHuWUr
…en PRs Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013g4xpqBjwwzfqtKyEHuWUr
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
1 participant
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 & why
Following the promotion philosophy used to require declaring a variance: LICENSE ships only at +Public, so a promotion-planned private repo had to declare an exception just to carry its licence from commit #1. The interview now asks private repos "is a public release already planned?" — yes stamps
LICENSEat Core from the existing Public-tier template, plus a minimalNOTICEwhen third-party licensed material is expected while still private (attribution is owed from the moment the material arrives). Recorded in ADR-0001, no variance row: the standard's Promotion path states the early licence IS the promotion path. Default stays no — forever-private repos keep zero ceremony. Decided in ADR-0011.Refs #32
Checklist
Refs #NN(no auto-close keywords), if the repo tracks issues.feat: …,fix: …,docs: …).CHANGELOG.mdupdated under## [Unreleased]if user-visible.python scripts/*.py; see.github/workflows/validate.yml).docs/adr/for any notable decision.🤖 Generated with Claude Code
https://claude.ai/code/session_013g4xpqBjwwzfqtKyEHuWUr